Windows 7: NoSurf: Can't reach websites via browsers on 1 of 2 PCs on network.

I have 2 computers on my home network:
#1 computer can receive email via POP3, can Ping www.sevenforums.com, but can't reach websites via browsers.
#2 computer can reach websites via browsers.

First, via system restore, I restored computer #1 to one earlier time, then another. That didn't solve it.

Second try, I powered down the modem and router and let them sit for 10 minutes before reconnecting power. But, that didn't solve it.

Next, I followed the instructions to upload an image of my IPCONFIG (see attached) and ran FlushDNS.bat as an administrator.

I still cannot browse the internet on #1 computer. Your help will be greatly appreciated!


In case it matters:
Computer #1 is hardwired to router. Runs current Win7 64-bit.
Computer #2 has a wireless connection to router. Runs current Win7 32-bit.

Could be a proxy setting in IE. See here: How to reset your Internet Explorer proxy settings

Thank you!!!
I replaced C:\Windows\System32\drivers\etc\hosts
with a version from 2 months ago, and I can surf again!

posted by Don:

Just checked and the attributes fro my hosts file are SHR (System, Hidden, Read Only).

It happened again - this is the third time:
I could once again surf after the usual fiddling with the (seemingly unchanged) HOSTS file, flushing dns cache, rebooting. Is there a way to determine why the problem recurs, or if the HOSTS file is not the real problem?

P.S. The HOSTS file attributes are SHR.

For this problem usually resetting the network stack and resetting winsock will fix it. Just save the file, unzip and let it run till your system reboots. I should also mention that the Windows 7 recovery feature is not the best way to restore your system. Every time I used it in the past something was always messed up. I seem to have much better luck with system images using the Windows 7 file recovery.

You might also want to remove the DNS entries from your IPv4 properties window and then type the DNS servers into the routers settings for DNS instead.

Thank you for the solution! I actually look forward to the problem recurring so I can use your proggy to solve it.

If the problem returns it's most likely an out of date driver or third party program that is causing it, you can always run the IP reset file again to fix it.

The IP reset file I posted will fix most every problem related to IP's but it may come back due to what I just mentioned.

"They're ba-ack..." Recently the problem has returned. Sometimes several reboots via IPResetALL.exe are required before a browser can load a webpage. Does the requirement for several reboots suggest that the random order of starting processes at boot is what's working rather than IPResetALL? Is this a clue to the root cause?