Windows 2003 Server can resolve hostnames with NSLOOKUP but not PING - TechRepublic
General discussion
April 26, 2014 at 01:27 AM
mdimunno

Windows 2003 Server can resolve hostnames with NSLOOKUP but not PING

by mdimunno . Updated 12 years, 1 month ago

I have a Windows 2003 SP2 server which is giving me a problem. I cannot resolve hostnames while using the PING command. It does not matter if these hostnames are for machines that are part of my LAN, or hostnames for websites / machines outside of my network (like google.com). I can however, successfully ping machines on my LAN and the WAN via IP address.

The most interesting part about all of this is that NSLOOKUP works fine. So, I can do “nslookup google.com” and get a result, which means DNS resolution is working to a degree.

The primary DNS server on this machine is a domain controller, and so is the secondary. However, for testing purposes, I changed the DNS servers assigned to the NIC to outside public DNS servers and I still cannot resolve hostnames when attempting to PING. For the heck of it, I even tried placing an entry in the HOSTS file and I still cannot get it to resolve when using the PING utility.

We have rebooted tons of times thus far. I am remotely connected to this server, so this does not appear to be a connection-related issue. We have reset winsock and the IP stack using the commands “netsh int IP reset” and “netsh winsock reset all” to no avail. I am at my wits end and would appreciate any ideas anyone might have.

This discussion is locked

All Comments