I've thrown myself into learning Hyper-V and Server 2012 over the past week or so, and I'm working on setting up a virtualized WDS/MDT server using Hyper-V. I'm having an issue managing/understanding the way the virtual switch works, and I've been unable to find a proper answer for my issue.
Currently, my box is set like this (with one physical NIC):
- Server 2012 (host) with Hyper-V and DHCP roles installed (dhcp scope
as 192.168.1.3 to .254)- Server 2012 (guest) with WDS & MDT
installed. (static to 192.168.1.2)
- Server 2012 (guest) with WDS & MDT
I've set up a virtual switch as external, and bound it to the physical NIC. The issue I have is with the IP address of the host. When I look at ipconfig on the host, my physical adapter has a 169...* address. My guest OS has no problem pulling an IP from the host DHCP server, nor do any other physical machines connected to the (unmanaged) switch.
The question I have is, is this working as intended? Another lab running VMware allows me to set the guest connection as bridged, and I'm able to manage both the host and guest with a single NIC, I'm just not sure how to do this in Hyper-V. I'm unable to manage the host server from another device on the network, which I imagine is wrong. Do I need two NICs, one dedicated to the guests and one dedicated to the host to have this work the way I want?
Best Answer
It sounds like you didn't enable the
Allow management operating system to share this network adaptersetting on the virtual switch. With a single NIC you'll need to enable this on the virtual switch so that you can assign an IP address to the virtual Ethernet adapter that will be created once this setting enabled, which is the ip address that you'll connect to the host with. Otherwise you'll have no network connectivity to the host itself.