Hi,
I am having an issue on a server with 2 NIC's that I am testing Hyper-V on.
My physical setup is 2 NIC's > unmanaged switch > router. Both NIC's on the same subnet and both connected to the switch.
The Hyper-V host is also a domain controller with DNS installed, which I know is not recommended but I was looking to use the server to test out a few different Xenapp deployments.
I set the 2nd NIC up as an external virtual network and unticked the box for allow OS to share the network adapter.
NIC 1 was set up to serve DNS requests and is the physical NIC on the DC. My first VM, lets call it CTX01 was joined on to the domain but took a lot longer than expected. The reboot took ages, sitting on applying computer settings then applying users settings for about 10 mins each. CTX01 didn't register its own record in DNS and had numerous errors and warnings in the event log. Kerberos, LDAP, unable to find domain controller, WINLOGON and group policy delays, DNS server not responding etc.
The NIC properties on the VM has its DNS server address pointing to the IP of NIC 1, which it can ping fine and it is on the same subnet.
If I only use 1 physical NIC on the host and share it with the VM's I don't have any issues at all, everything runs smoothly.
Can anyone tell me what I should be doing when using 2 NIC's in this way please, is there anything I should be setting up on the 2nd NIC before I use it for the virtual network ?
Any help would be gladly appreciated :)