Quote:
|
Originally Posted by BBKing
er - ge-wan6x is the part of the dns name denoting the interface on that router - this will always be the one closest to you (where the icmp reply comes from). The important bit is the not-t2core-a or not-t2core-b bit, those are two separate machines.
No, I don't know what the problem is, before anyone asks, it's too far up the network for me, have to ask a big boss network guy. People on the nthellworld irc channel are complaining too though.
|
it's 'deeper' than that for me too - & wan61 looked ok.
TraceRoute Report
on 06/01/04 at 22:28:52
Tracing route to forums.digiguide.com over a maximum of 25 hops:
#1 ***.**.***.*** [Unavailable]: TTL expired in transit, 17 ms
#2 80.4.47.225 [nott-t2cam1-b-ge-wan51-128.inet.ntl.com]: TTL expired in transit, 12 ms
#3 80.1.79.185 [not-t2core-b-ge-wan61.inet.ntl.com]: TTL expired in transit, 18 ms
#4 62.253.185.37 [nth-bb-b-so-200-0.inet.ntl.com]: TTL expired in transit, 34 ms
#5 62.253.185.117 [nth-bb-a-ae0-0.inet.ntl.com]: TTL expired in transit, 25 ms
#6 62.253.185.98 [gfd-bb-b-so-400-0.inet.ntl.com]: TTL expired in transit, 20 ms
#7 62.253.185.74 [tele-ic-2-so-100-0.inet.ntl.com]: TTL expired in transit, 24 ms
#8 195.66.224.126 [linx1.lon1.as8553.net]: TTL expired in transit, 24 ms
#9 195.10.255.194 [fa1-0.lon6.as8553.net]: TTL expired in transit, 24 ms
#10 195.10.255.134 [s6-1.bris1.as8553.net]: TTL expired in transit, 67 ms
#11 195.10.254.82 [fa0-0-2.bris2.as8553.net]: TTL expired in transit, 25 ms
#12 195.10.255.14 [s6-0.man1.as8553.net]: TTL expired in transit, 68 ms
#13 [Unavailable]: Request timed out
etc
#25 [Unavailable]: Request timed out
Statistics: Out: 25; In: 12; Loss: 52%; Times(min/avg/max): 12/29/68