darren
21-02-2006, 21:05
Hi, a few days ago I noticed that I can no longer access www.1fcnuk.com, its a website that I update for a friend, I can ftp to it fine, but trying to view it via firefox or IE fails, I can simultaneously access it a work via remote desktop with no problem, we have 2Mb SDSL connection with ntl.
The trace route from home is:
Tracing route to www.1fcnuk.com [81.21.75.26]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.254
2 9 ms 9 ms 8 ms 10.12.48.1
3 8 ms 9 ms 8 ms bagu-t2cam1-a-v110.inet.ntl.com [80.5.162.41]
4 9 ms 7 ms 9 ms bagu-t2core-a-ge-wan61.inet.ntl.com [80.5.161.5]
5 7 ms 51 ms 9 ms man-bb-a-so-100-0.inet.ntl.com [62.253.188.25]
6 14 ms 11 ms 31 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.185.194]
7 10 ms 10 ms 11 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
8 15 ms 15 ms 17 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
9 26 ms 18 ms 22 ms tele-ic-2-so-700-0.inet.ntl.com [62.253.184.6]
10 14 ms 16 ms 29 ms 212.250.14.42
11 27 ms 18 ms 17 ms g0-3-6.cr04.tn5.bb.pipex.net [62.72.140.132]
12 29 ms 51 ms 31 ms g5-0-0.cr02.ld3.bb.pipex.net [62.72.156.214]
13 41 ms 23 ms 23 ms v258.ar02.ld3.dco.pipex.net [62.105.126.22]
14 * * * Request timed out.
The trace route for work is:
Tracing route to www.1fcnuk.com [81.21.75.26]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.49.25
2 1 ms 1 ms 1 ms host81-101-87-222.not-set-yet.ntli.net [81.101.87.222]
3 4 ms 32 ms 12 ms mant-lam-1-s100.inet.ntl.com [62.252.220.69]
4 4 ms 4 ms 4 ms manc-t3core-1a-so-712-0.inet.ntl.com [213.104.242.13]
5 8 ms 5 ms 5 ms man-bb-a-so-400-0.inet.ntl.com [213.105.175.1]
6 6 ms 5 ms 6 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.185.194]
7 8 ms 6 ms 6 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
8 11 ms 11 ms 11 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
9 28 ms 10 ms 24 ms tele-ic-2-so-700-0.inet.ntl.com [62.253.184.6]
10 10 ms 10 ms 10 ms 212.250.14.42
11 11 ms 14 ms 11 ms g0-1-5.cr04.tn5.bb.pipex.net [62.72.140.4]
12 17 ms 17 ms 16 ms g5-0-0.cr02.ld3.bb.pipex.net [62.72.156.214]
13 17 ms 16 ms 17 ms v257.ar02.ld3.dco.pipex.net [62.105.126.10]
14 * * * Request timed out.
15 * * * Request timed out.
Interestingly tracert still times out but IE and firefox can browse it quickly.
I also have very poor speeds at www.ebuyer.co.uk when browsing beyond the homepage, it sometimes gets there but mostly times out. Again this works fine at work, who are on NTL buisness.
The trace route from home is:
Tracing route to www.1fcnuk.com [81.21.75.26]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.254
2 9 ms 9 ms 8 ms 10.12.48.1
3 8 ms 9 ms 8 ms bagu-t2cam1-a-v110.inet.ntl.com [80.5.162.41]
4 9 ms 7 ms 9 ms bagu-t2core-a-ge-wan61.inet.ntl.com [80.5.161.5]
5 7 ms 51 ms 9 ms man-bb-a-so-100-0.inet.ntl.com [62.253.188.25]
6 14 ms 11 ms 31 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.185.194]
7 10 ms 10 ms 11 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
8 15 ms 15 ms 17 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
9 26 ms 18 ms 22 ms tele-ic-2-so-700-0.inet.ntl.com [62.253.184.6]
10 14 ms 16 ms 29 ms 212.250.14.42
11 27 ms 18 ms 17 ms g0-3-6.cr04.tn5.bb.pipex.net [62.72.140.132]
12 29 ms 51 ms 31 ms g5-0-0.cr02.ld3.bb.pipex.net [62.72.156.214]
13 41 ms 23 ms 23 ms v258.ar02.ld3.dco.pipex.net [62.105.126.22]
14 * * * Request timed out.
The trace route for work is:
Tracing route to www.1fcnuk.com [81.21.75.26]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.49.25
2 1 ms 1 ms 1 ms host81-101-87-222.not-set-yet.ntli.net [81.101.87.222]
3 4 ms 32 ms 12 ms mant-lam-1-s100.inet.ntl.com [62.252.220.69]
4 4 ms 4 ms 4 ms manc-t3core-1a-so-712-0.inet.ntl.com [213.104.242.13]
5 8 ms 5 ms 5 ms man-bb-a-so-400-0.inet.ntl.com [213.105.175.1]
6 6 ms 5 ms 6 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.185.194]
7 8 ms 6 ms 6 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
8 11 ms 11 ms 11 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
9 28 ms 10 ms 24 ms tele-ic-2-so-700-0.inet.ntl.com [62.253.184.6]
10 10 ms 10 ms 10 ms 212.250.14.42
11 11 ms 14 ms 11 ms g0-1-5.cr04.tn5.bb.pipex.net [62.72.140.4]
12 17 ms 17 ms 16 ms g5-0-0.cr02.ld3.bb.pipex.net [62.72.156.214]
13 17 ms 16 ms 17 ms v257.ar02.ld3.dco.pipex.net [62.105.126.10]
14 * * * Request timed out.
15 * * * Request timed out.
Interestingly tracert still times out but IE and firefox can browse it quickly.
I also have very poor speeds at www.ebuyer.co.uk when browsing beyond the homepage, it sometimes gets there but mostly times out. Again this works fine at work, who are on NTL buisness.