Shoutbox

quote:

---

Originally posted by CookieRevised

quote:

---

Originally posted by theguy
well i tried tracert to msgplus.net and the request timed out from hop 2 to hop 30. the request also timed out on ping with 4 lost packets. is msgplus.net down?
the exact same thing happened with msghelp.net.

---

Wj requested to list it, not to tell him about it. The list is important as it gives the clue to where it goes wrong (the line before the timeouts).

PS: if the tracert check times out, the ping will always time out too.

---

Well, it would get to my router, then it would time out. <--that's for both sites.

hmm, I can't seem to connect to www.msgplus.net right now, here's the traceroute and ping below...

code:

---

tracert msgplus.net

Tracing route to msgplus.net [64.62.180.100]
over a maximum of 30 hops:

  1    27 ms    30 ms    30 ms  loopback1.ar2.gs1.systems.pipex.net [62.241.161.
244]
  2    31 ms    30 ms    30 ms  ge-2-0-0.cr1.gs1.systems.pipex.net [62.241.161.1
02]
  3    30 ms    30 ms    30 ms  xp-ix.lon.he.net [217.79.160.99]
  4   109 ms   108 ms   108 ms  pos8-0.gsr12416.nyc.he.net [216.218.200.101]
  5   171 ms   171 ms   171 ms  pos7-0.gsr12012.sjc.he.net [216.218.254.153]
  6   171 ms   186 ms   171 ms  pos1-2.gsr12416.fmt.he.net [64.71.128.182]
  7   187 ms   187 ms   186 ms  64.62.180.100

Trace complete.

---

code:

---

ping msgplus.net

Pinging msgplus.net [64.62.180.100] with 32 bytes of data:

Reply from 64.62.180.100: bytes=32 time=174ms TTL=58
Reply from 64.62.180.100: bytes=32 time=171ms TTL=58
Reply from 64.62.180.100: bytes=32 time=171ms TTL=58
Reply from 64.62.180.100: bytes=32 time=171ms TTL=58

Ping statistics for 64.62.180.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 171ms, Maximum = 174ms, Average = 171ms

---

Happened again...

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    19 ms    21 ms    18 ms  thes730a-l0.otenet.net [62.103.2.231]
  3    19 ms    20 ms    21 ms  thes734b-ge2.otenet.net [212.205.223.113]
  4    27 ms    24 ms    29 ms  athe-GSRb-thes-GSR.backbone.otenet.net [195.17
3.237]
  5    38 ms    27 ms    28 ms  pos3-0-cr02.customers.ath.oteglobe.net [62.75.
253]
  6    73 ms    74 ms    79 ms  Matm1-0-117-cr01.ama.OTEglobe.net [62.75.4.78]
  7    75 ms    78 ms    76 ms  gsr12012.lon.he.net [195.66.224.21]
  8   221 ms   216 ms   220 ms  pos8-0.gsr12416.nyc.he.net [216.218.200.101]
  9   285 ms   282 ms   287 ms  pos7-0.gsr12012.sjc.he.net [216.218.254.153]
10   285 ms   286 ms   282 ms  pos1-2.gsr12416.fmt.he.net [64.71.128.182]
11   286 ms   288 ms   287 ms  64.62.180.102

Trace complete.



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=287ms TTL=54
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 64.62.180.102:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
    Minimum = 287ms, Maximum = 287ms, Average = 287ms

Yep, well and truly gone crazy. I did another traceroute and ping which will be of more use.

code:

---

20:06PM | 29 May 2005

ping msghelp.net

Pinging msghelp.net [64.62.180.102] with 32 bytes of data:

Reply from 64.62.180.102: bytes=32 time=231ms TTL=58
Request timed out.
Reply from 64.62.180.102: bytes=32 time=230ms TTL=58
Request timed out.

Ping statistics for 64.62.180.102:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 230ms, Maximum = 231ms, Average = 230ms

tracert msghelp.net

Tracing route to msghelp.net [64.62.180.102]
over a maximum of 30 hops:

  1    22 ms    21 ms    23 ms  loopback1.ar2.gs1.systems.pipex.net [62.241.161.
244]
  2    22 ms    21 ms    21 ms  ge-2-0-0.cr1.gs1.systems.pipex.net [62.241.161.1
02]
  3    21 ms    21 ms    21 ms  xp-ix.lon.he.net [217.79.160.99]
  4   164 ms   161 ms   163 ms  pos8-0.gsr12416.nyc.he.net [216.218.200.101]
  5   231 ms   230 ms   230 ms  pos7-0.gsr12012.sjc.he.net [216.218.254.153]
  6   230 ms   230 ms   230 ms  pos1-2.gsr12416.fmt.he.net [64.71.128.182]
  7   234 ms   234 ms   232 ms  64.62.180.102

Trace complete.

---