TRACERT




Tracert is another command line utility built into Windows and most other computer systems. The basic tracert command syntax is:

tracert hostname
-or-
tracert nn.nn.nn.nn

First, tracert sends out an ICMP echo packet to the named host with a TTL of 1, second – with a TTL of 2, etc. Tracert eventually gets TTL expired in transit message back from the routers until the desination host computer finally is reached.

When the host computer is reached, it responds with the standard ICMP echo reply packet. The tracert then prints Trace complete and stops.

Tracing route to google.com [74.125.229.211]
over a maximum of 30 hops:

1     1 ms     1 ms     1 ms  linksys.linksys [10.0.0.1]
2     6 ms     7 ms     5 ms  adsl-72-145-34-1.mia.bellsouth.net [72.145.34.1

3     6 ms     7 ms     7 ms  205.152.108.1
4    10 ms     9 ms     9 ms  ixc00mia-ge-0-2-2.bellsouth.net [205.152.145.25

5   181 ms    13 ms    61 ms  12.81.8.94
6    10 ms    10 ms     6 ms  12.81.8.73
7    13 ms    14 ms    11 ms  74.175.192.222
8    15 ms    17 ms    17 ms  cr81.fldfl.ip.att.net [12.122.106.94]
9    20 ms    13 ms    13 ms  12.123.153.137
10    17 ms    17 ms     *     12.249.135.14
11    13 ms    16 ms    17 ms  209.85.253.120
12    15 ms    15 ms    15 ms  216.239.46.94
13    18 ms    15 ms    14 ms  mia04s05-in-f19.1e100.net [74.125.229.211]

Trace complete.

tracert condition 1

If your trace ends in all timeouts
This is possibly due to some kind of problem, but it may also be an intentional block due to a firewall or other security measures, and the block may affect traceroute but not actual server connections.
or
If your traceroute ends in timeouts at a certain system, it’s likely that either the connection between that system and the next system on the route, or the next system itself, is the source of the problem. The system may be down, or the network connecting them may be down. You may just have to wait for the problem to be fixed, especially if the problem system is not at your ISP and thus you aren’t a paying customer of that network.

tracert condition 2

error messages

error message sample
google.com (208.225.64.50)  35.931 ms !H *  39.970 ms !H

error message codes

!H
Host unreachable. The router has no route to the target system.
!N
Network unreachable.
!P
Protocol unreachable.
!S
Source route failed. You tried to use source routing, but the router is configured to block source-routed packets.
!F
Fragmentation needed. This indicates that the router is misconfigured.
!X
Communication administratively prohibited. The network administrator has blocked traceroute at this router.

tracert condition 3
high latency
Typically, a modem connection’s inherent latency will be around 120-130ms. The latency on an ISDN line is usually around 40-45ms. If you use a connection of this type, you won’t see any better than these numbers.

If you see, in a trace output, a large “jump” in latency from one hop to the next, that could indicate a problem. It could be a saturated (overused) network link; a slow network link; an overloaded router; or some other problem at that hop. Of course, it could also be a problem anywhere on the return route from the high-latency hop as well.

This entry was posted in Network and tagged , , , , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>