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.

Okay it's a bit tough to figure out where to start from, but here is the basic summary of the issue:

During general internet usage, there are times when any attempt to visit a website stalls at "Waiting for somedomain.com". This problem occurs in Firefox, IE and Chrome. No website will load, INCLUDING the router configuration page at 192.168.1.1. Curiously, ping works fine, and other network apps such as MSN Messenger continue to work and I can send and receive messages. Disconnecting and reconnecting to the wireless network seems to fix the problem for a bit, but there are times when it relapses into not loading after every 2-3 http requests. Restarting the router seems to fix the issue, but it can crop up hours or days later.

I have a CCNA cert and I know my way around the Windows family of operating systems, so I'm going to list all the things I've tried here.

  • Other computers on the network seem to suffer the same problem, which makes me think it might be a specific problem with something in Win7. The random nature of this issue makes it a bit difficult to confirm, but I can definitely say that I have experienced this on the following systems:
    • Windows 7 64-bit on my desktop
    • Windows Vista 32-bit on my desktop ( the desktop has 2 wireless NICs and the problem existed on both )
    • Windows Vista 32-bit on my laptop ( both with wireless and wired )
    • Windows XP SP3 on another laptop ( both wireless and wired )
  • Using Wireshark to sniff packets seemed to indicate that although HTTP requests were being SENT out, no packets were coming in to respond to the HTTP request. However, other network apps continued to work i.e I would still receive IMs on Windows Live Messenger.
  • Disabling IPV6 had no effect. Updating router firmware to the latest stock firmware by Linksys had no effect. Switching to dd-wrt firmware had no effect. By "no effect" I mean that although the restart required by firmware updates fixed the problem at the time, it still came back.
  • A couple of weeks back, after a LOT of googling and flipping of various options, I figured it might be a case of router slowdown ( http://www.dd-wrt.com/wiki/index.php/Router_Slowdown ) caused by the fact that I occasionally run a torrent client. I tried changing the configuration as suggested in that router slowdown link, and restarted the router. However I have not run the torrent client for 12 days now, and yet I still randomly experience this problem.

Currently the computer I am using is running Windows 7 64-bit. I would just like to reiterate some of the reasons that I was confused by the issue.

  • Even the router config page at 192.168.1.1 would not load, indicating that it's not a problem with the WAN link, but probably a router issue or a local computer issue. For some reason, disconnecting and reconnecting to the wireless network immediately seems to fix the problem.
  • Updating the router firmware, even switching to open source firmware did nothing. So it seemed to be a computer issue.
  • On the other hand, I have not seen any mass outrage of people having networking problems with Windows 7 and Linksys routers, especially a problem of this sort, and I have tweaked every network setting I could think of.
  • Although HTTP seems to have trouble, ping works fine, DNS lookups work fine, other networking apps work fine. However if I disconnect from Windows Live Messenger and try to reconnect, it fails to reconnect. So although it could receive data over the existing TCP/IP connection, trying to start a new one failed?

Does anyone have any further ideas on debugging or fixing this issue? I am reasonably certain there are no viruses or other malicious apps on my network, and I am also reasonably certain that nobody is accessing my router without my consent.

Router: Linksys WRT54G2 1.0 running dd-wrt firmware
Wireless Card: Alfa AWUS036H
OS: Windows 7 64-bit

EDIT: I tried switching to a clean wireless channel free from interference, but the problem still persisted. I tried connecting directly with a cable, but the problem still persisted.

share|improve this question
    
+1 for doing your homework and writing a very clear and concise question! –  marcusw Mar 21 '10 at 13:11
    
Have you tried another router? And do you have QoS turned on? –  harrymc Sep 14 '10 at 20:30
add comment

6 Answers

Have you tried using ethernet directly to see if it still happens? If it does we can rule out anything to do with wireless directly. Try watching your signal strength when the issue occurs, it could be interference. I have a friend who's wireless signal would cut drastically, allow existing connections to work, and prevent any new connections from being made when he or his wife opened their garage. Changing the channel the router was using fixed the issue. (Their garage frequency was on the equivalent of channels 6 and 7 on 802.11b/g)

share|improve this answer
    
I'm grabbing netstumbler to see what channels I'm getting interference on. I will update asap. –  Rohit Nair Dec 2 '09 at 20:35
    
Okay netstumbler didn't work with my wireless card, but I found another wireless monitoring software, and apparently there are 8 other wireless networks on the same channel that mine is on. xD The ISP provides the routers here so I'm guessing everyone just set theirs up directly out of the box, thus ending up with everyone on the same channel. Hopefully this should fix the issue. –  Rohit Nair Dec 3 '09 at 12:26
    
Nope, issue came back a few minutes later. Grrrrrrrrrrrrrrrrrr –  Rohit Nair Dec 3 '09 at 12:34
    
Yep. Tested using an ethernet cable as well. The problem still persisted. Attempting to access the router config page just led to "Waiting for 192.168.1.1...." forever, and similar results for other websites. –  Rohit Nair Dec 4 '09 at 14:37
    
Since you mention that the problem really only exists with HTTP calls, does the router have any sort of web content filtering/url filtering options? If it does, try turning them off. Otherwise, have you been able to try a different router with your network? It could be bad hardware. –  Joshua Dec 7 '09 at 0:18
add comment

Ok, this may give you a hand in troubleshooting, you need to determine if it is your computer or the router first.

Run ipconfig /all on the cmd line firstly to check.

  1. Ping 127.0.0.1 - If the ping fails, your tcpip stack is basically screwed and will require a reinstallation of the networking components.
  2. If #1 works, then try pinging your network card which as an IP address (maybe linksys acts as a dhcp server) for example ping 192.168.1.2 - this is to determine if your NIC is functioning. If the ping fails, time to get a new NIC.
  3. If #2 works, then ping the linksys router, if you cannot ping the router then the problem is on the router itself.
  4. If #3 works, can you load the router's web page on your browser? If it doesn't its obviously something in your browser - a recently installed add in (these are notorious for clogging up the browser to the point of making it malfunction). Or try telnet into the router's website address telnet 192.168.1.1 80 and even though nothing appears as you type, type this in GET HTTP1.1/index.html, if you do get output in the form of html code on your screen, the mini-web server on your router is functioning. If this check passes, and you cannot do it on your browser, then the browser is the problem.
  5. Now that you've reached this far, ping the ISP's address, if that fails, then the router cannot find the ISP..perhaps the arp cache got reset or the dns entries held in the router's memory is lost.

You did mention that having to disconnect and reconnect fixes this, I suspect two things here, the ports somehow are failing to recognise the MAC's and hence internal lookups for DNS fails which implies disconnect/reconnect 'activates' the lookup of the NIC's MAC...the other is the cables - check your cables here...

If #5 passed, then you can place the bet somewhere that the ISP's system is messed up, i.e. DNS errors being propagated back to your router hence making it look like the source of the problems, try forcing your dns to use open-dns or dyn-dns.

Hope this helps, Best regards, Tom.

share|improve this answer
    
When I said to check the cables I realized you were talking about wireless, so check the signals, there could be a interference in the signals or something blocking it (microwave ovens, cement walls etc). Usually switching to channel 11 remedies the wireless signal issues, please try that. Hope it helps and sorry for the confusion about the cables that I mentioned above. –  t0mm13b Dec 2 '09 at 15:04
    
As I mentioned in my post, ping/dns lookups on any site work. However attempting to load the site in a browser stalls at "Waiting for google.com". Again, for the telnetting bit, as I mentioned in my post, I ran a packet sniffer to see what was going on, and it detects an outgoing request but no response. Manually telnetting has the same result. It opens the connection and lets me type "GET / HTTP/1.1" but I don't get a response. As I told the other person, I'm grabbing netstumbler to check wireless interference now. –  Rohit Nair Dec 2 '09 at 20:37
add comment

I had similar issues with 2 different systems using a particular USB adapter that I had. I would suggest trying a different adapter or a wired connection. You could also try trading that adapter with another system's on the network and see where the problem goes.

share|improve this answer
    
I have experienced this problem on 3 OSs. Win7 64-bit on my desktop, Vista 32-bit on my desktop ( the desktop has 2 wireless NICs and I have tried them both ) and Vista 32-bit on my laptop. The problem still persisted. Attempting to access the router config page just led to "Waiting for 192.168.1.1...." forever, and similar results for other websites. –  Rohit Nair Dec 4 '09 at 14:38
add comment

I was running into precisely this same problem with similar hardware (Linksys WRT54G2v1.0, but MacBook Pro), and went through all the same gymnastics you did, with little or no success.

By luck, I managed to discover the root of the problem in my case: it's wireless interference from another device in our house. (In my case, it was the baby monitor -- but cordless phones seem to be another likely culprit.) Did you recently get a 2.4 GHz phone, or did one of your neighbors (if you live in an apartment building)? Either way, there's a really easy fix: change the wireless channel your router is using. In my case, this completely solved the issue.

share|improve this answer
add comment

This is old now, but one possibility to explore is to check the proxy settings in internet properties. For Windows XP:

Start Menu -> Control Panel -> Internet Properties -> Connections tab -> Lan Settings button -> make sure the Automatically detect settings option is not checked.

share|improve this answer
add comment

I had a similar problem:

Windows 7 64 bit and a Linksys router. I could ping any addresses but the nslookup gave me a "request timed out". This was with the default IP address 192.168.1.1 set in the Linksys router. The problem was there even when I connected with a cable.

when I changed the Linksys IP address to 10.120.0.1 everything works fine.

share|improve this answer
add comment

protected by studiohack Apr 27 '11 at 0:59

Thank you for your interest in this question. Because it has attracted low-quality answers, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

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