UF-8300, UF-8200, UF-7300, UF-7200 (serv.man4) - Panasonic Fax Service Manual (repair manual). Page 126

126

UF-7300/7200

UF-8300/8200

If for some reason, the physical connection is missing, the echo reply will not be received from the 
destination and the following output is displayed:

If the physical destination is far and it's connected by WAN (Wide Area Network), the PING option 
command default value must be changed to compensate for the expected delayed response.

e.g. 
-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 not 

responding.

Another useful command-line utility is TRACERT, which is used to verify the route a packet takes to 
reach its destination. The result shows each router crossed and how long it took to get through each 
particular router to reach the specified destination.
The time it takes to get through a particular router is calculated three times and displayed for each 
router hop along with the IP Address of each router crossed. If a FQDN (Fully Qualified Domain Name) 
is available, it will be displayed as well.

a. To detect whether a particular router is malfunctioning along a known path. For example, if you 

know that packets on a network always go through London to get from New York to Berlin, but the 
communication is failing. A TRACERT to the Berlin address shows all the hops up to the point 
where the router in London should respond. If it does not respond, the time values are shown with 
an asterisk (*), indicating the packet timed out.

C:\WINDOWS>ping sv2.labo.pcc.com

Pinging sv2.labo.pcc.com [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time=5ms TTL=253
Reply from 192.168.1.2: bytes=32 time=5ms TTL=253
Reply from 192.168.1.2: bytes=32 time=5ms TTL=253
Reply from 192.168.1.2: bytes=32 time=5ms TTL=253

C:\WINDOWS>ping fmrt7.labo.pcc.com

Pinging fmrt7.labo.pcc.com [192.168.4.1] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.4.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum =  0ms, Average =  0ms 

C:\WINDOWS>ping js2.labo.pcc.com -n 10 -w 2000

Pinging js2.labo.pcc.com [210.232.71.18] with 32 bytes of data:

Reply from 210.232.71.18: bytes=32 time=633ms TTL=252
Reply from 210.232.71.18: bytes=32 time=645ms TTL=252
Reply from 210.232.71.18: bytes=32 time=810ms TTL=252
Reply from 210.232.71.18: bytes=32 time=455ms TTL=252
Reply from 210.232.71.18: bytes=32 time=645ms TTL=252
Reply from 210.232.71.18: bytes=32 time=633ms TTL=252
Reply from 210.232.71.18: bytes=32 time=677ms TTL=252
Reply from 210.232.71.18: bytes=32 time=703ms TTL=252
Reply from 210.232.71.18: bytes=32 time=633ms TTL=252
Reply from 210.232.71.18: bytes=32 time=633ms TTL=252