Home / server / Questions / 10161
Accepted
MichaelGG
Asked: 2009-05-20 16:21:42 +0800 CST

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

  • 772

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.

windows windows-server-2008 uac tcpip netsh

5 Answers

  1. Best Answer

    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.

    • 2

  2. I've run into a few things that still need you to 'Run as administrator' on Vista and Win2008. Even if UAC is disabled. Not sure why, but try it and see if it helps out.

    -JFV

    • 0

  3. Can you ping localhost? If so then TCP/IP should be fine. Perhaps it's got a domain firewall setting enabled that it shouldn't have?

    • 0

  4. Check the firewall is not blocking PING (ICMP - listed under file and printer sharing).

    I had a similar problem previously where the host and virtual machine both had the firewall enabled and both were blocking PING, caused all kinds of havoc.

    • 0

  5. If your Firewall is enabled...you should enable File and Printer sharing.....File and printer sharing allow ICMP packets which is being used by PING

    OR

    If you dont need Windows Firewall...make sure to turn it all off....3 levels...

    • 0