Subject: | |
From: | |
Reply To: | |
Date: | Wed, 10 Nov 1999 03:39:07 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On 9 Nov 99, at 22:04, Yui Shin wrote:
> David A. Abbe wrote:
>
> > Tracing route to mail.ionet.net [206.41.128.16]
> > over a maximum of 30 hops:
> >
> > 1 125 ms 116 ms 93 ms bartnas1.ionet.net [38.193.96.3]
> > 2 150 ms 122 ms 99 ms nbbart.ionet.net [38.193.96.1]
> > 3 173 ms 124 ms 149 ms tul-bart-link.ionet.net [206.41.130.49]
> > 4 135 ms 137 ms 150 ms mail.ionet.net [206.41.128.16]
> >
> > Trace complete.
>
> Your modem sent 3 test data packets to determine how many servers it
> connects to before reaching the destination and their lag times.
> I ran the same tracert and I hit 4 Earthlink servers, 2 routers, and 2
> servers
> in your Ionet before final destination www.ionet.net.
> If you have to make 13 or more hops to connect that's too many.
> Also, if you experience high lag times with your ISP all the time you may
> want to change.
> Your results look fine.
>
> I'm glad you tried it.
> Now try it on web sites you frequently have delays and determine if the
> high lag times are from your ISP or the rest of the world.
There's a nifty shareware (freeware?) utility out there called
"Ping Plotter" that uses the traceroute mechanism, but graphs the
numbers -- and colours them green, yellow, or red depending on how
"acceptible" they are. Keeps a list of places you've tried
recently....
David G
The PCBUILD web site always needs good submissions. If
you would like to contribute to the website, send any
hardware tech tips or hardware reviews to:
[log in to unmask]
|
|
|