Question : Windows Update Error on Hyper-V guest on a HP Proliant ML370 G6 (NC375i network card)

Hi,

I installed a new server two weeks ago (HP Proliant ML370 G6) on Windows Server 2008R2 with Hyper-V and I'm getting some communication problems.

The first problem that I had was with my NIC teaming. My Hyper-V guest wasn't communicating with the network except the VM Host.

This problem was solved by following this link:

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01663264/c01663264.pdf

Now everything seems to works great but I'm not able to use Windows Update, I get this error: 0×80072EE2 .

I read a couple of posts about this problem:

http://support.microsoft.com/kb/836941/en-us

http://msmvps.com/blogs/thenakedmvp/archive/2009/11/08/windows-update-error-80072ee2-hyper-v-guest-issues.aspx

http://demonictalkingskull.com/2009/08/network-problems-on-a-hyper-v-guest/

http://grinding-it-out.blogspot.com/2008/05/error-number-0x80072ee2.html

http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/e6298788-c697-421b-8f3f-55b2d89e425a

I tried to disable all Offload configurations on my two connected network card, on the teaming configuration, on the Virtual network and on the network card of the Hyper-V guests but I'm still getting the Windows update error. I started ping from my Hyper-V server and from one guest and when I start Windows Update I lose the communication between the guest and the gateway but not between the Hyper-V host and the gateway. I don't get any Windows Update problem on my Hyper-V host, only on my guests. I also try to add DisableTaskOffloa=1 to the registry but that doesn't change anything.

I don't see my network card (HP NC375i Integrated Quad Port Multifunction Gigabit Server) in this document:

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01516156/c01516156.pdf

But It's not concerning Windows Server 2008R2, maybe this card is now compatible.

Does It exist a more recent document and is somebody has the same problem with this network card?

P.S. I'm using HP NC-Series QLogic nx3 Multifunction Driver for Windows Server 2008 R2 (4.0.520.13471) and HP Network Configuration Utility for Widows Server R2 (9.90.1.0)  and my networcard Firmware version is 4.0.520.

On a other post, somebody suggest me to disolve my team, disable Offload feature and rebuild my team.

So I have deleted my virtual network, disolved my NIC teaming, disabled all Offload options:

IPV4 Checksum Offload
Large Receive Offload (LSO)
Large Send Offload V1 IPv4
Large Send Offload V2 IPv4
Large Send Offload V2 IPv6
TCP Checksum Offload IPv4
TCP Checksum Offload IPv6
TCP Connection Offload IPv4
UDP Checksum Offload IPv4
UDP Checksum Offload IPv6

on my two enable ports (I have a 4 ports card with 2 port disable), verified that all Offload feature are disable in HP NCU, Disabled Offload options on my virtual network card on the Hyper-V host and on the guest side:

IPv4 Cheksum Offload
Large Send Offload Version 2 (IPv4)
Large Send Offload Version 2 (IPv6)
TCP Checksum Offload (IPv4)
TCP Checksum Offload (IPv6)
UDP Checksum Offload (IPv4)
UDP Checksum Offload (IPv6)

And I'm still loosing communication with the gateway during Windows Update.

The only thing that I didn't modify on network cards concerning Offload is the Max Offload Connections and its set to 512.

Has anybody had the same problem?

I read a lot of post and disabling Offload feature normally solve the problem but that don't seem to work for me.

Thanks!


Jim


 

Answer : Windows Update Error on Hyper-V guest on a HP Proliant ML370 G6 (NC375i network card)

Can you :

Remove all Virtual Networks (keeping a note of static ip's you assigned to your virtual servers)
Remove all Physical NIC Drivers from "Start > RUN > Devmgmt.msc" (Delete Quad nc375i or all nics if possible)
Reboot Windows Server 2008 R2 HOST (Physical server)
Once windows comes back, let it auto detect the drivers for your nic
then instead of creating a team, as a test can you just create a virtual network and then try windows update ?

I had a network connection problem too with the same nic (at a client site server) and I removed the drivers, then elt windows detect, test it without teaming and no problems

Hope this works for you - Will check back here after work