Bill Bogstad wrote: > On Tue, Feb 15, 2011 at 6:22 AM,<[email protected]> wrote: > >> I have not as yet tried a traceroute when this occurs, but will do so the >> next time. I have not experienced this same issue on my laptop using a >> wireless connection. >> >> But even when this occurs, /if/ the problem is further downstream, past the >> cable modem, at least the modem and router status pages should have no >> trouble coming into the browsers and they are not even doing that when this >> problem occurs, yet they ping fine during all this. >> > You didn't say that before. So if you ping the modem and router they > are "fine"; but accessing their web pages fails? Try doing a simple > "telnet ipofdevice 80" to bypass DNS or web browser issues and see if > you can get a connection to the devices web pages. You can even try > sending HTTP commands to the device via telnet and see if you get > results. If this works, but your web browser can't connect to the > devices web pages then it is beginning to sound like it is a problem > with > your local system software. > > Bill Bogstad > > P.S. What do you mean by fine for ping by the way? Try a ping flood > "ping -f" as well. Also you might try getting Matt's traceroute > (mtr). It's a screen based version > of traceroute can be very nice for diagnosing network connectivity > issues (which it might not be in this case). >
Ping fine = goes through without any packet loss, immediate response. Traceroute also went through during an "outage". Did not try telnet, but I have now disabled IPv6 on the Linux (via sysctl.conf) side to see if that makes any difference. _______________________________________________ Discuss mailing list [email protected] http://lists.blu.org/mailman/listinfo/discuss
