My wifi connection (from my MacBook running Snow Leopard) to a Time Warrner cabel model and router has a recurring connection problem. Every 20 minutes or so it will enter a "dead state" where no data can be transfered and yet pings still work:
$ ping linkedin.com PING linkedin.com (22.214.171.124): 56 data bytes 64 bytes from 126.96.36.199: icmp_seq=0 ttl=245 time=13.029 ms 64 bytes from 188.8.131.52: icmp_seq=1 ttl=245 time=16.214 ms 64 bytes from 184.108.40.206: icmp_seq=2 ttl=245 time=16.221 ms 64 bytes from 220.127.116.11: icmp_seq=3 ttl=245 time=15.778 ms 64 bytes from 18.104.22.168: icmp_seq=4 ttl=245 time=16.220 ms ^C --- linkedin.com ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 13.029/15.492/16.221/1.243 ms $ telnet linkedin.com 80 Trying 22.214.171.124... GET /
Notice the successfull pings to linkedin.com but trying to make an HTTP GET on port 80 hangs. A few minutes later:
$ telnet linkedin.com 80 Trying 126.96.36.199... Connected to linkedin.com. Escape character is '^]'. GET / HTTP/1.0 200 Content-Type: text/html Content-Length: 349 Connection: close Date: Tue, 07 Jun 2011 11:38:21 GMT Server: lighttpd
In the dead state I don't get:
Connected to linkedin.com. Escape character is '^]'.
Any idea what the problem is and how to fix? I can power cycle the modem and turn wifi on/off and it eventually comes back. But it comes back from a dead state after just waiting a few minutes too. My goal is to get a solid 24/7 connection that never has these dead periods. This has nothing to do with linkedin.com BTW, all sites have the same problem during the dead period.
More info from router logs:
Mon Jun 06 09:12:22 2011 Error (4) DHCP RENEW sent - Invalid DHCP option Fri Jun 03 14:51:21 2011 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out Time Not Established Critical (3) DHCP FAILED - Requested Info not supported. Wed Jun 01 12:36:00 2011 Critical (3) DCC aborted unable to communicate on new upstream channel Wed Jun 01 12:36:00 2011 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout