Occasionally on my Windows XP Pro SP3 machine, Outlook 2007 SP2 will tell me that it has had an error receiving POP mail from my SBS 2003 server, which resides on the same network.
I started a command prompt and typed “ping myserver.mydomain.local”. Sure enough, I get back the message “Ping request could not find host myserver.mydomain.local. Please check the name and try again.”
An nslookup works fine, so I know the SBS server is there and is responding to DNS requests.
In fact, I can “ping myserver” without problems. But for some reason, pinging the fully-qualified internal name doesn’t work.
Sometimes, I can just type “ipconfig /flushdns” to clear this up. Today that didn’t work. However once I actually stopped and started the DNS cache, ping started working and so did email:
net stop DNScache
net start DNScache
C:>net stop DNScache
System error 5 has occurred.
Access is denied.
C:>
You’ll need admin privileges to stop and start a service. On XP, you can use a command like this:
runas /noprofile /env /user:Administrator cmd
You will be prompted for the Administrator password, and a new command window will open.
same issue here as the OP – tried the stop and start of DNScache – each command executed successfully, but no change – can still ping both ways by IP addr but not by computer name and hence Network Neighborhood only shows the source PC name, and can not see the other shared folders
Are NSLOOKUPs resolving the names correctly? Does it help if you stop then start the “DNS Client” service (not just “DNSCache”)?
Hello, same problem as OP; Windows XP Home SP3. “PING name” does not find the host, and “PING ip-address” works fine. Also, “NSLOOKUP name” and also “NSLOOKUP name dns-server-ip-address” both work fine; that is NSLOOKUP works using it’s own default, and also using any valid DNS server I specify. But, PING and various other software like browsers, anti-virus, and pretty much any other name-dependent software will not function. Stopping/starting the DNS Client service does not fix the problem. Repairing the TCP-IP installation manually does not help. Various “TCP reset” software like Winsock Fix or LSP fix did not solve the problem. I have seen some sites recommend to remove SP3 to downgrade to SP2, then reinstall SP3 to solve this particular issue, however, this machine was installed originally from SP3 media and never had SP2, so going to SP2 is not an option. I could try a Windows Repair, but.. would prefer not to have to go through all the updates again. Any more ideas? (kindly note that reinstalling the OS from scratch is not a fix – it’s a band-aid that does not solve the problem, just eradicates the symptoms. So kindly, with respect, please don’t suggest reformatting/reloading if you don’t really know how to fix this problem)