I have 2 VMs each on 2 Hyper V 2012 R2 Hosts. The hosts are completely identical in hardware with 2 x 4-port 1Gb BroadCom NetXtreme adapters on which I disabled VMQ about 2 months ago when the Forefront VM was inexplicably and randomly losing connectivity.
Each host has a Windows Server 2012 R2 DC VM and a Windows Server 2008 SP2 member server VM (One member server VM is running Exchange 2010 SP3 and the other Forefront TMG 2010 SP2). The Exchange member server in particular has me puzzled since about a week now. Every time the Hyper-V host is restarted and this VM is started up too, either automatically or manually, it will lack true connectivity. To be sure, it shows its connection as connected but it will not be reachable or be able to reach any other system. Furthermore, any attempt to make changes to its settings will stall for a few minutes and eventually fail. Any attempt to run any program or management tool in it will lead to nothing; even TaskManager will not load.
Also, it will not shutdown or power off by Hyper-V Manager or PowerShell as it will just hang on shutting down. The only way out is to shutdown the host, which more times than not will hang and be unable to shut down cleanly because of this same situation. I then have to power off the host physically. The only work around I have found so far is to disconnect the VM's adapter from its virtual switch before starting it up, wait until it is fully booted and then reconnect the adapter to the virtual switch. This way it will have true connectivity and remain so for as long as it is up.
Does any one have an idea of what may be wrong please?
Please note: the virtual switch is bound to an adapter port that is not shared with the management OS and the virtual switch is dedicated to the VM's virtual adapter, no other VM shares the virtual switch with it.
BPK