Ross Smith wrote:
> They're both the same machine. Here's what I get from a traceroute:
>
> >Tracing route to twysted.net [206.54.177.99]
> >over a maximum of 30 hops:
> > 1 117 ms 104 ms 113 ms max52.akl.ihug.co.nz [203.29.165.52]
> > 2 126 ms 118 ms 113 ms feth-0-1-tig-nz-akl-1.ihug.net [203.29.165.254]
> > 3 489 ms 477 ms 479 ms 202.49.88.42
> > 4 444 ms 447 ms 446 ms gip-stock-5-serial1-1-0.gip.net [204.59.165.33]
> > 5 458 ms 449 ms 444 ms sl-bb23-stk-1-1.sprintlink.net [144.232.4.133]
> > 6 444 ms 447 ms 467 ms sl-pr1-stk-4-0-0.sprintlink.net [144.232.4.102]
> > 7 * * * Request timed out.
> > 8 * * * Request timed out.
>
> It looks as though Sprintlink might have got one of their routers in a
> twist. If it's still not working when I get back from my holiday I'll
> get one of our networking people to have a word with them.
My apologies.....
It was initially the case that www.twysted and twysted were identical.
Then the www option was removed. Twyst must have reinstalled the
www option -- I should have checked before posting my advice.
I also have had spotty luck reaching the server. But I am able
to do so a majority of the time.
Dan
Post a reply to this message
|