Hyper-V VM on host DC
We have a new server with a host OS of WS2012 (WHICH ALSO FUNCTIONS AS DC.) Inside of the host OS, we have a Hyper-V VM of WS2008R2. We have a multiple NIC adapter installed in the server.
On NIC 1, we have the DC IP (192.168.1.7) serving all domain functionality (DNS, AD, DHCP, etc.)
On NIC 2, we have the external virtual switch. We have a static IP set in the VM of 192.168.1.8. The default TCP/IP properties for the NIC in the HOST OS is set to automatically obtain an IP from DHCP (with the gateway set to 192.168.1.1, but grayed out.)
This is causing the server to have multiple IP addresses (192.168.1.7, and 192.168.1.101.) It's showing both IP addresses in Server Manager for AD DS, DNS, DHCP, File and Storage Services, Hyper-V, and any other role that we have installed. We are getting tons of DNS errors, for example here's one of many:
"A duplicate name has been detected on the TCP network.
The IP address of the machine that sent the message is in the data.
Use nbtstat -n in a command window to check which name is in the conflict state. "
Obviously this is due to a multihomed server.
Any ideas what to do? Thanks!
On NIC 1, we have the DC IP (192.168.1.7) serving all domain functionality (DNS, AD, DHCP, etc.)
On NIC 2, we have the external virtual switch. We have a static IP set in the VM of 192.168.1.8. The default TCP/IP properties for the NIC in the HOST OS is set to automatically obtain an IP from DHCP (with the gateway set to 192.168.1.1, but grayed out.)
This is causing the server to have multiple IP addresses (192.168.1.7, and 192.168.1.101.) It's showing both IP addresses in Server Manager for AD DS, DNS, DHCP, File and Storage Services, Hyper-V, and any other role that we have installed. We are getting tons of DNS errors, for example here's one of many:
"A duplicate name has been detected on the TCP network.
The IP address of the machine that sent the message is in the data.
Use nbtstat -n in a command window to check which name is in the conflict state. "
Obviously this is due to a multihomed server.
Any ideas what to do? Thanks!
ASKER
The only reason I used it was that I was not previously aware that DHCP handed out an IP to a VS in the host before it reaches the VM OS where you assign a static IP. I was aware that you could branch off of NIC 1, but for simplicities sake I chose to put them on separate NICs.
I would really like this to work, since we have two servers with the same configuration. Is there any way to get networking in the VM working without having the host OS assign the VS a DHCP IP?
If nothing else, some last resort questions I have would be:
Would there be an easy way to take the current installation and somehow create a VM out of it? Or would it be more viable to create a VM DC and transfer roles?
I would really like this to work, since we have two servers with the same configuration. Is there any way to get networking in the VM working without having the host OS assign the VS a DHCP IP?
If nothing else, some last resort questions I have would be:
Would there be an easy way to take the current installation and somehow create a VM out of it? Or would it be more viable to create a VM DC and transfer roles?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
This will remove the DHCP IP from the DC roles.
http://technet.microsoft.com/en-us/library/dd363553(WS.10).aspx
As far as your NIC question, what is your reason for using NIC2?
Regards,
Scott