quote:
Originally posted by tracert
E:\Documents and Settings\Mike>tracert msghelp.net
Tracing route to msghelp.net [64.62.180.102]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 21 ms 21 ms 24 ms thes730a-l0.otenet.net [62.103.2.231]
3 20 ms 23 ms 21 ms thes734b-ge2.otenet.net [212.205.223.113]
4 26 ms 25 ms 25 ms athe-GSRb-thes-GSR.backbone.otenet.net [195.170.
3.237]
5 26 ms 26 ms 24 ms pos3-0-cr02.customers.ath.OTEglobe.net [62.75.3.
253]
6 73 ms 74 ms 71 ms Matm1-0-117-cr01.ama.oteglobe.net [62.75.4.78]
7 75 ms 74 ms 72 ms gsr12012.lon.he.net [195.66.224.21]
8 157 ms 157 ms 155 ms pos8-0.gsr12416.nyc.he.net [216.218.200.101]
9 223 ms 226 ms 221 ms pos7-0.gsr12012.sjc.he.net [216.218.254.153]
10 226 ms 225 ms 223 ms pos1-2.gsr12416.fmt.he.net [64.71.128.182]
11 226 ms 228 ms 226 ms 64.62.180.102
Trace complete.
quote:
Originally posted by ping
E:\Documents and Settings\Mike>ping msghelp.net
Pinging msghelp.net [64.62.180.102] with 32 bytes of data:
Reply from 64.62.180.102: bytes=32 time=223ms TTL=54
Reply from 64.62.180.102: bytes=32 time=222ms TTL=54
Reply from 64.62.180.102: bytes=32 time=222ms TTL=54
Reply from 64.62.180.102: bytes=32 time=223ms TTL=54
Ping statistics for 64.62.180.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 222ms, Maximum = 223ms, Average = 222ms
Anyway, the problem seems to be fixed now...
/ 
