Like...
tracert
www.yahoo.com
Tracing route to
www.yahoo.akadns.net [68.142.226.47]
over a maximum of 30 hops:
1 10 ms 20 ms 11 ms 10.5.63.1
2 10 ms 10 ms 10 ms at-3-3-0-1715.CORE-RTR2.NWRK.verizon-gni.net [13
0.81.7.53]
3 10 ms 10 ms 20 ms so-2-0-0-0.BB-RTR2.NWRK.verizon-gni.net [130.81.
7.161]
4 10 ms 20 ms 10 ms so-6-0-0-0.BB-RTR2.PHIL.verizon-gni.net [130.81.
7.185]
5 20 ms 20 ms 20 ms so-5-0-0-0.BB-RTR2.RES.verizon-gni.net [130.81.7
..245]
6 20 ms 21 ms 10 ms so-7-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81
..10.94]
7 10 ms 20 ms 10 ms 130.81.15.50
8 10 ms 20 ms 20 ms vlan260-msr2.re1.yahoo.com [216.115.96.173]
9 20 ms 20 ms 20 ms v3.bas1.re2.yahoo.com [206.190.33.6]
10 20 ms 10 ms 20 ms p16.
www.re2.yahoo.com [68.142.226.47]
Trace complete.
and...
tracert 202.54.6.35
Tracing route to md3.vsnl.net.in [202.54.6.35]
over a maximum of 30 hops:
1 10 ms 10 ms 10 ms 10.5.63.1
2 10 ms 10 ms 11 ms at-3-3-0-1715.CORE-RTR2.NWRK.verizon-gni.net [13
0.81.7.53]
3 10 ms 10 ms 20 ms so-2-0-0-0.BB-RTR2.NWRK.verizon-gni.net [130.81.
7.161]
4 10 ms 10 ms 20 ms so-5-0-0-0.BB-RTR1.NY5030.verizon-gni.net [130.8
1.7.189]
5 10 ms 10 ms 20 ms so-7-0-0-0.BB-RTR2.NY5030.verizon-gni.net [130.8
1.8.74]
6 10 ms 20 ms 10 ms so-6-0-0-0.BB-RTR1.NY60.verizon-gni.net [130.81.
8.250]
7 10 ms 10 ms 20 ms so-1-0-0-0.PEER-RTR1.NY60.verizon-gni.net [130.8
1.4.210]
8 10 ms 10 ms 10 ms jfk-edge-20.inet.qwest.net [65.116.172.85]
9 10 ms 10 ms 10 ms jfk-core-03.inet.qwest.net [205.171.230.18]
10 10 ms 10 ms 20 ms jfk-brdr-02.inet.qwest.net [205.171.230.25]
11 10 ms 10 ms 20 ms qwest-gw.n54ny.ip.att.net [192.205.32.169]
12 10 ms 20 ms 10 ms 12.123.3.110
13 20 ms 20 ms 20 ms tbr2-cl1.wswdc.ip.att.net [12.122.10.54]
14 30 ms 40 ms 30 ms tbr1-cl1.attga.ip.att.net [12.122.10.70]
15 30 ms 30 ms 40 ms gbr5-p20.attga.ip.att.net [12.122.12.22]
16 30 ms 30 ms 40 ms gar2-p360.attga.ip.att.net [12.123.21.73]
17 351 ms 350 ms 351 ms 12.124.58.134
18 371 ms 370 ms 371 ms chn-ekm-atm-pvc1.Bbone.vsnl.net.in [202.54.2.150
]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27
~~~
Dave
| i have tried to trace the route to
www.yahoo.com and to
| md3.vsnl.net.in(202.54.6.35). i had traced routes to both of them earlier
| when i was running windows 98.
| S.L.Narasimham.
| | > So, the end-node isn't a traceable node with the routers not being
| resolvable. That does
| > NOT mean TRACERT.EXE is not working. It means you don't understand how
| TRACERT.EXE works
| > and the possible output displays you may see.
| >
| > Dave
| >
| >
| >
| >
| > | > | when i try to run the tracert to a particular host(any host) the command
| > | window opens --says trying to trace route to ------ over 30 hops then in
| the
| > | next line it says 1 and puts out 3 asterisks and says request timed out.
| 2.
| > | 3 asterisks and request timed out.
| > | same with gimme ip also.
| > | i am not able to run a trace.
| > | same with the ping command also.
| > | i run windows xp with all the patches regularly downloaded and
| installed.
| > | i have zone alarm installed but both tcp/ip ping command and tcp/ip
| > | traceroute command are permitted in the trusted as well as internet
| zones
| > | under both access and server categories.
| > | where is the problem? with my local isp? in my system? have i tweaked
| > | something unknowingly?
| > | thanking you in advance,
| > | S.L.Narasimham
| > |
| > |
| >
| >
|
|
