This is a new problem that faced with HP Proliant ML 370 G6 . After Installing Windows 2008 SP2 and install Hyper-V finish all the configuration everything looks fine.
I start creating some Guest machines with Hyper-V console and joining the domain. We start see unexpected behavior like some missing PING packets and time out for DNS lookup. this looks strange as I tried a lot of HP servers and it worked fine. I made sure that HP Network Configuration is uninstalled but still facing the problem.
I start suspecting the NIC as I saw problems like this due to NIC , After disabling IPv4 Checksum Offload J It worked fine.
In most cases I can see that Guest machines are suffering in case of IPv4 Checksum Offload.
While I was searching online I found the same problem there and he recommend to disable all those:
IPv4 Checksum Offload
TCP Checksum Offload IPv4
UCP Checksum Offload IPv4
TCP Checksum Offload IPv6
UCP Checksum Offload IPv6
I saw this error before in establishing many failover clusters , In the validation phase of the cluster nodes everything went fine except the IP configurations part.
I made sure that all network drivers are static and the binding is right. But the error keep appearing every time I validate the cluster.
I found that one of my network drivers has APIPA IP although I haven’t
I run ‘ipconfig /all’ from the command prompt. You might have noticed a few extra interfaces, but not really understand what they are. I suspected that those NICs are the problem so open the server manager to see what I get. I saw that there is many drivers under Network adaptors
There I found driver called Teredo tunneling pseudo-interface
Teredo is an IPv6 transition technology that provides address assignment and host-to-host automatic tunneling for unicast IPv6 traffic when IPv6/IPv4 hosts are located behind one or multiple IPv4 network address translators (NATs). To traverse IPv4 NATs, IPv6 packets are sent as IPv4-based User Datagram Protocol (UDP) messages. For more information check Microsoft network part here
Teredo is enabled by default in Windows Server 2008.
To pass the validation wizard just disable Teredo tunneling pseudo-interface on the cluster nodes