Thanks for the replies guys!
Quote:
Originally Posted by Joxer
Just had another thought - if it's your server could you set up a test page on a non standard port and see if you can access that? Not sure how useful it may be but it would narrow it down to a port or service issue. How about ftp? does that work ok?
|
Yes that's a decent idea. FTP is blocked by our University firewall(s) but an unprivileged port should get through.
I've tried traceroute/tracert from Windows, Mac OSX and Linux at home, all with the same outcome.
Quote:
Originally Posted by Cobbydaler
|
Thanks, I'll give that a go.
The problem happened again this morning, I managed to get a tracert to my server and the BBC while it was happening, then another once it had clear up.
Here's the route to my server (I've blanked out my server name for reasons paranoia! Not that I don't trust folk here, but you know...). The first trace is during the problem, the second once it had cleared up:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Richard>tracert xxx.le.ac.uk
Tracing route to xxx.le.ac.uk [143.210.xx.xxx]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms agate.skynet [192.168.1.1]
2 9 ms 15 ms 18 ms 10.227.172.1
3 57 ms 62 ms 39 ms leic-t2cam1-b-v109.inet.ntl.com [82.3.34.197]
4 11 ms 18 ms 6 ms cpc3-ches1-3-1-cust233.lutn.cable.ntl.com [82.3.
32.233]
5 9 ms 14 ms 36 ms nth-bb-b-so-130-0.inet.ntl.com [213.105.172.41]
6 16 ms 14 ms 12 ms tele-ic-1-as0-0.inet.ntl.com [62.253.184.2]
7 16 ms 15 ms 14 ms 212.250.14.34
8 22 ms 21 ms 12 ms so-1-3-0.lond-sbr4.ja.net [146.97.33.9]
9 21 ms 21 ms 17 ms so-2-1-0.leed-sbr1.ja.net [146.97.33.29]
10 26 ms 23 ms 26 ms EMMAN-N1.site.ja.net [146.97.42.10]
11 22 ms 39 ms 27 ms uol3-gw-v320.emman.net [195.195.228.114]
12 19 ms 20 ms 21 ms uol3-gw-5-2-r.emman.net [194.82.121.178]
13 26 ms 21 ms 25 ms 143.210.7.1
14 40 ms 19 ms 22 ms xxx.le.ac.uk [143.210.xx.xxx]
Trace complete.
C:\Documents and Settings\Richard>tracert xxx.le.ac.uk
Tracing route to xxx.le.ac.uk [143.210.xx.xxx]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms agate.skynet [192.168.1.1]
2 23 ms 21 ms 31 ms 10.227.172.1
3 18 ms 20 ms 33 ms leic-t2cam1-b-v109.inet.ntl.com [82.3.34.197]
4 11 ms 12 ms 14 ms cpc3-ches1-3-1-cust233.lutn.cable.ntl.com [82.3.
32.233]
5 13 ms 11 ms 13 ms nth-bb-b-so-130-0.inet.ntl.com [213.105.172.41]
6 38 ms 12 ms 29 ms tele-ic-1-as0-0.inet.ntl.com [62.253.184.2]
7 27 ms 12 ms 22 ms 212.250.14.34
8 19 ms 12 ms 17 ms so-1-3-0.lond-sbr4.ja.net [146.97.33.9]
9 17 ms 17 ms 19 ms so-2-1-0.leed-sbr1.ja.net [146.97.33.29]
10 21 ms 40 ms 19 ms EMMAN-N1.site.ja.net [146.97.42.10]
11 33 ms 18 ms 32 ms uol3-gw-v320.emman.net [195.195.228.114]
12 19 ms 25 ms 22 ms uol3-gw-5-2-r.emman.net [194.82.121.178]
13 21 ms 48 ms 22 ms 143.210.7.1
14 37 ms 48 ms 29 ms xxx.le.ac.uk [143.210.xx.xxx]
Trace complete.
And here's the trace to the BBC, again first during problem, second once clear:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Richard>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.253.73]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms agate.skynet [192.168.1.1]
2 8 ms 8 ms 10 ms 10.227.172.1
3 12 ms 9 ms 40 ms leic-t2cam1-a-v109.inet.ntl.com [82.3.34.69]
4 26 ms 9 ms 12 ms cpc3-ches1-3-1-cust233.lutn.cable.ntl.com [82.3.
32.233]
5 17 ms 19 ms 40 ms lee-bb-a-so-120-0.inet.ntl.com [213.105.172.17]
6 30 ms 24 ms 39 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
7 15 ms 27 ms 40 ms tele-ic-2-as0-0.inet.ntl.com [62.253.184.6]
8 20 ms 15 ms 15 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
9 15 ms 17 ms 17 ms 212.58.238.129
10 17 ms 19 ms 19 ms 212.58.239.222
11 18 ms 43 ms 16 ms www4.cwwtf.bbc.co.uk [212.58.253.73]
Trace complete.
C:\Documents and Settings\Richard>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.253.73]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms agate.skynet [192.168.1.1]
2 12 ms 43 ms 13 ms 10.227.172.1
3 16 ms 11 ms 10 ms leic-t2cam1-a-v109.inet.ntl.com [82.3.34.69]
4 26 ms 18 ms 29 ms cpc3-ches1-3-1-cust233.lutn.cable.ntl.com [82.3.
32.233]
5 13 ms 10 ms 30 ms lee-bb-a-so-120-0.inet.ntl.com [213.105.172.17]
6 27 ms 24 ms 17 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
7 17 ms 18 ms 18 ms tele-ic-2-as0-0.inet.ntl.com [62.253.184.6]
8 13 ms 18 ms 15 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
9 22 ms 23 ms 51 ms 212.58.238.129
10 17 ms 16 ms 19 ms 212.58.239.222
11 30 ms 21 ms 36 ms www4.cwwtf.bbc.co.uk [212.58.253.73]
Trace complete.
C:\Documents and Settings\Richard>
A few things to draw from those I think. First off the DNS resolve seems to work OK during the problem. Second, the routes aren't changing between working and not working intervals. Thirdly the routes only share the first four hops in common (agate is my Linksys router, presumably 10.227.172.1 in my UBR?).
I did a trace to an unaffected site during the problem:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Richard>tracert www.beyond3d.com
Tracing route to beyond3d.com [74.200.65.90]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms agate.skynet [192.168.1.1]
2 27 ms 29 ms 14 ms 10.227.172.1
3 38 ms 14 ms 10 ms leic-t2cam1-a-v109.inet.ntl.com [82.3.34.69]
4 26 ms 22 ms 29 ms leic-t3core-1a-ge-017-0.inet.ntl.com [195.182.17
9.245]
5 56 ms 12 ms 10 ms lee-bb-a-so-120-0.inet.ntl.com [213.105.172.17]
6 25 ms 17 ms 18 ms bre-bb-b-so-200-0.inet.ntl.com [213.105.175.26]
7 19 ms 17 ms 18 ms telc-ic-1-as0-0.inet.ntl.com [62.253.185.74]
8 26 ms 21 ms 25 ms tge2-3.fr4.lon.llnw.net [195.66.226.133]
9 40 ms 43 ms 20 ms ve5.fr3.lon.llnw.net [69.28.171.137]
10 99 ms 89 ms 82 ms tge7-2.fr3.lga.llnw.net [69.28.171.125]
11 114 ms 97 ms 96 ms ve2002.fr4.lga.llnw.net [69.28.171.202]
12 125 ms 124 ms 107 ms tge2-3.fr4.iad.llnw.net [69.28.171.153]
13 * 100 ms 110 ms readnews.defender.tge1-4.fr4.iad.llnw.net [69.28
.158.174]
14 109 ms 102 ms 102 ms colo12c.iad.keepitsecure.net [69.65.112.54]
15 102 ms 132 ms 108 ms cerberus.fileburst.net [74.200.65.90]
Trace complete.
C:\Documents and Settings\Richard>
Which is interesting because it differs from the other two at hop 4 (cpc3-ches1-3-1-cust233.lutn.cable.ntl.com on the affected route).