Can browse, but cant ftp or anything else

There is something very odd going on at the moment. I have lost tcp connectivity to one of my servers over the NTL network, I can connect to it fine from other networks.

[Stuartbe]

Originally Posted by pem

There is something very odd going on at the moment. I have lost tcp connectivity to one of my servers over the NTL network, I can connect to it fine from other networks.

I can connect to the server fine via TS - But stew cant ???

He can connect to mine though - WTF is going on...

[Stewh]

something very odd is the way I see it as well, I am pretty sure that it's not anything in my configuration or the server config.

Is it possible that a range of ip addresses are banned on a server which is part of the route taken to another server or something wierd like that?

[Avatar]

Originally Posted by Stewh

something very odd is the way I see it as well, I am pretty sure that it's not anything in my configuration or the server config.

Is it possible that a range of ip addresses are banned on a server which is part of the route taken to another server or something wierd like that?

if any one routes through tele-ic-2-so-000-0.inet.ntl.com that could be your problem, its dropping packets all over the place, no idea what it is though...sounds like a backbone link down at telehouse though

[Stewh]

Tracert is ...

Tracing route to ***.***.***.*** over a maximum of 30 hops

1 1 ms <1 ms <1 ms ***.***.***.***
2 11 ms 12 ms 10 ms 10.184.111.254
3 12 ms 12 ms 17 ms nott-t2cam1-b-ge-wan41-116.inet.ntl.com [80.4.46
.245]
4 13 ms 12 ms 11 ms not-t2core-b-ge-wan73.inet.ntl.com [80.1.79.205]

5 13 ms 10 ms 12 ms nth-bb-b-so-200-0.inet.ntl.com [62.253.185.37]
6 17 ms 13 ms 14 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]

7 46 ms * * tele-ic-2-so-000-0.inet.ntl.com [62.253.185.86]

8 28 ms 22 ms 24 ms ldn-th-i1-geth3-0.telia.net [195.66.226.48]
9 22 ms 24 ms 24 ms ldn-bb2-pos1-2-0.telia.net [213.248.74.13]
10 102 ms 97 ms 96 ms nyk-bb2-pos6-0-0.telia.net [213.248.65.94]
11 103 ms 103 ms 103 ms ash-bb1-pos5-0-0.telia.net [213.248.80.138]
12 115 ms 116 ms 114 ms atl-bb1-pos0-1-0.telia.net [213.248.80.58]
13 * * * Request timed out.
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.

[Stuartbe]

Tracing route to ***.***.***.*** over a maximum of 30 hops

1 16 ms 31 ms 31 ms cisco.pix.rtnl.rbd [10.0.0.5]
2 15 ms 31 ms 32 ms ***.***.***.***
3 15 ms 32 ms 31 ms lutn-t2cam1-b-ge93.inet.ntl.com [80.4.118.173]
4 15 ms 32 ms 31 ms lutn-t2core-b-ge-wan63.inet.ntl.com [213.107.47.
209]
5 15 ms 31 ms 32 ms nth-bb-b-so-220-0.inet.ntl.com [62.253.188.189]

6 63 ms 31 ms 31 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]

7 63 ms * 47 ms tele-ic-2-so-000-0.inet.ntl.com [62.253.185.86]

8 32 ms 31 ms 47 ms ldn-th-i1-geth3-0.telia.net [195.66.226.48]
9 15 ms 31 ms 32 ms ldn-bb1-pos0-3-0.telia.net [213.248.74.5]
10 16 ms 31 ms 31 ms ldn-bb2-pos0-0-0.telia.net [213.248.64.162]
11 156 ms 94 ms 141 ms nyk-bb2-pos6-0-0.telia.net [213.248.65.94]
12 109 ms 141 ms * ash-bb1-pos5-0-0.telia.net [213.248.80.138]
13 109 ms 125 ms 125 ms atl-bb1-pos0-1-0.telia.net [213.248.80.58]
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.

Can he and you do a tracert and see if there is anything in common. I can ping my server but I cannot get any tcp traffic to it. Not tried UDP.

This is the NTL section of my route to my server;

2 30 ms 9 ms 8 ms 10.145.239.254
3 8 ms 9 ms 9 ms nott-t2cam1-b-ge-wan42-122.inet.ntl.com [80.4.46.201]
4 8 ms 11 ms 13 ms not-t2core-b-pos41.inet.ntl.com [80.1.79.189]
5 13 ms 10 ms 30 ms nth-bb-b-so-200-0.inet.ntl.com [62.253.185.37]
6 11 ms 12 ms 32 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]
7 * * 42 ms tele-ic-2-so-000-0.inet.ntl.com [62.253.185.86]
8 14 ms 12 ms 11 ms linx1.lon1.as8553.net [195.66.224.126]

[Avatar]

Originally Posted by stuartbe

Tracing route to ***.***.***.*** over a maximum of 30 hops

1 16 ms 31 ms 31 ms cisco.pix.rtnl.rbd [10.0.0.5]
2 15 ms 31 ms 32 ms ***.***.***.***
3 15 ms 32 ms 31 ms lutn-t2cam1-b-ge93.inet.ntl.com [80.4.118.173]
4 15 ms 32 ms 31 ms lutn-t2core-b-ge-wan63.inet.ntl.com [213.107.47.
209]
5 15 ms 31 ms 32 ms nth-bb-b-so-220-0.inet.ntl.com [62.253.188.189]

6 63 ms 31 ms 31 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]

7 63 ms * 47 ms tele-ic-2-so-000-0.inet.ntl.com [62.253.185.86]

8 32 ms 31 ms 47 ms ldn-th-i1-geth3-0.telia.net [195.66.226.48]
9 15 ms 31 ms 32 ms ldn-bb1-pos0-3-0.telia.net [213.248.74.5]
10 16 ms 31 ms 31 ms ldn-bb2-pos0-0-0.telia.net [213.248.64.162]
11 156 ms 94 ms 141 ms nyk-bb2-pos6-0-0.telia.net [213.248.65.94]
12 109 ms 141 ms * ash-bb1-pos5-0-0.telia.net [213.248.80.138]
13 109 ms 125 ms 125 ms atl-bb1-pos0-1-0.telia.net [213.248.80.58]
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.

its not just droping for me then....glad to se that

[Stuartbe]

Originally Posted by Avatar

if any one routes through tele-ic-2-so-000-0.inet.ntl.com that could be your problem, its dropping packets all over the place, no idea what it is though...sounds like a backbone link down at telehouse though

So how can I TS to his server but he cant ?????

[Stewh]

and vice versa

[Stuartbe]

Originally Posted by pem

Can he and you do a tracert and see if there is anything in common. I can ping my server but I cannot get any tcp traffic to it. Not tried UDP.

This is the NTL section of my route to my server;

2 30 ms 9 ms 8 ms 10.145.239.254
3 8 ms 9 ms 9 ms nott-t2cam1-b-ge-wan42-122.inet.ntl.com [80.4.46.201]
4 8 ms 11 ms 13 ms not-t2core-b-pos41.inet.ntl.com [80.1.79.189]
5 13 ms 10 ms 30 ms nth-bb-b-so-200-0.inet.ntl.com [62.253.185.37]
6 11 ms 12 ms 32 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]
7 * * 42 ms tele-ic-2-so-000-0.inet.ntl.com [62.253.185.86]
8 14 ms 12 ms 11 ms linx1.lon1.as8553.net [195.66.224.126]

All the tracerts seem the same - What the hell is going on ??????

[Avatar]

Tracing route to newswww.bbc.net.uk [212.58.226.40]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.100.101
2 55 ms 58 ms 77 ms 172.28.167.254
3 35 ms 66 ms 16 ms lutn-t2cam1-b-ge92.inet.ntl.com [80.4.118.129]
4 73 ms 23 ms 59 ms lutn-t2core-b-ge-wan64.inet.ntl.com [213.107.47
213]
5 15 ms 132 ms 25 ms nth-bb-b-so-220-0.inet.ntl.com [62.253.188.189]
6 25 ms 12 ms 18 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]
7 82 ms * * tele-ic-2-so-000-0.inet.ntl.com [62.253.185.86]
8 23 ms 13 ms 13 ms 212.58.239.217
9 91 ms 12 ms 13 ms news.bbc.co.uk [212.58.226.40]



/me poinst to hop 7 on everyones traces

tele-ic-2-xxx will always look bad in tracerts because it gives replying to pings a low priority.

However - in this case it does seem to be the prime suspect because my servers that I can connect to do not route via it.

[Stewh]

But is there any way to change how you are routed?

[Stuartbe]

Originally Posted by Stewh

But is there any way to change how you are routed?

Sadly not my m8 ..... Anyone know any cisco core router passwords ??

conf t - anyone