Windows 7 browsers unable to resolve domain names

A few days ago a client's laptop just stopped connecting to the internet via the browser.
The laptop is a Dell that is only about a month old running Windows 7 with no software other than firefox  that isn't Microsoft's. All the lady does is browse the web and get eMail so she has no inclination to add any more software.

When she got it, she called me to set-up her network which includes an HP printer and her computer on a wireless network with a D-Link router.

I uninstalled Norton (through add/remove programs) and installed Microsoft Security Essentials.
I also installed Firefox (although she only uses IE).

I also set-up the network and everything was fine running perfect until 3 days ago when she couldn't connect to the internet through IE.

She called SHAW Cable Support who monitored the connection, saw her router was getting an IP and communicating but had no idea why she couldn't connect so she called me.

Typing any domain name into either Firefox or IE would not connect, (Site could not be found)
IPCONFIG is good. Has been released/renewed, and I even tried changing the DNS server from the gateway to the ISPs
In all cases NSLOOKUP, PING, TRACEROUTE are able to resolve the domain name and return the IP.
The DNS client is running.
Neither browser can resolve domain names.
Both browsers work fine if I enter the IP address, the problem is with name resolution.

I thought it might be remnants of Norton left on the system so I used Norton's own 'Complete Removal' system to remove all traces.
It left no files/folders/registry entries and indicated success.
After a reboot... still same problem.

Windows network diagnostics indicates that it cannot find the problem.

I verified that no proxy was selected.
I disabled Microsoft's firewall.. problem still present after reboot.
I checked the HOSTS file.. intact but no entries.
 * I actually tried adding an entry for google.com into hosts to see if that would work but it didn't.
I tried booting in safe mode with networking.. still no name resolving on either browser.
I reset winsock (netsh winsock reset)... that did not fix the problem.
I thought maybe IPv6 problem, disabled that protocol.. no change, problem still there.
I also toggled network.dns.disableIPv6 in Firefox's about:config screen and tried that to ensure IPv6 was not the problem... no change
I flushed the DNS 'ipconfig /flushdns' several times through this and at no time did it make a difference.

I rolled back to before the last update (at which point the system was working) and still have the same problem.

Other than re-installing Windows which means I would have to set up the network and MSSecurity again, I have no ideas.
-------------------------

Any ideas?
  - Kent

Hi Kent_L,

 

I would suggest you to open Microsoft website by typing the IP address in the address bar and check.

 

a.       Open Internet Explorer

b.      Type the following in the address bar and press Enter

207.46.19.190

If it displays www.microsoft.com website then you may have to contact the Internet Service Provider (ISP) to reset DNS settings.

 

Hope this information helps.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Of course it connects to Microsoft.
And I can ping Microsoft using the domain name which resolves correctly so it isn't a dns server issue.
Windows 7 resolver is working... for everything except browsers... well' and eMail
All command line tools work as expected.
All GUI applications (IE, Outlook, Firefox) are failing to resolve domain names.

All other computers on the net are having no issues.

That would seem to be a problem with the stack but I reset that with no effect.
----------------------------

It looks like the simplest solution to this problem is ripping out the Win7 network completely and letting it re-install.

Unfortunately, it's time consuming to set-up the network again and if I don't find the problem there is nothing to prevent it from happening again.






Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I realize this is an old post, and I'm sure (or hope) that you've fixed the issue but, for others still trying to fix this problem, what FINALLY solved my problem with resolving domain names into IP addresses was that, somehow, my computer's name (while in Win7) had been erased.  I re-entered the original name I gave it and, voila! - it works!  I can now completely access the internet, again!  So, to sum up, right-click the "Computer" icon, left-click "Properties".  Select "Computer Name" and see if there's anything in that field.  If not, enter something, click "Apply" and click "OK" to reboot the system.  Hopefully this will solve your issue, too.  Good luck and good hunting!

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

As of 5 minutes ago I went to check on my local host file and the only thing I found that was modified recently was a file call host.ics which appeared to be some icalendar.  I looked at the file and found ip's that didn't match.  I didn't want to removed the file temporaly incase the file was needed.  As soon as I removed the file I was able to resolve both bing.com and google.com which were not working unless I used their ip's in the browser.

My problem was only noticed in browsers.  I was not able to resolve dns names but the IP would work.  I was able to temporary fix the problem by run command prompt as an admin and flushing the dns(ipconfig /flushdns).  I will report back later if problem continues.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated June 13, 2022 Views 3,617 Applies to: