Connection problems in CM18 area
 

Having some problems which I have had since beginning of last week. Basically, connection is very intermittent, web browsing can be painfully slow, sometimes pages load in normal time while other times I can be sitting there for ages. Odd thing is that it seems OK with a constant connection to a news/ftp server where I get sustained rates of 80/90k.

I ran the braodbast speed test and all tests appears OK, other then the pack loss tests which were as follows:-

Packet loss en route to a UK server

gold.ac.uk: 4%
cardiff.ac.uk: 8%

Packet loss en route to a European server

univie.ac.at: 6%
sunsite.cdlab-switch.ch: 2%

Packet loss en route to a USA server

unet.brandeis.edu: 2%
rutgers.edu: 6%

Running a netstat -s -p tcp, gets the following:-

TCP Statistics for IPv4
Active Opens = 278
Passive Opens = 2
Failed Connection Attempts = 6
Reset Connections = 114
Current Connections = 12
Segments Received = 23959
Segments Sent = 16291
Segments Retransmitted = 440

Now, to me the packet loss seems a little high here, but I am no expert. Anyone able to shed any light?

Re: Connection problems in CM18 area
 

Can you post some traceroutes to the servers you mentioned there, please.

Re: Connection problems in CM18 area
 

hi Nuttah :welcome: to Cable Forum

if ftp works then the connection is ok - however ftp traffic doesn't go through the 'transparent' proxy cache, like web stuff does.

So in the first instance I would try a different proxy

- more info about this at Robin Walker's excellent site - click the link

http://homepage.ntlworld.com/robin.d...trancache.html

:)

Re: Connection problems in CM18 area
 

I have tried several different proxies, doesn't appear to be making any difference. Here are a few traceroutes...

Tracing route to scorpio.gold.ac.uk [158.223.1.1]
over a maximum of 30 hops:
1 7 ms 7 ms 6 ms 10.132.231.254
2 6 ms 7 ms 9 ms cmbg-t2cam1-a-v111.inet.ntl.com [80.1.202.53]
3 17 ms 8 ms 15 ms cmbg-t2core-a-ge-wan62.inet.ntl.com [80.1.201.37]
4 12 ms 18 ms 9 ms pop-bb-a-so-200-0.inet.ntl.com [62.253.188.193]
5 12 ms 12 ms 12 ms nth-bb-b-so-400-0.inet.ntl.com [213.105.172.13]
6 15 ms 16 ms 15 ms lee-bb-a-so-600-0.inet.ntl.com [62.253.185.102]
7 19 ms 20 ms 20 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
8 22 ms 21 ms 21 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
9 21 ms 22 ms 21 ms 212.250.14.34
10 * 21 ms 35 ms po2-3.lond-scr4.ja.net [146.97.35.233]
11 22 ms 21 ms 22 ms po0-0.lond-scr.ja.net [146.97.33.33]
12 22 ms 41 ms 22 ms po0-0.london-bar1.ja.net [146.97.35.2]
13 22 ms 38 ms 24 ms ulcc-gsr.lmn.net.uk [146.97.40.34]
14 22 ms 21 ms 22 ms po0-0.kcl-gsr.lmn.net.uk [194.83.100.13]
15 24 ms 25 ms 22 ms goldsmiths.lmn.net.uk [194.83.101.174]
16 23 ms 23 ms 24 ms scorpio.gold.ac.uk [158.223.1.1]

Tracing route to www.cardiff.ac.uk [131.251.0.3]
over a maximum of 30 hops:
1 7 ms 17 ms 5 ms 10.132.231.254
2 8 ms 7 ms 7 ms cmbg-t2cam1-a-v111.inet.ntl.com [80.1.202.53]
3 8 ms 7 ms 7 ms cmbg-t2core-a-ge-wan61.inet.ntl.com [80.1.201.25]
4 18 ms 9 ms 10 ms pop-bb-a-so-200-0.inet.ntl.com [62.253.188.193]
5 12 ms 11 ms 12 ms nth-bb-b-so-400-0.inet.ntl.com [213.105.172.13]
6 15 ms 14 ms 14 ms lee-bb-a-so-600-0.inet.ntl.com [62.253.185.102]
7 19 ms 20 ms 20 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
8 42 ms 23 ms 22 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
9 22 ms 21 ms 32 ms 212.250.14.34
10 22 ms 21 ms 32 ms po3-3.lond-scr4.ja.net [146.97.35.237]
11 23 ms 23 ms 23 ms po1-0.read-scr.ja.net [146.97.33.26]
12 23 ms 23 ms 24 ms po2-0.bris-scr.ja.net [146.97.33.49]
13 28 ms * 25 ms po3-0.cardiff-bar.ja.net [146.97.35.154]
14 27 ms 26 ms 27 ms 146.97.40.94


Tracing route to rutgers.edu [128.6.72.102]
over a maximum of 30 hops:
1 8 ms 8 ms 8 ms 10.132.231.254
2 10 ms 9 ms 10 ms cmbg-t2cam1-b-v111.inet.ntl.com [80.1.202.181]
3 8 ms 13 ms 9 ms cmbg-t2core-b-ge-wan61.inet.ntl.com [80.1.201.153]
4 11 ms 11 ms 15 ms nth-bb-b-so-210-0.inet.ntl.com [62.253.188.197]
5 * 11 ms 13 ms sl-gw11-lon-8-0.sprintlink.net [213.206.159.245]
6 13 ms 14 ms * sl-bb21-lon-11-0.sprintlink.net [213.206.128.58]
7 103 ms 81 ms 81 ms sl-bb21-tuk-10-0.sprintlink.net [144.232.19.69]
8 98 ms 84 ms 84 ms sl-bb23-pen-3-1.sprintlink.net [144.232.20.116]
9 85 ms 84 ms 83 ms sl-bb20-pen-14-0.sprintlink.net [144.232.16.25]
10 84 ms * 83 ms sl-gw2-pen-9-0.sprintlink.net [144.232.5.10]
11 85 ms 87 ms 86 ms sl-rutge1-1-0-0.sprintlink.net [144.223.1.214]
12 85 ms 86 ms 87 ms vlan100-sr02-hill012-svcs.rutgers.edu [128.6.1.22]

Re: Connection problems in CM18 area
 

IIRC there are problems with SNR being low in CM18 and 19

Re: Connection problems in CM18 area
 

Mmm....ya reckon phoning up and having a whinge is likely to get the problem fixed any quicker? Connection keeps on totally stalling at the moment, modem reboot seems to get things working again for a bit, but not for long.

Re: Connection problems in CM18 area
 

Those traceroutes look ok. No packet loss on the ntl network showing itself there. Infact, those pings to your UBR are rather nice. You might want to get Ignition to check out your signal levels though... PM him your MAC address (on the barcode on the modem)