Andy Smith wrote:
> On Thu, Jan 25, 2007 at 11:54:08PM +0000, Chris Dennis wrote:
>> A client of mine is mysteriously unable to access a particular website,
>> viz www.newforestliving.co.uk. The browser hangs for quite a while and
>> then says it can't display the page.
>
> [...]
>
>> So where can the block be happening? What other tests can I do to find out?
>
> A tcptraceroute from knoppix cd might be interesting..
>
> $ tcptraceroute www.newforestliving.co.uk
> Selected device eth0, address 212.13.198.70, port 36374 for outgoing packets
> Tracing the path to www.newforestliving.co.uk (85.13.249.8) on TCP port 80 (www), 30 hops max
> 1 212.13.198.68 0.353 ms 0.289 ms 0.265 ms
> 2 kpn-peer.jump.net.uk (194.153.169.233) 0.770 ms 0.242 ms 0.260 ms
> 3 ldn-s2-rou-1001.UK.eurorings.net (134.222.231.61) 0.864 ms 1.063 ms 0.707 ms
> 4 134.222.230.121 0.586 ms 0.713 ms 0.591 ms
> 5 ldn-s2-rou-1003.UK.eurorings.net (134.222.231.226) 0.749 ms 0.601 ms 0.580 ms
> 6 ldn-s3-rou-1003.UK.eurorings.net (134.222.231.221) 0.971 ms 0.545 ms 0.576 ms
> 7 134.222.249.46 0.969 ms 0.647 ms 0.582 ms
> 8 so-0-1-0.lon11.ip.tiscali.net (213.200.80.29) 0.722 ms 0.982 ms 1.092 ms
> 9 ge-1-1-0-40.core2.sta.lon2.coreix.net (213.200.78.11) 0.957 ms 0.873 ms 1.058 ms
> 10 ge-0-2-60.dist1.sta.lon2.coreix.net (193.26.222.22) 1.344 ms 1.265 ms 1.705 ms
> 11 colo18.ukhost4u.com (85.13.249.8) [open] 1.096 ms 1.255 ms 1.183 ms
>
>
OK, thanks -- I'll try that next time I'm there.
What determines whether the results from tcptraceroute show up? All I
get from home is this:
tcptraceroute
www.newforestliving.co.uk
Selected device eth0, address 192.168.1.2, port 57053 for outgoing packets
Tracing the path to
www.newforestliving.co.uk (85.13.249.8) on TCP
port 80 (www) , 30 hops max
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 colo18.ukhost4u.com (85.13.249.8) [open] 58.226 ms 34.133 ms
37.242 ms
cheers
Chris
--
Chris Dennis cgdennis@???
Fordingbridge, Hampshire, UK
