Hyper-V VM's cannot access Host resources, and vice-versa
Posted
by
Agent
on Server Fault
See other posts from Server Fault
or by Agent
Published on 2010-10-11T19:18:38Z
Indexed on
2010/12/23
19:55 UTC
Read the original article
Hit count: 214
I have several Hyper-V vm's running on this Win2008 R2 Server box, and up until a reboot of the host server, all the VM's were able to access shared folders on the host. Now, they can't even ping the host server.
From what I've seen, I need to setup an Internal only network through Virtual Network Manager in Hyper-V. I set this up, then tried to enable the Microsoft Virtual Network Switch Protocol option in this Internal Only NIC, but I get popups saying:
Your current selection will also disable the following features: Microsoft virtual network switch protocol
Which is absolutely stupid, considering the protocol is what I'm ticking the checkbox to Enable!
As of now, on the host, I have 2 NICs: Physical - This NIC on the host machine does have the MVNS protocol enabled Virtual Network Adapter - Created through Hyper-V Virtual Network Manager as an External type of network. Trying to enable MVNS on this NIC also produces the error above.
I've tried enabling Client for Microsoft Networks on the physical NIC for IPv6, but everytime I do that, all the VMs lose Internet connectivity and I cannot RDP into them.
Anything else I can try?
© Server Fault or respective owner