This problem began on Friday and has become stranger and stranger. At my company we have two Hyper-V Servers which each host a Domain Controller. All of a sudden these DC's lost the ability to ping certain addresses. Most importantly the internet. They can ping each other and hosts on the network but when pinging their Default Gateway they are receiving time outs. When the pings do connect they are received within <1ms for about three replies then times out. Then again three or four replies and the same. I have cleared the arp cache and uninstalled and reinstalled the network cards but this problem is carrying on. I have powered off and on the DC's as well as the Switches they are supported by. The problem will be resolved for a short period and then users will begin to randomly lose internet connection. This will then carry on until all users are affected. The default gateway is on a separate switch to the DC's (this was done today as I originally believed the problem to be the switch) however, this resolved the issue temporarily but then occurred again with the slowly losing internet connection for the office. Please assist?

Hi, I suggest you ask this question in the Microsoft Hyper-V forum for further discussion. The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.Mohammed Imtiyaz Ali

Hi, I suggest you ask this question in the Microsoft Hyper-V forum for further discussion. The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.Mohammed Imtiyaz Ali

Hi, Did you get anywhere with this? I am having the same problem since 22nd June and it is not in a Hyper-V environment, it is in an SBS2008 environment. I'm thinking an update caused it, but get this. If I move it off the physical network to another network it appears to be ok. Kevin