Wednesday, October 29, 2008

Fix: Can't connect to any sites with a 64.x.x.x IP address

Yesterday, my wife Melissa noticed a problem with our home Internet connection: certain websites, including my own, would not load. The browser would get past the "looking up..." step (so DNS resolution was working fine), but the website would simply never respond to the HTTP request, and the browser would eventually give a "Network Timeout - The server at [site] is taking too long to respond" error.
Timeout screen cap
Troubleshooting the issue this evening, I started to notice a pattern in the sites that were working, versus those that were not working:

Working Sites

SiteIP Address

Non-Working Sites

SiteIP Address
Did you spot the pattern? (If not, take a closer look at the IP addresses.) Once I started looking at the IP addresses of the working sites versus the non-working sites, it quickly became obvious: Attempts to connect to sites with 64.x.x.x IP addresses were not working, whereas all other sites that I tried worked just fine. I had never heard of an issue like this before. I initially didn't really have a good idea where along the pipeline of [Client PC] - [Router] - [Cable Modem] - [ISP] - [Internet] - [Web Server] the problem was likely to be.

It wasn't just http requests that were failing; I couldn't successfully ping, tracert, or connect via ftp to any of the "non-working" sites, either. I was able to successfully connect to some of the sites from work; plus, given that if a site like the homepage had any significant downtime at all it was likely to immediately be big news, and there had been no such news, I was able to rule out the web server as the problem. I was able to reproduce the problem on a couple of different client machines and different web browsers from home, so that (most likely) ruled out the client PC as the issue. My suspicion at this point was some kind of problem at the ISP level; I figured that since I was able to browse some websites with no problem at all, my router and cable modem must be ok.

This turned out to be a bad assumption. I had tried "rebooting" the cable modem (by disconnecting the power, waiting a couple of minutes, and then reconnecting) early in the troubleshooting process, but that step had had no effect. Throughout the process, I had assumed my router was ok. However, when I used the router's browser-based administration application to try and perform a release/renew on its Internet IP address, and the application simply stopped responding after the new request, I immediately (and to my chagrin, for the first time) suspected some kind of problem with the router. I cycled the power on the router (unplug, wait briefly, plug back in), and that turned out to be the solution! Immediately, all of the 64.x.x.x sites were working fine once again.

I'm still not sure why cycling the power on the router was the solution to the issue, except that to guess that apparently, after weeks (or maybe even months) of uptime, the router had managed to get itself into a bad state, and cycling the power was enough to refresh whatever internal memory the router has back into a good state. Hopefully, this post will be a time saver for anyone else out there who manages to run across this issue -- at least, so long as this blog doesn't get changed to have a 64.x.x.x IP address! :-) I have had various problems with this router -- a Linksys BEFW11S4 Wireless-B that's now over a couple of years old -- before (1, 2, 3). I think it may be time to start keeping my eyes open for a sale, and jump on a deal to replace this router when the right deal presents itself.


  1. Thank you so much for this post, you are my hero right now. For about two weeks I haven't been able to connect even to AIM, and in my hunt I figured out it was all 64.x.x.x sites that weren't working, just like for you. Your method worked like a charm. I no longer need to live in and the google cache! Thank you again!

  2. @Anonymous - I'm glad this was helpful! :-)

    If you happen to visit again, I wonder if you could comment on whether your router is a Linksys BEFW11S4, or a different model?

  3. I can confirm having the same problem on a Motorola WRT850 Wireless hub connected to the WAN via my ISP supplied Thompson/RCA CM.

    I usually cycle modem power religiously (yes, your cable modem and network hub have internal caches that can stand being cleared out once in a while) and when I saw this post remembered I hadn't done it in a while.

    Thanks for the reminder, worked great.

  4. Today, internet technology is advancing, whether you realize it? Why not, most people is needed the internet for their works. This internet advances, strongly felt by internet marketer, student, office, or large companies. Information’s in the internet unlimited almost all of them there. Internet also is resource for internet marketer and science resources for student. For traders, the internet is where their product promotions. Many people were success by business at the internet. High speed internet access is most the important to do business on the internet. That is my opinions about internet technology, and how about you?.. Tips and trick Router Setup


Non-spammers: Thanks for visiting! Please go ahead and leave a comment; I read them all!

Attention SPAMMERS: I review all comments before they get posted, and I REPORT 100% of spam comments to Google as spam! Why not avoid getting your account banned as quickly -- and save us both a little time -- by skipping this comment form and moving on to the next one on your list? Thanks, and I hope you have a great day!