Comments on: (Fix) When DNS and ping Fail but nslookup Works (Windows)

By: Philip

Philip — Wed, 02 Nov 2011 18:26:49 +0000

I had same problem on Windows 2003 active directory domain. The netsh interface reset all seemed to work. So did putting just a . in the DNS suffix search order. That is a workaround but was faster than having to redo the IP settings on all the machines.

By: lenny

lenny — Tue, 04 Jan 2011 21:05:32 +0000

look at dns devolution. If you can ping the fqdn it is propbably the way dns devolution is setup on the client.

By: Rich

Rich — Wed, 09 Dec 2009 17:39:27 +0000

Thanks for the info.

I have this problem occasionally on the workstations of our network, where I am unable to ping by hostname or fqdn, but an nslookup works. (xp workstations, windows server 2003 r2 dhcp/dns server)

restarting the workstation’s dns client sorts it, or an ipconfig /renew. In my case netbios is disabled on our network cards and I wonder if ping.exe switches to netbios sometimes, I guess i’d have to re-enable netbios on the network to find out.

The winsock fix doesn’t solve it for me (though I have used winsock fix in the past to fix problems left by malware, successfully)

Thanks, Rich