Hyper-v assigns auto-configuration IP for virtual network
Posted on 2011-05-03
My server has two static IPs (one NIC with two ports). When I create a virtual external network in Hyper-v manager (named External1) and assign it to port 1, it works until I reboot, at which point Windows assigns it an auto-configuration IP address in the 169 range and therefore I cannot connect to the server on it, nor can vm's connect outbound. If I assign External1 to port 2 it doesn't have a problem.
Note that both port 1 and 2 are statically configured. Port 1 has a default gateway and port 2 does not.
To fix it I have to delete External1 and reboot the server. Then I can connect again, but have no virtual network to use anymore. Another way to fix it is to delete External1 and set port 1 to DHCP which allows me to connect (so it's not a cabling issue) but I need the static IP.
Ideally I want a virtual network on each port (named External1 and External2) so that I can assign vm's to one or the other.
The server with this problem is part of a 2-node cluster. The partner server doesn't seem to have a problem and I have two virtual networks on it.
I also tried setting the 'alternate configuration' for port 1 to use the same static settings but it still keeps assigning the auto-config IP.
Server is running Win2008 R2 SP1.