Quote:
|
Originally Posted by pem
Actually both those traces are looking fine - the first one is missing the final step of the server itself - which is expected as ICMP is blocked by the servers firewall (I know, I configured it).
The second one is fine and identical to mine, the 207.46.x.x hops are all inside the Microsoft Network so I would guess they are blocking ICMP at the servers as well (hence you can't ping them either).
|
yes this would confirm?
TraceRoute Report on 07/01/04 at 01:39:47
Tracing route to 207.46.244.188 over a maximum of 25 hops:
#1 ***.**.***.***[Unavailable]: TTL expired in transit, 42 ms
#2 80.4.47.225 [nott-t2cam1-b-ge-wan51-128.inet.ntl.com]: TTL expired in transit, 26 ms
#3 80.1.79.201 [not-t2core-b-ge-wan74.inet.ntl.com]: TTL expired in transit, 15 ms
#4 62.253.188.37 [nth-bb-b-so-300-0.inet.ntl.com]: TTL expired in transit, 13 ms
#5 62.253.185.117 [nth-bb-a-ae0-0.inet.ntl.com]: TTL expired in transit, 17 ms
#6 193.251.254.141 [So5-0-0.LONCR2.London.opentransit.net]: TTL expired in transit, 18 ms
#7 193.251.128.205 [So3-0-0.LONCR1.London.opentransit.net]: TTL expired in transit, 50 ms
#8 193.251.242.254 [P12-0.OAKCR1.Oakhill.opentransit.net]: TTL expired in transit, 211 ms
#9 193.251.248.109 [So4-0-0.ASHBB1.Ashburn.opentransit.net]: TTL expired in transit, 91 ms
#10 193.251.248.109 [So4-0-0.ASHBB1.Ashburn.opentransit.net]: TTL expired in transit, 97 ms
#11 207.46.34.113 [Unavailable]: TTL expired in transit, 93 ms
#12 207.46.34.113 [Unavailable]: TTL expired in transit, 98 ms
#13 207.46.33.61 [Unavailable]: TTL expired in transit, 186 ms
#14 207.46.155.13 [Unavailable]: TTL expired in transit, 190 ms
#15 207.46.155.13 [Unavailable]: TTL expired in transit, 184 ms
#16 [Unavailable]: Request timed out
#17 [Unavailable]: Request timed out
etc
#25 [Unavailable]: Request timed out
Statistics: Out: 25; In: 15; Loss: 40%; Times(min/avg/max): 13/88/211