Appendix Ii: Using Tracert - ESI E-Class Installation Manual

Esi remote ip feature phone
Hide thumbs Also See for E-Class:
Table of Contents

Advertisement

Remote IP Feature Phone Installation Manual
Appendix II:
Using TRACERT
The MS-DOS command TRACERT (short for trace route) can be used to determine the location of the
problem. At the DOS prompt type tracert followed by the IP PBX's remote-access IP address.
Here's an example of a trace route (host names simulated):
C:\WINDOWS\Desktop>tracert 63.211.73.226
Tracing route to 63.211.73.226 over a maximum of 30 hops
1
1 ms
2
3 ms
3
94 ms
4
75 ms
5
79 ms
6
80 ms
7
79 ms
8
165 ms
9
165 ms
10
*
11
*
12
*
13
*
14
*
15
*
16
*
17
*
18
*
19
*
This example shows that the PING request went through nine devices attempting to find a route to
63.211.73.226 before the PING timed out. The first device, at 10.0.2.1, is the local gateway. This shows
that the routing between the PC and local gateway is correct. If this first step times out, the problem is
between the PC and the gateway and may be a problem with the configuration of the gateway. Steps to
take in this case include:
• Verify that the PC is set to automatically obtain an IP address.
• Check the cabling connections.
• Use the applicable procedure in the next section to correct the gateway configuration.
The second step on the trace route is the ISP gateway. In the example, the ISP gateway address is
63.221.73.225. If this step times out, there is not a connection between the local gateway and the ISP
gateway. This again can be a problem with the configuration of the local gateway. Check the gateway
configuration and correct it if necessary. If this doesn't correct the problem, contact the service provider
for the remote site.
If TRACERT successfully reaches the ISP gateway but involves many hops, the problem could be at
the main office. Possible problems:
• Address used for PING and TRACERT is incorrect.
• Main office gateway is off-line.
• Service to the main office has been interrupted.
Call the network administrator at the main office to check these. If none of these is the source of the
problem contact the ISP.
1 ms
1 ms
10.0.2.1
2 ms
1 ms
63.221.73.225
74 ms
74 ms
172.20.0.1
75 ms
75 ms
fa7-2.core2.blink.net [63.216.17.33]
79 ms
80 ms
199.ATM-0.SAC1.BLINK.NET [204.255.174.13]
79 ms
80 ms
157.0.XR2.SAC1.BLINK.NET [152.63.51.70]
80 ms
80 ms
0.so.TR2.SAC1.BLINK.NET [152.63.3.197]
166 ms
164 ms
127.TR2.DCA8.BLINK.NET [146.188.141.117]
165 ms
166 ms
296.XR2.TCO1.BLINK.NET [152.63.32.217]
*
*
Request timed out.
*
*
Request timed out.
*
*
Request timed out.
*
*
Request timed out.
*
*
Request timed out.
*
*
Request timed out.
*
*
Request timed out.
*
*
Request timed out.
*
*
Request timed out.
*

Appendix II: Using TRACERT

I.1

Advertisement

Table of Contents
loading

Table of Contents