XP cannot resolve DNS
I was at a friend's house last night, after they said their new PC couldn't access the internet.
I found that it can't resolve DNS. IPConfig shows everything is correct: valid IP, with DHCP server and DNS server pointing to the router.
Both IE and Firefox can access web pages through an IP address, but entering a domain name URL give the DNS error page.
DNS Client service is running.
Plugged my laptop into the router and internet browsing works perfectly.
It's a second hand PC with XP Home COA sticker, but the system restore CD is missing. If the CD turns up, I'll just wipe and reinstall XP. I fixed another strange problem on it a few weeks ago, so I think it's just a corrupt OS or virus damaged.
I haven't seen this before. Any ideas?
You'll probably find that the DNS should not be pointing at the router. Check that the router actually provides DNS. If it does then were is the router pointing to for DNS?
Either the DNS server on the router, or more likely the DNS clients on your computer need pointing to your ISP's DNS servers. Or, better IMHO than using ISP's DNS, there is OpenDNS:
126.96.36.199 and 188.8.131.52
I've had this happen twice this in last 2 months on other peoples PC's both times it was AVG8 for some reason. I could use the direct IP , but the www address would not work. If it has AVG on remove it and it should work again. If it has not got AVG on, i do not know!
My laptop used their router for DNS (obtained from the router's DHCP service), and it worked well. There wasn't any difference between their computer's and my laptops IP settings. Thanks anyway.
Originally Posted by tmcd35
@Quackers: that's worth a try when I go back. Thanks.
Is the PC setup to configure it's ip dynamically from the DHCP (router)
Is the router setup to dynamically give out requested ip addresses?
Have you refreshed the DNS in cmd using ipconfig commands and then renewed using same?
Have you chckd what address it is picking up.
Could it be the TCP/IP stack has become corrupted?
Is the windows firewall disabled?
As you have said it could be a damaged XP installation!!