On Sun, Sep 02, 2007 at 01:02:28PM +0100, Ted Harding wrote:
The route up to 66.113.197.54 is basically the same for both.
Any ideas what's going on anyone?
Something really weird is going on!
I just repeated the experiment I made last night:
[A] traceroute to htmlhelp.com [from same machine as last time] 1st time: OK but a hesitation near the end of the line 2nd time: Similar, but longer hesitation 3rd time: Gets near the end, then hangs forever. So kill with ^C.
BUT: From that machine I can no longer ping a remote host (that does respond to pings, and my other machines can ping it successfully). So:
[B] Log in to another of my machines, and repeat as for [A]. Same results as for 1st time, 2nd time, 3rd time. AND: Can no longer ping from this machine either! So:
[C] Log in to a third machine, and repeat same. Result: Exactly as for [A] and [B], including "lockout" of ping.
However, on all three cases, ability to ping is resumed after a few minutes.
Anyone met this before? I never did!
It is/was apparently some sort of starnge routing issue in the USA somewhere. It seems to have been sorted out now as I can get to htmlhelp.com OK again.