Diagnosing connection issue

[edwardp-jjFNsPSvq+iXDw4h08c5KA at public.gmane.org (edwardp-jjFNsPSvq+iXDw4h08c5KA at public.gmane.org)]

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.

 


 

-----Original Message-----
From: Tom Metro <tmetro-blu-5a1Jt6qxUNc at public.gmane.org>
To: edwardp <edwardp-jjFNsPSvq+iXDw4h08c5KA at public.gmane.org>
Cc: L-blu <discuss-mNDKBlG2WHs at public.gmane.org>
Sent: Tue, Feb 15, 2011 1:03 am
Subject: Re: Diagnosing connection issue


edwardp wrote:

> And even after this, it occurred again, this time it was at least a full 

> minute before the page(s) started loading in.



So when it happens, have you attempted to run trace routes?



One approach I've used to catch intermittent problems like that is to do

a trace (to www.google.com or some other public site) and identify the

IP address of the nearest 3 or 4 hops. Whatever takes you to the first

backbone router. Then I setup a ping command for each IP, logging to a

file, and using appropriate options so the ping rate is low enough not

to bother anyone.



(Technically, I don't use the ping command, but a Perl module for

sending ICMP and UDP packets and a custom connectivity monitoring

script, but the principle is the same.)



 -Tom



-- 

Tom Metro

Venture Logic, Newton, MA, USA

"Enterprise solutions through open source."

Professional Profile: http://tmetro.venturelogic.com/