active directory - Why is the secondary interface address on our AD DCs in our domain's primary DNS zone?

We have 2 hardware interfaces on our Active Directory Domain Controllers. The secondary interface should never be listed in our domain's DNS zone, but it is. This is problematic because most machines on the network do not have access to the secondary subnet that the DCs are on.

For example, our primary subnet is 10.10.10.0, the secondary network is 192.168.0.0. When clients on the primary network query our AD DNS servers for the DC address, they often get 192.168.0.15 as a result. Clients aren't on that subnet, so everything breaks.

I've tried every combination of advanced DNS settings on the secondary interface on both machines and yet, the secondary IP always ends up being published in the domain DNS zone. I've unchecked "register this connection's address in DNS" with no success. I've left that checked and set a different DNS suffix for the connection (for a different, working zone) along with checking the "Use this connection's DNS suffix in DNS registration" box to no avail. Of course, I always delete the incorrect DNS listing before trying these settings.

Any ideas would be appreciated!

Answer

More than one network adapter is not recommended on domain controllers.

Routers should do routing not domain controllers :)

Although there are workarounds I think all of them are only causing more trouble when You forget about them later and want to revert back.

Usefull links:

or just google search for multihomed domain controllers. You will always get same answer:
- not recommended / causing troubles / but possible.

windows 10 - How do I enable the option to "Notify to schedule restart"?

I have two machines with Windows 10 Home. One of them, in Settings > Update & security > Windows Update > Advanced options, has a drop-down menu where I can choose to automatically install updates whenever available ("Automatic (recommended)") or at a time of my choosing ("Notify to schedule restart"). The other machine, in the same location, does not have that option. How do I get that option to appear in the latter machine?

The machine with this option is on build 10586.679, recently updated from 10586.633. The machine without this option is on build 14393.447.

The machine with this option:

The machine without this option:

After updating the older machine to build 14393.0, the Advanced Options screen is just as restricted as the one on the newer machine. How do I restore this vital functionality to both machines?

security - Linux-KVM / iptables: prevent guest spoofing by matching ip+mac address on bridge?

I have my KVM guests on a standard br0 bridge setup:

auto br0
iface br0 inet static

   address 192.168.1.117
   netmask 255.255.255.0
   network 192.168.1.1
   broadcast 192.168.1.225
   gateway 192.168.1.1
   bridge_ports eth0
   bridge_stp off
   bridge_fd 0

auto eth1

iface eth1 inet static
address 10.0.0.117
netmask 255.255.255.0
gateway 10.0.0.1
broadcast 10.0.0.225

eth1 is reserved for other traffic but a guest could simply change it's ip to connect to it.

What I am trying to achieve is dropping all traffic towards the host / outside / other guest as soon as a guest attempts to change either it's ip address or mac address (in an attempt to join the other network / spoof another guest)

I tried many interfaces (eth0, br0, tap0, tap+) but I cannot seem to get my rule right:

iptables -A INPUT -m physdev --physdev-in tap+ --physdev-out tap+ -s 192.168.1.205 -m mac ! --mac-source 52:54:5a:8d:77:8e -j DROP

IP forwarding is enabled- there are no other rules in iptables.
Am I missing something- or even should I consider try to achieve this another way?

Using AutoHotkey, I'm trying to remap the function keys to their secondary function as default and the default as the secondary

I'm trying to remap the function keys to their secondary function as a default nut I'm running into a few issued in the code. One thing to note is that, in my keyboard driver software, I can switch the Fn key to be a right windows key so I can avoid the low level coding issues involved with the Fn key.

I have written the following and the first bunch of hotkeys seem to work fine:

RightWindowsDown := 0
F1::Send {Volume_Mute}
F2::Send {Volume_Down}
F3::Send {Volume_Up}
F4::Send {Launch_App2}
F5::Send {Media_Play_Pause}
F6::Send {Media_Stop}
F7::Send {Media_Prev}
F8::Send {Media_Next}
F9::Send {Launch_App1}
RWin::
{
    RightWindowsDown:=1
    soundbeep
}
If (RightWindowsDown = 1)
{
    F1::F1
    F2::F2
    F3::F3
    F4::F4
    F5::F5
    F6::F6
    F7::F7
    F8::F8
    F9::F9
}
return

However, when I press the RWin key, it just spams the normal F1 key and opens up a load of help pages. Any ideas on how I can avoid this?

Installed Ubuntu on usb drive, now it's read-only and can't be formatted

I installed Ubuntu (ubuntu-13.04-desktop-amd64) on a 8 gb pendrive. Because it worked pretty slow, I wanted to change it back to a normal pendrive. But this is what happened.

Windows7 can't open the usb drive, can't view files or anything, can't access attributes. When I select to format, it says it can't format it because it is write-protected. Tried the same running from an Ubuntu, and trying from a booted GParted thing. When I view the partitions, they can't be deleted either.

What should I do to get it formatted?

hp - Proliant server will not accept new hard disks in RAID 1+0?

I have a HP ProLiant DL380 G5, I have two logical drives configured with RAID. I have one logical drive RAID 1+0 with two 72 gb 10k sas 1 port spare no 376597-001.

I had one hard disk fail and ordered a replacement. The configuration utility showed error and would not rebuild the RAID. I presumed a hard disk fault and ordered a replacement again. In the mean time I put the original failed disk back in the server and this started rebuilding. Currently shows ok status however in the log I can see hardware errors.

The new disk has come and I again have the same problem of not accepting the hard disk.

I have updated the P400 controller with the latest firmware 7.24 , but still no luck.

The only difference I can see is the original drive has firmware 0103 (same as the RAID drive) and the new one has HPD2.

Any advice would be appreciated.

Thanks in advance

Logs from server

ctrl all show config

Smart Array P400 in Slot 1 (sn: PAFGK0P9VWO0UQ)

  array A (SAS, Unused Space: 0  MB)


  logicaldrive 1 (68.5 GB, RAID 1, Interim Recovery Mode)

  physicaldrive 2I:1:1 (port 2I:box 1:bay 1, SAS, 73.5 GB, OK)
  physicaldrive 2I:1:2 (port 2I:box 1:bay 2, SAS, 72 GB, Failed

  array B (SAS, Unused Space: 0  MB)



  logicaldrive 2 (558.7 GB, RAID 5, OK)

  physicaldrive 1I:1:5 (port 1I:box 1:bay 5, SAS, 300 GB, OK)
  physicaldrive 2I:1:3 (port 2I:box 1:bay 3, SAS, 300 GB, OK)
  physicaldrive 2I:1:4 (port 2I:box 1:bay 4, SAS, 300 GB, OK)

ctrl all show config detail

  Smart Array P400 in Slot 1
  Bus Interface: PCI
  Slot: 1
  Serial Number: PAFGK0P9VWO0UQ
  Cache Serial Number: PA82C0J9VWL8I7
  RAID 6 (ADG) Status: Disabled
  Controller Status: OK
  Hardware Revision: E
  Firmware Version: 7.24
  Rebuild Priority: Medium

  Expand Priority: Medium
  Surface Scan Delay: 15 secs
  Surface Scan Mode: Idle
  Wait for Cache Room: Disabled
  Surface Analysis Inconsistency Notification: Disabled
  Post Prompt Timeout: 0 secs
  Cache Board Present: True
  Cache Status: OK
  Cache Status Details: A cache error was detected. Run
  more information.

  Cache Ratio: 100% Read / 0% Write
  Drive Write Cache: Disabled
  Total Cache Size: 256 MB
  Total Cache Memory Available: 208 MB
  No-Battery Write Cache: Disabled
  Battery/Capacitor Count: 0
  SATA NCQ Supported: True

  Array: A
  Interface Type: SAS

  Unused Space: 0  MB
  Status: Failed Physical Drive
  Array Type: Data

  One of the drives on this array have failed or has




     Logical Drive: 1

     Size: 68.5 GB
     Fault Tolerance: RAID 1
     Heads: 255
     Sectors Per Track: 32
     Cylinders: 17594
     Strip Size: 128 KB
     Full Stripe Size: 128 KB
     Status: Interim Recovery Mode
     Caching:  Enabled
     Unique Identifier: 600508B10010503956574F305551

     Disk Name: \\.\PhysicalDrive0
     Mount Points: C:\ 68.5 GB
     Logical Drive Label: A0100539PAFGK0P9VWO0UQ0E93
     Mirror Group 0:
        physicaldrive 2I:1:2 (port 2I:box 1:bay 2, S
     Mirror Group 1:
        physicaldrive 2I:1:1 (port 2I:box 1:bay 1, S
     Drive Type: Data

     physicaldrive 2I:1:1

     Port: 2I
     Box: 1
     Bay: 1
     Status: OK
     Drive Type: Data Drive
     Interface Type: SAS
     Size: 73.5 GB
     Rotational Speed: 10000
     Firmware Revision: 0103
     Serial Number: B379P8C006RK

     Model: HP      DG072A9B7
     PHY Count: 2
     PHY Transfer Rate: Unknown, Unknown

     physicaldrive 2I:1:2
     Port: 2I
     Box: 1
     Bay: 2
     Status: Failed
     Drive Type: Data Drive

     Interface Type: SAS
     Size: 72 GB
     Rotational Speed: 15000
     Firmware Revision: HPD9
     Serial Number: D5A1PCA04SL01244
     Model: HP      EH0072FARUA
     PHY Count: 2
     PHY Transfer Rate: Unknown, Unknown



     Array: B
     Interface Type: SAS
     Unused Space: 0  MB
     Status: OK
     Array Type: Data



     Logical Drive: 2
     Size: 558.7 GB

     Fault Tolerance: RAID 5
     Heads: 255
     Sectors Per Track: 32
     Cylinders: 65535
     Strip Size: 64 KB
     Full Stripe Size: 128 KB
     Status: OK
     Caching:  Enabled
     Parity Initialization Status: Initialization Co
     Unique Identifier: 600508B10010503956574F305551

     Disk Name: \\.\PhysicalDrive1
     Mount Points: E:\ 558.7 GB
     Logical Drive Label: AF14FD12PAFGK0P9VWO0UQD007
     Drive Type: Data

     physicaldrive 1I:1:5
     Port: 1I
     Box: 1
     Bay: 5
     Status: OK

     Drive Type: Data Drive
     Interface Type: SAS
     Size: 300 GB
     Rotational Speed: 10000
     Firmware Revision: HPD4
     Serial Number: 3SE07QH300009923X1X3
     Model: HP      DG0300BALVP
     Current Temperature (C): 32
     Maximum Temperature (C): 45
     PHY Count: 2

     PHY Transfer Rate: Unknown, Unknown

     physicaldrive 2I:1:3
     Port: 2I
     Box: 1
     Bay: 3
     Status: OK
     Drive Type: Data Drive
     Interface Type: SAS
     Size: 300 GB

     Rotational Speed: 10000
     Firmware Revision: HPD4
     Serial Number: 3SE0AHVH00009924P8F3
     Model: HP      DG0300BALVP
     Current Temperature (C): 34
     Maximum Temperature (C): 47
     PHY Count: 2
     PHY Transfer Rate: Unknown, Unknown

     physicaldrive 2I:1:4

     Port: 2I
     Box: 1
     Bay: 4
     Status: OK
     Drive Type: Data Drive
     Interface Type: SAS
     Size: 300 GB
     Rotational Speed: 10000
     Firmware Revision: HPD4
     Serial Number: 3SE08NAK00009924KWD6

     Model: HP      DG0300BALVP
     Current Temperature (C): 35
     Maximum Temperature (C): 47
     PHY Count: 2
     PHY Transfer Rate: Unknown, Unknown

Answer

You may have a spare (replacement) drive whose size in sectors is slightly less than the original drive.

What operating system are you using? We can look at the hpacucli output to determine this for sure.

I will update this answer once we get more information.

Edit:

See my answer on: Smart Array P400i Physical Drive failed after being replaced for the tool download link for Windows 2008...

I'm specifically looking for the output of ctrl all show config.

---

Edit:

Now that I've seen your hpacucli output, you're in an incredibly rare situation.

  logicaldrive 1 (68.5 GB, RAID 1, Interim Recovery Mode)

  physicaldrive 2I:1:1 (port 2I:box 1:bay 1, SAS, 73.5 GB, OK)
  physicaldrive 2I:1:2 (port 2I:box 1:bay 2, SAS, 72 GB, Failed

Your original 72GB drives were actually larger than 72GB. As you can see, your healthy disk is a 73.5GB disk. HP changes disk manufacturers during the product lifetime, keeping the same spare part numbers. In this case, the replacement sent to you is a true 72GB drive. The rebuild would definitely not work.

The only thing that can fix this one is an equal or larger-size physical drive. Simply send this output to HP and ask for a 146GB disk if you're under warranty. If you're not under warranty, just get a 146GB disk and it'll rebuild as a "68.5 GB" RAID-1 member.

Also, ask for a 10k RPM 146GB disk. Your old 72GB disk is a 10k RPM (which was discontinued in that capacity LONG ago). The HP replacement is a 15k RPM drive.

Windows 8.1 64-bit: High memory usage

I have 8GB of memory on a 64 bit windows 8.1 machine, and windows is telling me I'm using 91% of my memory, yet its simultaneously telling me I'm only using 3GB.

I literally just restarted my machine a few minutes ago because it was being incredibly rediculously slow. I'm currently only running chrome (with a ton of tabs, but doesn't add up to anywhere near 7.5GB). What could be going on here?

Here's a bunch of my current info

I took a look at this: How to find source of memory leak in Windows 7? but I wasn's able to use xperf and the rest didn't lead me to a solution.

UPDATE - RamMap:

UPDATE 2: I checked Resource Monitor at Wouter's suggestion and found an "Image" called lxdecoms.exe with over 6GB of Commt (KB). I tried killing the process, but while it lowered my Commit Charge, it didn't affect "Used Physical Memory". So I restarted hoping to capture it again in full, but its not back yet and yet the problem persists.

I should note that I do have a Centos virtual box virtual machine running on my machine, not sure if that has any weird memory impacts that aren't reflected in the numbers in these tools.

I got xperf working, so here's my resource monitor and a wpa analysis of my xperf output (from xperf -on ReferenceSet -BufferSize 1024 -MaxFile 512 -FileMode Circular && timeout 5 && xperf -d MemUsage.etl):

What is N/A that's taking up 2.7GB of memory? My VM?

Answer

The high memory usage comes from a high Page table and Driver Locked usage.

To see which processes causes the page table usage, install the Windows Performance Toolkit, open a command prompt as admin and run this command:

xperf -on ReferenceSet -BufferSize 1024 -MaxFile 512 -FileMode Circular  && timeout 5 && xperf -d C:\HighMemoryUsage.etl

Open the HighMemoryUsage.etl with Windows Performance Analyzer (WPA.exe), drag and drop the graph "ResidentSet" from the left graph list to the analysis pane:

Now move the "Page Category" column to the left side and expand the "Page Table" entry:

Here you see the processes which have the high pagetable usage. On the right site (after the blue line), you see page table memory usage in MB for each process.

The Driver Locked usage can be caused by Virtual Machines like Hyper-V. If this is not the case, use the Windows Assessment Toolkit to see which driver is causing the Drivers Lock usage: