ml>ml> ping sucks for diagnostics... use traceroute but understand that,
ml>ml> like ping, not all systems will respond... traceroute will get you
ml>ml> responses from systems in the path whereas ping doesn't and so
ml>ml> doesn't give any idea where the breakage may be...
 
ml>RN> From personal experience, I have to disagree with the above about
ml>RN> TRACERT.
 
ml> why disagree? i should think you would be agreeing because TRACERT
ml> definitely showed where the breakage was... you were able to report it...
ml> and it got fixed... ping cannot give the type of information necessary
ml> for this...
 
I "misinterpretated" what Roy wrote, then.  (-:[
 
ml>RN> In October of 2010 when everybody was having trouble with
ml>RN> a direct connect to me, in every instance I had various people
ml>RN> running that program and it ALWAYS hung at the same locale in the
ml>RN> path to here.  When I informed the $5 per hour geniuses at AT&T
ml>RN> what that address was and how often the traces stopped there, I
ml>RN> must have been (finally) speaking to someone with a modicum of
ml>RN> intellect because by the end of that month, the problem went away.
ml>RN> I think some of you may remember that.  Those of you who do, let me
ml>RN> just say I couldn't have done it without you.
 
ml> yes, i was one of those... more than once ;)
 
Yes, you were.

ml> you are welcome for the assist :)
 
Thanks again, )\/(ark.  :-)
 
 
Regards,
 
Roger

--- D'Bridge 3.78