Ok, so when I try tracert www.ionet.net as below, what am I supposed to be
looking at?  There are three columns to stare at.
Sending/Waiting/Receiving?  heck if I know.... This has been interesting to
hear about.  Thank You

P.S.  this was the shortest of all of them, presumably due to their close
proximity, ~200 miles away.  I tried microsoft.com but after a few 500ms
readings it timed out.


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.

Thanks again, hopefully this isn't supposed to be a duh answer, cuz I don't
know it...

David A. Abbe
[log in to unmask]


> access earlier versions of tracert.exe is still a good free
> way to find out if your ISP has high lag times. Otherwise,
> worst scenario: lag times may show readings which are
> too low that should have timed out.
>
>    100ms or better to play games on the internet.
>    125ms is what I refer to as par.
>    200ms or over is a red flag.

                         PCBUILD's List Owner's:
                      Bob Wright<[log in to unmask]>
                       Drew Dunn<[log in to unmask]>