Tracert Problems

W

W Dean

Hi,

I am having problems doing a tracert to m19.co.uk, it keeps reporting
timeouts. However, I can do pings to the same address and they seem to work.
browsing to the url and other functions also are working.


Ping
----
Pinging m19.co.uk [66.234.10.148] with 32 bytes of data:
Reply from 66.234.10.148: bytes=32 time=130ms TTL=108
Reply from 66.234.10.148: bytes=32 time=131ms TTL=108
Reply from 66.234.10.148: bytes=32 time=150ms TTL=108
Reply from 66.234.10.148: bytes=32 time=161ms TTL=108
Ping statistics for 66.234.10.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 130ms, Maximum = 161ms, Average = 143ms

Tracert
-------

Tracing route to m19.co.uk [66.234.10.148]
over a maximum of 30 hops:
1 10 ms 10 ms 10 ms 10.11.0.1
2 30 ms 10 ms 10 ms oldh-t2cam1-b-ge-wan51-120.inet.ntl.com
[80.5.164.209]
3 10 ms 20 ms 20 ms man-t2core-b-ge-wan62.inet.ntl.com
[213.104.242.169]
4 10 ms <10 ms 20 ms man-bb-b-so-210-0.inet.ntl.com
[62.253.184.61]
5 20 ms 10 ms 20 ms man-bb-a-ae0-0.inet.ntl.com [62.253.187.177]
6 10 ms 10 ms 10 ms ycr2-so-3-0-0.Manchester.cw.net
[208.175.252.89]
7 20 ms 20 ms 20 ms bcr2-so-3-0-0.Thamesside.cw.net
[166.63.209.201]
8 110 ms 221 ms 150 ms dcr1-loopback.Chicago.cw.net [208.172.2.99]
9 110 ms 181 ms 160 ms bpr2-so-0-0-0.ChicagoEquinix.cw.net
[208.175.10.98]
10 110 ms 120 ms 151 ms 208.174.224.26
11 130 ms 161 ms 130 ms chcgil1wcx2-oc48.wcg.net [64.200.103.117]
12 160 ms 191 ms 140 ms brvwil1wcx3-pos9-0-1-a0.wcg.net
[64.200.103.194]
13 150 ms 131 ms 180 ms drvlga1wcx2-pos6-0.wcg.net [64.200.210.106]
14 130 ms 140 ms 141 ms drvlga1wcx1-oc48.wcg.net [64.200.127.29]
15 120 ms 130 ms 150 ms miamfl2wcx3-oc48.wcg.net [64.200.240.17]
16 120 ms 130 ms 130 ms miamfl6lce1-pos5-0.wcg.net [64.200.119.90]
17 191 ms 130 ms 130 ms Miami-NOTA-TWC1114543-GE.wcg.net
[64.200.118.242]
18 151 ms 160 ms 140 ms 66.234.14.57
19 140 ms 200 ms 180 ms 216.87.0.37
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 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.


wodge
 
J

J N Katzman-TCM

W,

There might be hosts/routers/firewalls in between that are configured not to
respond to the trace route. Ping and Traceroute are implemented using different
ICMP techniques/functions.

It does not necesarilly indicate a problem.

HTH,

Joel Katzman
TCM Integrated Systems, Inc
Freeport NY.

W said:
Hi,

I am having problems doing a tracert to m19.co.uk, it keeps reporting
timeouts. However, I can do pings to the same address and they seem to work.
browsing to the url and other functions also are working.

Ping
----
Pinging m19.co.uk [66.234.10.148] with 32 bytes of data:
Reply from 66.234.10.148: bytes=32 time=130ms TTL=108
Reply from 66.234.10.148: bytes=32 time=131ms TTL=108
Reply from 66.234.10.148: bytes=32 time=150ms TTL=108
Reply from 66.234.10.148: bytes=32 time=161ms TTL=108
Ping statistics for 66.234.10.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 130ms, Maximum = 161ms, Average = 143ms

Tracert
-------

Tracing route to m19.co.uk [66.234.10.148]
over a maximum of 30 hops:
1 10 ms 10 ms 10 ms 10.11.0.1
2 30 ms 10 ms 10 ms oldh-t2cam1-b-ge-wan51-120.inet.ntl.com
[80.5.164.209]
3 10 ms 20 ms 20 ms man-t2core-b-ge-wan62.inet.ntl.com
[213.104.242.169]
4 10 ms <10 ms 20 ms man-bb-b-so-210-0.inet.ntl.com
[62.253.184.61]
5 20 ms 10 ms 20 ms man-bb-a-ae0-0.inet.ntl.com [62.253.187.177]
6 10 ms 10 ms 10 ms ycr2-so-3-0-0.Manchester.cw.net
[208.175.252.89]
7 20 ms 20 ms 20 ms bcr2-so-3-0-0.Thamesside.cw.net
[166.63.209.201]
8 110 ms 221 ms 150 ms dcr1-loopback.Chicago.cw.net [208.172.2.99]
9 110 ms 181 ms 160 ms bpr2-so-0-0-0.ChicagoEquinix.cw.net
[208.175.10.98]
10 110 ms 120 ms 151 ms 208.174.224.26
11 130 ms 161 ms 130 ms chcgil1wcx2-oc48.wcg.net [64.200.103.117]
12 160 ms 191 ms 140 ms brvwil1wcx3-pos9-0-1-a0.wcg.net
[64.200.103.194]
13 150 ms 131 ms 180 ms drvlga1wcx2-pos6-0.wcg.net [64.200.210.106]
14 130 ms 140 ms 141 ms drvlga1wcx1-oc48.wcg.net [64.200.127.29]
15 120 ms 130 ms 150 ms miamfl2wcx3-oc48.wcg.net [64.200.240.17]
16 120 ms 130 ms 130 ms miamfl6lce1-pos5-0.wcg.net [64.200.119.90]
17 191 ms 130 ms 130 ms Miami-NOTA-TWC1114543-GE.wcg.net
[64.200.118.242]
18 151 ms 160 ms 140 ms 66.234.14.57
19 140 ms 200 ms 180 ms 216.87.0.37
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 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.

wodge
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

I've used tracert. Now what do I do ?? 3
PROBLEM IN MY LAN 3
ICS / (DNS?) Problem with Sharing Client 1
Mysterious network problem. 7
WCG on O2/Be Broadband 14
Problem with tracert command 1
HELP! Can anyone give me a clue here? 2
Bizarre ping times 3

Top