Moved VM from one 2008 R2 machine to another - now network won't work
I moved a Windows Server 2008 R2 VM from one Windows Server 2008 R2 host to another. When I started up the VM everything seemed ok, but the network didn't work. It was showing up as an unknown device. I tried to installed the Hyper-V Integration Services.....but they just spun around and never did anything. I tried removing the network adapter and adding it again, no dice. I added a legacy network adapter. No dice. I extracted the files from the HyperVIntegrationServices6
Manually installing the legacy network adapter won't work at all - won't find the device, driver, notta. If I manually install a driver for the regular (non legacy) network adapter I get "This device is not configured correctly."
Any idea what has happened or how I can fix this?
Manually installing the legacy network adapter won't work at all - won't find the device, driver, notta. If I manually install a driver for the regular (non legacy) network adapter I get "This device is not configured correctly."
Any idea what has happened or how I can fix this?
Craig Beck
The NICs need to be named EXACTLY the same on each Hyper-V host. If you move a VM from a host which attached the guest VM to "Local Area Connection 1" to a host which tries to attach the guest VM to a NIC called "Local Area Connection 2" the network connection won't work after the migration as the config file specified "Local Area Connection 1", and that may not be present, or attaches to the wrong network at the new host.
you really no need to do anything INSIDE the VM as it was caused by incomplete or incompatible settings of virtual networks.
the most easy way is to go back to the previous VM host server and copy all virtual networking settings from there. Or, open the XML based configuration file of the VM and grab required Virtual Network names, types, and set up new virtual networks on the new host accordingly. be aware that some infrastructure settings such as DHCP and NAT settings should be also correctly configured as per the VM requirements.
hope it helps.
bbao
the most easy way is to go back to the previous VM host server and copy all virtual networking settings from there. Or, open the XML based configuration file of the VM and grab required Virtual Network names, types, and set up new virtual networks on the new host accordingly. be aware that some infrastructure settings such as DHCP and NAT settings should be also correctly configured as per the VM requirements.
hope it helps.
bbao
...or just use the same NIC names on each Hyper-V host, as documented by Microsoft!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.