On 01-Sep-07 21:28:22, Chris G wrote:
On Sat, Sep 01, 2007 at 09:43:04PM +0100, Ted Harding wrote:
On 01-Sep-07 20:34:07, Chris G wrote:
The WDG site at htmlhelp.com appears to be down at the moment, can anyone recommend any similar sites which document the basics of HTML, CSS etc. on line?
Or are the htmlhelp.com pages available from anywhere else?
-- Chris Green
Hi Chris, I just got, without any apparent problems, what looks like a WDG site at
http://htmlhelp.com/ [...]
Yes, that's right, but I still can't see it! Just about everything else seems to be OK so it must be some wierd DNS type problem I guess with my ISP. .... no, not a DNS problem, I can't get to 207.36.201.119 either.
However if I ssh to somewhere else and then use Lynx to access http://htmlhelp.com/ it works fine. So it would seem to be some sort of routing issue. Running traceroute to htmlhelp.com grinds to a halt after 17 hops.
It's rather odd actually, from the other site (that I ssh'ed to) I get:-
... ... ... 11 66.113.197.54 (66.113.197.54) 101.976 ms 102.833 ms 102.855
ms 12 e1-3.co2.as30217.net (84.40.24.101) 103.306 ms 103.715 ms 105.891 ms 13 e49te.dr5.as30217.net (84.40.24.82) 107.886 ms * * 14 66.230.227.170 (66.230.227.170) 106.569 ms 123.725 ms 103.507 ms 15 zaphod.htmlhelp.com (207.36.201.119) 105.921 ms 102.421 ms 103.245 ms
Whereas from home I get:-
... ... ... 14 66.113.197.54 (66.113.197.54) 136.029 ms 136.216 ms 137.974
ms 15 * * * 16 e49te.dr5.as30217.net (84.40.24.82) 137.665 ms * * 17 66.230.227.170 (66.230.227.170) 138.291 ms 137.107 ms 135.996 ms 18 * * * 19 * * * 20 * * *
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!
Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) ted.harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 02-Sep-07 Time: 13:02:19 ------------------------------ XFMail ------------------------------