Windows 2008 Corrupt TCP/IP? (Ping access denied)

Question

I'm having a weird problem on two Windows 2008 VMs (inside HyperV) running NLB. They were working at one point, but now TCP/IP appears to be corrupt. I cannot ping anything if logged in with my Domain Admin account:

>ping 10.1.1.1
Unable to contact IP driver, error code 5,

I tried resetting winsock and ip with netsh. That makes no difference:

netsh int ip reset
Resetting Echo Request, failed.
Access is denied.

I uninstalled NLB, I removed the synthetic NIC and added a legacy NIC from Hyper-V -- no dice.

The weird thing is that it works if I login with the built-in Administrator account, but not my Domain Admins account. UAC is disabled, so this should just work.

Any ideas apart before I call PSS?

Edit: Can't ping anything if I don't login with the built-in Administrator account. (UAC on or off makes no different.) Can't ping 127.0.0.1 (access denied). NICs are the HyperV ones.

I installed SP2 for Windows 2008, no change.

Solution

I ran into this same problem on Server 2008, completely out of the blue. Tried the same steps as you also, with no luck. I ended up dumping the Winsock and Winsock2 settings from the registry from another (working) box and using those.

Download from here and here.

If you want to give it a shot, just back up HKLM\SYSTEM\CurrentControlSet\Services\WinSock and HKLM\SYSTEM\CurrentControlSet\Services\WinSock2 first to be safe. After you back those keys up, delete them from the registry, then import and reboot. Dumped from Server 2008 x86.

Comments

[Gareth Williams]

Tried that too - no luck.

[JFV]

The only other thing I can recommend is to update the drivers for your network card and see if that helps.

[Ryan Ferretti]

Not even local host? That's surprising. I'd give Corey's regkeys a try then.

[Gareth Williams]

Even tried turning off the firewall - no luck.

[Corey]

I should mention that my problem was also with virtualized Server 2008 (running on VMware Workstation 6.5). I had three Server 2008 VMs on a new forest/domain; Domain Controller, Exchange 2007 server, BES. My user account (Domain Admin) and the BESAdmin account could not ping on the BES, but the local Administrator could. Both BESAdmin and my account could run ping on other boxes. The referenced error message is not a firewall issue and it's not a permission issue as other users are suggesting. In my case the box responded to pings too, the problem was weird Winsock corruption.

[Manu]

solving a problem in 2021 with your solution. thx mate, have my upvote!