On your computer:
- Click Start and then Run
- Type cmd and press Enter
- In the command window, type 'tracert 69.41.234.242 > C:\tracert.txt'
(without the quotes) and press the Enter key.
- Type exit and press the Enter key to close the command window.
A file will be created on your C: drive called tracert.txt that
contains your Traceroute information. Please be patient when waiting for the
tracert command to complete, it may take several minutes. When you are
returned to the command prompt, then the trace is complete.
If you are having problems and you believe it is our server, then send us this file. If you think it might be on your ISP or your computer side, here is how you can analyze the results.
Open the tracert.txt file. You will see 3 kinds of information regarding the
route that internet traffic is taking from your computer to your web server:
1. The number on the far left is the hop number.
2. The next 3 numbers (with 'ms' after each one) is the length of time, in
milliseconds, it takes for your computer to receive a response from the
computer you are trying to contact. A high value, for example greater than 200
ms for broadband or 350 ms for dial-up, indicates that traffic is slow, and
can cause latency or 'laggy' play. Asterisks (*) indicate that your computer
did not receive a response from the computer you are trying to contact at all,
which can keep you from connecting to our servers altogether, or cause you to
be disconnected abruptly.
3. The final piece of information is the DNS (or 'name') and/or the IP
number of server you are trying to contact on this hop. If you did not receive
any responses from this server, you may receive an error message such as
'Request Timed Out' or 'Destination Net Unreachable'.
Some error messages and what they mean:
Error Message:
"The server does not have a DNS entry" (Netscape) or "A
connection with the server could not be established" (Internet Explorer).
Explanation:
The domain name is not being resolved.
Possible reasons:
Your domain name registration has not been completed by the
InterNIC.
Your domain name has been registered, but the name has not
propagated through the main root servers on the Internet. Wait 24-72 hours and
your domain should then be working.
Your computer has lost the connection to your Internet Service
Provider. Make sure your are connected to your ISP.
You are connected to your ISP, but there is a problem with their DNS
servers. If you cannot reach many sites this is probably the problem.
You are connected to your ISP but there is a routing problem
somewhere between you and us. Tips on how to diagnose this are below.
Error Message:
"There was no response. The server could be down or not
responding" (Netscape) or "A connection with the server could not be
established" (Internet Explorer)
Explanation:
No connection could be made to the server.
Possible reasons:
You are not connected to your Internet Service Provider. Check your
connection to your ISP.
You are connected to your Internet Service Provider but there is a
routing problem somewhere between you and us. Tips on how to diagnose this are
below.
The web server could be down. Check our network notices page.
Your individual web site could be down. This can happen on a
Microsoft® FrontPage® enabled web sites if your connection to the web server
did not terminate properly after publishing to your web site. This can also
happen if an error occurs while publishing with Visual Interdev.
Here's an example of a successful tracert to www.arrowwebsites.com:
Tracing route to arrowwebsites.com [69.41.234.242]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms 20.17.1.254
2 <10 ms 16 ms <10 ms 20.6.29.9
3 <10 ms <10 ms 15 ms nwkrtr01-v305.de-sil.tst.com [20.6.29.5]
4 <10 ms 15 ms 16 ms ignenclwk3-v804.amer.tst.com [20.6.120.1]
5 <10 ms 15 ms 16 ms 192.168.100.34
6 <10 ms 16 ms <10 ms 20.136.32.18
7 <10 ms 15 ms 16 ms IGNRTRNWK1ige-0-2-0v112.amer.csc.com [20.137.6.2]
8 15 ms <10 ms 16 ms so-2-0-2.ar2.phi1.gblx.net [208.49.224.117]
9 47 ms 47 ms 47 ms so1-0-0-2488m.ar1.dal2.gblx.net [67.17.73.34]
10 47 ms 47 ms 47 ms the-planet.ge-0-2-1.ar1.dal2.gblx.net [64.213.176.150]
11 47 ms 47 ms 62 ms car2-4-v2.dllstx2.theplanet.com [12.96.160.52]
12 47 ms 47 ms 47 ms server.e3-plutos.com [69.41.234.242]
Trace complete.
If there is a routing problem on the Internet that is beyond the control
of you or us, you might see results like this:
traceroute to www.arrowwebsites.com [69.41.234.242]
1 <10 ms <10 ms <10 ms 20.17.1.254
2 <10 ms 16 ms <10 ms 20.6.29.9
3 <10 ms <10 ms 15 ms nwkrtr01-v305.de-sil.tst.com [20.6.29.5]
4 <10 ms 15 ms 16 ms ignenclwk3-v804.amer.tst.com [20.6.120.1]
5 hssi6-0.chi.sprintlink.net (209.8.159.25) 91 ms * 88 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * * (etc... repeated many times)
Results such as above could indicate excessive Internet traffic at an
exchange point, a routing problem, a fiber cut, or some other severed link
between you and us. You'll notice that the tracert stops before it reaches
Arrow's network. In this case, the connection failed just beyond Sprintlink (hssi6-0.chi.sprintlink.net).
If the problem appears to be somewhere between us and you,
unfortunately there's probably not much either of us can do about it other
than to wait for it to clear up.
If the problem appears to be with your ISP's network, you may want
to notify them of the condition so that they can take corrective measures.
