150SEP 2004Ver. 1.2DP-1520P/1820P/1820EIf the physical destination is far and it's connected by WAN (Wide Area Network), the PING optioncommand default value must be changed to compensate for the expected delayed response.e.g.4. Tracing a Packet RouteAnother useful command-line utility is TRACERT, which is used to verify the route a packet takes toreach its destination. The result shows each router crossed and how long it took to get through eachparticular router to reach the specified destination.The time it takes to get through a particular router is calculated three times and displayed for eachrouter hop along with the IP Address of each router crossed. If a FQDN (Fully Qualified DomainName) is available, it will be displayed as well.This utility is useful for two diagnostic purposes:a. To detect whether a particular router is malfunctioning along a known path. For example, if youknow that packets on a network always go through London to get from New York to Berlin, but thecommunication is failing. A TRACERT to the Berlin address shows all the hops up to the pointwhere the router in London should respond. If it does not respond, the time values are shown withan asterisk (*), indicating the packet timed out.b. To determine whether a router is slow and needs to be upgraded or additional routers should beinstalled on the network. You can determine this by simply comparing the time it takes for a packetto get through a particular router. If its return time is significantly higher than the other routers, itshould be upgraded.To use this utility, from the DOS command-line, type: tracert Tracing the Route to SMTP/POP Server-n 10 : The number of echo requests that the command should send.-w 2000 : Specifies the period PING will wait for the reply before deciding that the host is notresponding.C:\WINDOWS>ping js2.labo.pcc.com -n 10 -w 2000Pinging js2.labo.pcc.com [210.232.71.18] with 32 bytes of data:Reply from 210.232.71.18: bytes=32 time=633ms TTL=252Reply from 210.232.71.18: bytes=32 time=645ms TTL=252Reply from 210.232.71.18: bytes=32 time=810ms TTL=252Reply from 210.232.71.18: bytes=32 time=455ms TTL=252Reply from 210.232.71.18: bytes=32 time=645ms TTL=252Reply from 210.232.71.18: bytes=32 time=633ms TTL=252Reply from 210.232.71.18: bytes=32 time=677ms TTL=252Reply from 210.232.71.18: bytes=32 time=703ms TTL=252Reply from 210.232.71.18: bytes=32 time=633ms TTL=252Reply from 210.232.71.18: bytes=32 time=633ms TTL=252C:\WINDOWS>tracert sv2.labo.pcc.comTracing route to sv2.labo.pcc.com [192.168.1.2]over a maximum of 30 hops:1 4 ms 2 ms 2 ms 192.168.3.2542 4 ms 5 ms 5 ms sv2.labo.pcc.com [192.168.1.2]Trace complete.