Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

When I browse localhost in my browser when connected to the Internet, the response is slow; it takes 30 seconds or completely times out. When I disconnect from the Internet, it is blazing fast and loads instantly.

What is going on? This is very annoying. I'm using Windows 7 Home Premium with Apache installed.

No changes have been made to the system.

share|improve this question
    
How about your network setting ? –  matzone May 14 '13 at 8:08
    
@matzone: What network setting? –  Erwinus May 14 '13 at 13:57
    
Your TCP/IP setting .. I don't know much about this, but mostly occured in DHCP setting .. –  matzone May 14 '13 at 16:30

3 Answers 3

What's probably going on when you are connected to Internet is that your system tries to resolve name localhost in yours ISP DNS servers.

As a solution you can define name localhost as IP address 127.0.0.1 in your hosts file which is read before querying DNS servers. Since you have Windows 7 you should have required entry in C:\Windows\System32\drivers\etc\hosts file but by default it's commented out. Start Notepad as Administrator by right-clicking on it and choosing Run as Administrator. Open your hosts file and change lines:

#   127.0.0.1       localhost
#   ::1             localhost

to:

127.0.0.1       localhost
::1             localhost

Basically uncomment it by removing # from the beginning of these two lines. Save the file and test if it resolved your problem.

share|improve this answer
    
I appreciate your answer, but already tried that without success! One said that to remove it and the other said to add it. It makes really no sense to the problem. –  Erwinus May 14 '13 at 13:56
up vote 2 down vote accepted

Al right, it seems no problem of the system itself, windows or network but remove some hidden networkcard configurations from the past and disable all WAN-miniports in the hardware configuration that increases the speed a little.

But that was not the problem causing the long delays when connected to the internet. In the php code there was some cURL code that connects to a slow site to get some additional useragent info (REST interface). Because the data was not cached and the site access slow down in time for some reason, it connects to this slow site for each part of the webpage. This caused the long delays.

Now it is cached, the problem no longer exists. Thanks for the input anyway.

share|improve this answer

I know that this question has been closed but I wanted to add my experience to this knowledge base as it might help someone else that encounters, has I did, multiple problems while resolving this issue.

I also suffered from very slow localhost and while trying to resolve this issue, I experienced a lot of other complications to the resolution of this problem.

I first discovered that other software wrote their own information in my host file...

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost

# 127.0.0.1 localhost

#127.0.0.1 3dns.adobe.com 3dns-1.adobe.com 3dns-2.adobe.com 3dns-3.adobe.com 3dns-4.adobe.com # activate.adobe.com activate-sea.adobe.com activate-sjc0.adobe.com activate.wip.adobe.com #127.0.0.1 activate.wip1.adobe.com activate.wip2.adobe.com activate.wip3.adobe.com>
activate.wip4.adobe.com adobe-dns.adobe.com adobe-dns-1.adobe.com adobe-dns-2.adobe.com adobe-dns-3.adobe.com adobe-dns-4.adobe.com
#127.0.0.1 adobeereg.com practivate.adobe practivate.adobe.com practivate.adobe.newoa practivate.adobe.ntp practivate.adobe.ipp ereg.adobe.com ereg.wip.adobe.com ereg.wip1.adobe.com
#127.0.0.1 ereg.wip2.adobe.com ereg.wip3.adobe.com ereg.wip4.adobe.com hl2rcv.adobe.com wip.adobe.com wip1.adobe.com wip2.adobe.com wip3.adobe.com wip4.adobe.com
#127.0.0.1 www.adobeereg.com wwis-dubc1-vip60.adobe.com www.wip.adobe.com www.wip1.adobe.com
#127.0.0.1 www.wip2.adobe.com www.wip3.adobe.com www.wip4.adobe.com wwis-dubc1-vip60.adobe.com crl.verisign.net CRL.VERISIGN.NET ood.opsource.net

It seems here that Adobe had something to do with my problems ... ;-)

To resolve this issue, I had to uncommented one of these lines (get rid of # sign
# 127.0.0.1 localhost
And comment all Adobe lines (add # sign) before restarting my computer.

That seemed easy to do but Win7 didn't want me to save the host file saying that it was used by an other software even if I had started notepad as an administrator...?

The only way I found to edit this file was to retart my computer in safe mode (using F8 at startup), but when I tried, I found that this feature did not work on my computer (I'll need to find why later...).

The other way to start in safe mode was to preconfigure Win7 to start in Safe mode using msconfig (find the way here How to Start Windows in Safe Mode). This being done I was able to edit my host file and make proper corrections..

Don't forget, while in safe mode, to reconfigure Win7 to start in standard mode using msconfig before rebooting your computer...

After applying these corrections, my localhost regain its "vitality" and displayed all pages in a blink of an eye...

I hope that my modest contribution helps brighten your day...

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.