| Traceroute:
Analyzing Your Connectivity
If
a web site cannot be accessed, or if web site access
seems to be slow, there are many things that could be
causing this to happen. The first thing to do is to
run a traceroute, so that you can review what is happening
between you and the web server.
Some common reasons tracrt would find a slow connection
could be that a router is down and the system must foward
much of the traffic to another router, or the web server
is getting "bogged down" by the amount of
traffic that is being submitted to it.
By
running a traceroute, you can review the number of hops
and the time it takes to reach a particular destination
on the web. You can also view where in the route you
are experiencing a slow connection or if there is a
dropped connection.
To
perform a traceroute, open a DOS window on your computer
(you must also have an active internet connection),
and type:
or
alternatively
Using the above command, your computer will begin to
follow the route from your internet connection to the
server at your destination site. Below is an example
of a typical traceroute result. In this case, we typed
in: tracert ibm.net
Tracing route to www.ibm.net [204.146.17.5]
over a maximum of 30 hops:
1 10 ms <10 ms 207.213.224.1
2 10 ms 20 ms GA0F80.GR-1.LosAngCA.savvis.net
3 <10 ms 10 ms 908.Hssi4-0.GW1.LAX1.ALTER.NET
4 20 ms <10 ms 105.ATM2-0.XR2.LAX4.ALTER.NET
5 10 ms 10 ms 192.ATM3-0.TR2.LAX2.ALTER.NET
6 10 ms 20 ms 111.ATM7-0.TR2.SCL1.ALTER.NET
7 20 ms 10 ms 198.ATM6-0.XR2.SFO4.ALTER.NET
8 30 ms 20 ms 190.ATM11-0-0.BR1.SFO1.ALTER.NET
9 20 ms 20 ms 165.87.225.26
10 20 ms 30 ms 165.87.33.132
11 100 ms 100 ms 165.87.230.190
12 100 ms 80 ms scha34-48-fddi1.il.us.ibm.net
13 100 ms 110 ms www.ibm.net [204.146.17.5]
Trace complete.
In
the above example, the connection slows down on the
11th hop. That series of three slow responses could
potentially cause a slow connection to ibm.net. Anything
under 250 ms is considered acceptable. If you hit a
backbone connection that is down, the result will read:
TIMED OUT * * *
Note that
the results of every traceroute will differ, depending
on your current connection, routing, and time you ran
the traceroute. For example, the same traceroute can
take a very different path, even ten seconds later
Webmail | Search
Terms
of Service | Privacy
Statement
© 1995- 2005, Stealth
Media Solutions, Inc. All rights reserved.
(888) 557-5282
For more information, questions, or comments, send email
to: info@StealthAccess.net.
|
