Bad Tracert?

Wicked_and_Crazy · 15-12-2006, 22:55

Can someone trace this for me and post the results

Tracing route to www.meshcomputers.com [217.33.108.40]
over a maximum of 30 hops:

1 7 ms 1 ms 1 ms ******** [192.168.1.1]
2 7 ms 9 ms 8 ms ***.***.***.***
3 8 ms 7 ms 8 ms pete-t2cam1-b-ge95.inet.ntl.com [80.3.130.145]
4 10 ms 7 ms 8 ms pete-t2core-b-ge-wan61.inet.ntl.com [195.182.176.213]
5 14 ms 13 ms 13 ms pop-bb-b-so-630-0.inet.ntl.com [62.253.188.229]
6 14 ms 14 ms 15 ms gfd-bb-a-so-010-0.inet.ntl.com [213.105.172.137]
7 14 ms 14 ms 13 ms gfd-bb-b-ge-000-0.inet.ntl.com [213.105.172.6]
8 14 ms 15 ms 16 ms tele-ic-1-so-110-0.inet.ntl.com [62.253.185.78]
9 16 ms 14 ms 14 ms 194.74.65.21
10 15 ms 14 ms 13 ms core1-pos14-1.ealing.ukcore.bt.net [194.74.65.253]
11 14 ms 13 ms 14 ms core1-pos13-3.kingston.ukcore.bt.net [62.6.201.74]
12 15 ms 15 ms 15 ms vhsaccess1-pos7-0.kingston.fixed.bt.net [194.72.3.234]
13 20 ms 15 ms 15 ms ftip002831732.vhsaccess1.kingston.fixed-nte.bt.net [195.99.117.22]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19

Druchii · 15-12-2006, 22:57

Code:

C:\Documents and Settings\X>tracert meshcomputers.com
Unable to resolve target system name meshcomputers.com.

C:\Documents and Settings\X>tracert www.meshcomputers.com

Tracing route to www.meshcomputers.com [217.33.108.40]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  WRT54G [192.168.1.1]
  2    10 ms     9 ms     8 ms  10.156.64.1
  3    26 ms    11 ms    11 ms  gsr01-do.blueyonder.co.uk [62.30.241.129]
  4     *      144 ms   199 ms  62.30.252.81
  5    18 ms    15 ms    15 ms  62.30.252.53
  6    53 ms    61 ms    82 ms  e123-van1-kno.cableinet.net [194.117.138.2]
  7    18 ms    20 ms    16 ms  194.117.136.166
  8    27 ms    26 ms    31 ms  tele2-gw4.telewest.net [194.117.136.197]
  9    32 ms    49 ms    46 ms  bt-telewest-privatepeer.blueyonder.co.uk [194.11
7.147.18]
 10    33 ms    38 ms    30 ms  core1-pos14-0.ealing.ukcore.bt.net [62.6.201.81]

 11    52 ms    70 ms   100 ms  core1-pos5-3.kingston.ukcore.bt.net [62.6.201.70
]
 12   138 ms   104 ms   117 ms  vhsaccess1-pos7-0.kingston.fixed.bt.net [194.72.
3.234]
 13   160 ms   175 ms   133 ms  ftip002831732.vhsaccess1.kingston.fixed-nte.bt.n
et [195.99.117.22]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17  ^C

There you go

Wicked_and_Crazy · 15-12-2006, 22:58

thanks for that

might want to get rid of you IP address

and maybe rename your router

Druchii · 15-12-2006, 23:23

That's not my WAN side IP address, and the router is fine

Richy99 · 18-12-2006, 13:24

all it means is that the routers are set not to respond to icmp ping packets