NSLookup can resolve domain names, Ping can not resolve. Can ping IP
I am fixing a XP SP2 problem.
It is connect to a cable modem. No router. standalone, in a windows group(not domain). No proxy. I verified the following:
1. Network is getting correct info via DHCP including DNS addresses
2. NSLookup is resolving names correctly
3. I can ping machines on the internet by IP address
4. I can ping local machines by name and IP
5. When I try to ping an external machine by name (e.g., www.excite.com), I get the following error: Ping command could not find host www.excite.com. Please check the name ....
6. Pinging excite by IP (66.235.126.95) works correctly.
7. Use the resolved IP by nslookup (e.g. 66.235.126.95), can open the web page.
8. Use network packet capture tool, Microsoft network monitor, found that when I use ping to resolve a name, it did not send DNS package, but NetBios Package.
I tried uninstalling and reconfiguring NIC
I tried ipconfig /flushdns
The DNS client is running and I don't see any errors in the event log
I tried to uninstall the anti-virus soft, disable the firewall.
I tried these, but not working.
1. "netsh int ip reset resetlog.txt" to reset TCP/IP
2. "netsh winsock reset" to reset Winsock 2
Thank you!
Re: NSLookup can resolve domain names, Ping can not resolve. Can ping IP
Hi,
Do you see anything unusual in lmhosts file?
How about in safe mode with Networking?
Regards
Fradual
Re: NSLookup can resolve domain names, Ping can not resolve. Can ping IP
Re: NSLookup can resolve domain names, Ping can not resolve. Can ping IP
Got the same problem, on Windows XP. I recently tried upgrading to SP3, but the upgrade was interrupted. After which, nslookup works and ping doesn't. Tried uninstalling SP3 but problem persists.
I have a workaround however: Stop the dnscache service by typing the following line at the MS/DOS prompt:
net stop dnscache
(You have to do this every time you boot, unless you permamently disable the dnscache).
I am still looking for a proper solution to this problem, but for the moment I can get by with this workaround.
