Quote:
|
Originally Posted by jonbr
|
I fear it may have been a fluke or some network condition thing. I'm suffering badly again today. Nowt's resolving the issue here. I'd contact NTL if I thought they could seriously solve it, but I really don't.
Edit:
Don't know if this highlights anything to anyone smarter than me?
Quote:
Tracing route to cableforum.co.uk [66.199.235.18]
over a maximum of 30 hops:
1 10 ms 6 ms 10 ms 10.22.240.1
2 6 ms 5 ms 6 ms oldh-t2cam1-a-ge95.inet.ntl.com [80.5.164.13]
3 7 ms 10 ms 9 ms mant-t2core-a-ge-wan81.inet.ntl.com [213.104.242.73]
4 9 ms 8 ms 8 ms man-bb-a-so-210-0.inet.ntl.com [213.105.174.18]
5 23 ms 12 ms 7 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
6 28 ms 12 ms 13 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
7 20 ms 14 ms 16 ms bre-bb-b-so-100-0.inet.ntl.com [213.105.172.234]
8 18 ms 16 ms 15 ms bre-bb-a-ae0-0.inet.ntl.com [213.105.172.86]
9 16 ms 19 ms 16 ms redb-ic-1-so-010-0.inet.ntl.com [62.253.188.106]
10 18 ms 26 ms 17 ms linx-gw1.peer1.net [195.66.224.156]
11 94 ms 93 ms 95 ms oc12-pos5-0.nyc-telx-dis-a.peer1.net [216.187.115.225]
12 105 ms 94 ms 92 ms 64.34.84.114
13 122 ms 96 ms 95 ms 65.125.239.146
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Pinging cableforum.co.uk [66.199.235.18] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
|