Happened here too...
Here's my ping & tracert results while I couldnt connect... :
quote:
Originally posted by ping.exe
C:\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=331ms TTL=51
Reply from 64.62.180.102: bytes=32 time=318ms TTL=51
Reply from 64.62.180.102: bytes=32 time=321ms TTL=51
Reply from 64.62.180.102: bytes=32 time=330ms TTL=51
Ping statistics for 64.62.180.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 318ms, Maximum = 331ms, Average = 325ms
quote:
Originally posted by tracert.exe
C:\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 42 ms 39 ms 38 ms 62.103.1.80
3 31 ms 45 ms 33 ms vlan55-k2.otenet.net [62.103.14.193]
4 32 ms 28 ms 35 ms 62.103.6.145
5 30 ms 31 ms 34 ms athe-GSRb-po1.otenet.net [62.103.6.4]
6 117 ms 117 ms 112 ms 62.75.3.245
7 185 ms 195 ms 195 ms pos2-0-cr02.lon.oteglobe.net [62.75.4.78]
8 103 ms 98 ms 108 ms lon.he.net [195.66.226.21]
9 248 ms 267 ms 268 ms pos4-1.gsr12416.nyc.he.net [216.218.200.101]
10 322 ms 331 ms 322 ms pos0-1.gsr12416.sjc2.he.net [216.218.223.133]
11 249 ms 246 ms 249 ms pos10-0.gsr12416.fmt.he.net [216.218.229.38]
12 341 ms 345 ms 346 ms 64.62.180.102
Trace complete.
/ 
