Server reboot.

[Anonymous]

Small but important typo ... "cmd" is what you should type - no quotes.

Good point well presented :blush2:

[TeaLeaf]

...and there was I thinking "oh, I've been using 'cmd' and doing it wrong all these years" and was off to try 'cms' :norty:

TL.

[Anonymous]

...and there was I thinking "oh, I've been using 'cmd' and doing it wrong all these years" and was off to try 'cms' :norty:
 
TL.

Let me know how you get on :unsure:

[MAD_ness]

How do ya stop it from doing 5 jumps then closing the window ?

[Hippy]

C:\>tracert -d 87.240.138.21

Tracing route to 87.240.138.21 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    19 ms    20 ms    20 ms  195.93.23.169
  3    20 ms     *        *     195.93.17.190
  4    21 ms    19 ms    19 ms  172.17.169.92
  5    20 ms    20 ms    50 ms  195.93.31.30
  6    21 ms    20 ms    19 ms  66.185.143.197
  7    21 ms    20 ms    20 ms  213.206.157.153
  8    49 ms    49 ms    50 ms  82.195.191.26
  9    50 ms    51 ms    50 ms  217.118.119.57
 10    50 ms    50 ms    50 ms  84.233.152.162
 11    50 ms    49 ms    49 ms  217.118.119.34
 12    50 ms    50 ms    49 ms  84.233.186.90
 13    55 ms    56 ms    56 ms  87.240.128.50
 14    54 ms    53 ms    54 ms  87.240.138.21

Trace complete.

[Anonymous]

Your problem seems to relate to the jump from node 7 to node 8. The IP Addresses resolve as:

sl-gw23-lon-12-0.sprintlink.net [213.206.157.153] <- Node 7
sle-intercom-3-0.sprintlink.net [82.195.191.26] <- Node 8

which suggests to me that the problem lies within Sprintlink

Interestingly, I cannot tracert to either of the above IP addresses as it keeps timing out!