Slow broadband ... ?

[darren] · 06-09-2004, 20:06

For the last two weeks my broadband connection has been acting strange. I have the 750k connection and recently the following things happening browsing;

- slow web site address lookup on dns
- slow page loading, images can take over a minute to finally download
- page being blank or stylesheet not downloading
- clicking links not retrieving pages, browser tries then stops
- uploading files to webmail and here (3 tries to do it) don't always work

Have this in Firefox and IE. The speed fluctuates and can seem link a dialup at times! I'm pretty sure that it started after my speed upgrade but that may not be the cause.

I rang ntl support (30min wait!) he got me to try repairing network connection. Shut down firewall so he could ping me and he reckons I had 'flutuations' in my ping. After trying a Spybot and Adaware scan like he said = no spyware.

Don't fancy waiting 30mins to get to them so hoped someone here might help?

I installed Ethereal to try and find any weird traffic. I just did a 60 second capture while not using web.

For a 60 second capture I have 1087 packets for ARP protocol.

An example dump is ....

Code:

No.     Time        Source                Destination           Protocol Info
      1 0.000000    81.108.142.1          Broadcast             ARP      Who has 213.106.163.163?  Tell 213.106.163.1

Frame 1 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:03:fe:e6:30:8c, Dst: ff:ff:ff:ff:ff:ff
Address Resolution Protocol (request)

No.     Time        Source                Destination           Protocol Info
      2 0.061875    81.108.142.1          Broadcast             ARP      Who has 81.108.142.154?  Tell 81.108.142.1

Frame 2 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:03:fe:e6:30:8c, Dst: ff:ff:ff:ff:ff:ff
Address Resolution Protocol (request)

No.     Time        Source                Destination           Protocol Info
      3 0.276732    81.108.142.1          Broadcast             ARP      Who has 213.106.163.252?  Tell 213.106.163.1

Frame 3 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:03:fe:e6:30:8c, Dst: ff:ff:ff:ff:ff:ff
Address Resolution Protocol (request)

No.     Time        Source                Destination           Protocol Info
      4 0.358996    81.108.142.1          Broadcast             ARP      Who has 80.4.215.101?  Tell 80.4.215.1

Frame 4 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:03:fe:e6:30:8c, Dst: ff:ff:ff:ff:ff:ff
Address Resolution Protocol (request)

No.     Time        Source                Destination           Protocol Info
      5 0.371212    81.108.142.1          Broadcast             ARP      Who has 82.6.65.232?  Tell 82.6.65.254

Frame 5 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:03:fe:e6:30:8c, Dst: ff:ff:ff:ff:ff:ff
Address Resolution Protocol (request)

No.     Time        Source                Destination           Protocol Info
      6 0.457007    81.108.142.1          Broadcast             ARP      Who has 80.4.215.221?  Tell 80.4.215.1

Frame 6 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:03:fe:e6:30:8c, Dst: ff:ff:ff:ff:ff:ff
Address Resolution Protocol (request)

No.     Time        Source                Destination           Protocol Info
      7 0.593926    81.108.142.1          Broadcast             ARP      Who has 80.4.215.236?  Tell 80.4.215.1

Frame 7 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:03:fe:e6:30:8c, Dst: ff:ff:ff:ff:ff:ff
Address Resolution Protocol (request)

No.     Time        Source                Destination           Protocol Info
      8 0.644932    81.108.142.1          Broadcast             ARP      Who has 81.97.70.192?  Tell 81.97.70.254

Frame 8 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:03:fe:e6:30:8c, Dst: ff:ff:ff:ff:ff:ff
Address Resolution Protocol (request)

I have attached a text extract from Etehreal and attached.

Is this normally?
Has anyone else had slow network speed in wirral area?

My ip address is 213.106.163.x and on bagu.broadband area.

Thanks, Darren

**Paul M** · 06-09-2004, 21:46

ARP traffic is perfectly normal and necessary.

**Matt D** · 06-09-2004, 21:58

Re: the slowness etc.

Have you tried using a different proxy server?

http://www.cableforum.co.uk/kb/12/ho...pecify-a-proxy

http://www.cableforum.co.uk/kb/47/li...ers-old-format

http://www.cableforum.co.uk/kb/84/li...ers-new-format

Also, try a speed test & post back the results:

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

or

http://www.broadbandspeedtest.net/

Upload speed test: http://www.pcpitstop.com/internet/BandwidthUpTest.asp

[darren] · 07-09-2004, 19:53

Tried the stuff you mentioned.

Used http://www.all-nettools.com/pr.htm to detect proxy.
Currently set at Baguley 8 = bagu-cache-8.server.ntli.net

Download test from robin walker's page:

Code:

Tue, 07 Sep 2004 18:15:39 GMT
1st 128K took 1484 ms = 88323 Bytes/sec = approx 735 kbits/sec
2nd 128K took 1469 ms = 89225 Bytes/sec = approx 742 kbits/sec
3rd 128K took 1484 ms = 88323 Bytes/sec = approx 735 kbits/sec
4th 128K took 1391 ms = 94229 Bytes/sec = approx 784 kbits/sec

Looks ok, but still slow surfing?

Upload test will not work. Turned off firewall and stil no joy. I tried to upload a 10k file to my web email account as attachment. I had to do 8 times as it kept timeing out or just taking longer than 5mins!!! 10k file.

Trying Baguley 7 for proxy server so going to restart browser and post back....

[darren] · 07-09-2004, 20:05

Tried bagu 7, 4, 1 and manu 11.

All taking 12 to 25 secs a page just tio this site!

Have firewall disabled and did ping to site...

Code:

Pinging cableforum.co.uk [66.199.235.18] with 32 bytes of data:

Reply from 66.199.235.18: bytes=32 time=93ms TTL=50
Reply from 66.199.235.18: bytes=32 time=93ms TTL=50
Reply from 66.199.235.18: bytes=32 time=92ms TTL=50
Reply from 66.199.235.18: bytes=32 time=91ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=89ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=91ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=96ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=120ms TTL=50
Reply from 66.199.235.18: bytes=32 time=91ms TTL=50
Request timed out.
Reply from 66.199.235.18: bytes=32 time=92ms TTL=50
Reply from 66.199.235.18: bytes=32 time=92ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=89ms TTL=50
Reply from 66.199.235.18: bytes=32 time=91ms TTL=50
Reply from 66.199.235.18: bytes=32 time=92ms TTL=50
Reply from 66.199.235.18: bytes=32 time=91ms TTL=50
Reply from 66.199.235.18: bytes=32 time=91ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=111ms TTL=50
Reply from 66.199.235.18: bytes=32 time=89ms TTL=50
Reply from 66.199.235.18: bytes=32 time=91ms TTL=50
Reply from 66.199.235.18: bytes=32 time=93ms TTL=50
Reply from 66.199.235.18: bytes=32 time=99ms TTL=50
Reply from 66.199.235.18: bytes=32 time=94ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50
Reply from 66.199.235.18: bytes=32 time=92ms TTL=50
Reply from 66.199.235.18: bytes=32 time=92ms TTL=50
Reply from 66.199.235.18: bytes=32 time=91ms TTL=50
Request timed out.
Reply from 66.199.235.18: bytes=32 time=91ms TTL=50
Reply from 66.199.235.18: bytes=32 time=90ms TTL=50

Ping statistics for 66.199.235.18:
    Packets: Sent = 44, Received = 42, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
    Minimum = 89ms, Maximum = 120ms, Average = 92ms

I'm sure that's not good! The ntl engineer said when pinging me he have timeouts as well. Wonder if he can ping STB to see if it's pc or STB?

I have scanned for spyware/trojans as ntl guy asked and nothing.

Thanks for help so far and I hope someone has an idea because I don't!

Darren

daxx · 07-09-2004, 20:18

getting similar times from bagu8 in SK9 through a samsung box but sites load OK and uploads go through fine

Pinging cableforum.co.uk [66.199.235.18] with 32 bytes of data:

Reply from 66.199.235.18: bytes=32 time=79ms TTL=49
Request timed out.
Reply from 66.199.235.18: bytes=32 time=78ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=93ms TTL=49
Reply from 66.199.235.18: bytes=32 time=78ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=93ms TTL=49
Reply from 66.199.235.18: bytes=32 time=79ms TTL=49
Reply from 66.199.235.18: bytes=32 time=93ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=78ms TTL=49
Reply from 66.199.235.18: bytes=32 time=93ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=78ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=93ms TTL=49
Reply from 66.199.235.18: bytes=32 time=78ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=93ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49
Reply from 66.199.235.18: bytes=32 time=78ms TTL=49
Reply from 66.199.235.18: bytes=32 time=94ms TTL=49

Ping statistics:
Packets: Sent = 32, Received = 31, Lost = 1 (3% loss)
Minimum = 78ms, Maximum = 94ms, Average = 89ms

Jonboy · 07-09-2004, 20:30

ntl has allways been a bag of spanners and allways will be as far as i can see but what the hell at least it works more often than not

**Matt D** · 07-09-2004, 20:36

Try some proxies from different areas.

Also....

What are your connection diagnostics? The ntl techs who post here may find them useful. I think you press "Page Up", "Page Down", "Blue" to get them on an STB connection.

Oh, and have a look at this, to see if there's any other info you can give: http://www.cableforum.co.uk/board/sh...ad.php?t=15305

DeadKenny · 08-09-2004, 13:57

Ping your cable modem (or STB) and see if you get packet loss. If you get none, try pinging the UBR (it's the first hop IP address in a traceroute from you to an external site).

If you get packet loss pinging the UBR, have a look at your modem diagnostics. Typically by browsing to http://192.168.100.1 but it varies per modem.

Post the Downstream power level, downstream SNR and the upstream power level.

With the symptoms you are getting, it's very much likely to be packet loss.

I get the same with slow loading of sites, constantly having to refresh to get pages to load and stylesheets or images sometimes not loading. It's because of packet loss and the packet loss in my case is caused by (apparently) my upstream power level being right on the limit. The explanation given to me was that at the limit the modem adjusts it's power frequently and each adjustment causes a delay and thus packet loss.

It's since got worse for me and the modem is now dropping the upstream lock completely and rebooting (with most of the day being unable to lock on at all).

For info on packet loss see here: http://homepage.ntlworld.com/robin.d...tips/loss.html

and on diagnosing signal levels: http://homepage.ntlworld.com/robin.d...ps/signal.html

[darren] · 10-09-2004, 19:53

Code:

C:\WINDOWS\system32>netstat -s -p tcp

TCP Statistics for IPv4

  Active Opens                        = 186
  Passive Opens                       = 1
  Failed Connection Attempts          = 9
  Reset Connections                   = 12
  Current Connections                 = 2
  Segments Received                   = 9974
  Segments Sent                       = 8206
  Segments Retransmitted              = 406

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    whitebox:1055          localhost:1056         ESTABLISHED
  TCP    whitebox:1056          localhost:1055         ESTABLISHED
  TCP    whitebox:1225          phoenix.cableforum.co.uk:http  LAST_ACK

Code:

Tracing route to www.bbc.net.uk [212.58.224.82]
over a maximum of 30 hops:

  1    18 ms    11 ms    13 ms  10.47.96.1
  2    16 ms    12 ms    16 ms  bagu-t2cam1-b-ge-wan41-109.inet.ntl.com [80.5.16
2.165]
  3    16 ms    16 ms    15 ms  bagu-t2core-b-ge-wan64.inet.ntl.com [80.5.161.14
1]
  4    11 ms    13 ms    14 ms  lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29]
  5    17 ms    14 ms    20 ms  lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
  6    22 ms    22 ms    22 ms  pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

  7     *        *       22 ms  pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
  8    25 ms    21 ms    23 ms  tele-ic-2-so-000-0.inet.ntl.com [62.253.185.86]

  9    21 ms    22 ms    20 ms  212.58.239.217
 10    22 ms    18 ms    20 ms  212.58.238.153
 11     *       27 ms    27 ms  www31.thdo.bbc.co.uk [212.58.224.82]

Trace complete.

Code:

C:\WINDOWS\system32>tracert www.google.co.uk

Tracing route to www.google.akadns.net [216.239.59.147]
over a maximum of 30 hops:

  1    17 ms    15 ms    14 ms  10.47.96.1
  2    15 ms    19 ms    22 ms  bagu-t2cam1-a-ge-wan41-109.inet.ntl.com [80.5.16
2.37]
  3    11 ms    19 ms    17 ms  bagu-t2core-a-ge-wan63.inet.ntl.com [80.5.161.17
]
  4    14 ms    15 ms     *     man-bb-a-so-100-0.inet.ntl.com [62.253.188.25]
  5    22 ms     *       18 ms  ren-bb-b-so-000-0.inet.ntl.com [62.253.185.169]

  6    23 ms    21 ms    19 ms  ren-bb-a-ae0-0.inet.ntl.com [62.253.185.185]
  7    29 ms    32 ms    32 ms  bre-bb-b-so-200-0.inet.ntl.com [62.253.185.166]

  8    30 ms    30 ms    50 ms  telc-ic-1-so-100-0.inet.ntl.com [62.253.188.117]

  9    30 ms    32 ms    42 ms  195.66.226.125
 10    61 ms    40 ms    39 ms  216.239.49.254
 11    49 ms    42 ms    39 ms  216.239.48.158
 12    58 ms    45 ms    47 ms  216.239.49.126
 13    43 ms    41 ms    39 ms  216.239.59.147

Trace complete.

Pinging STB (gather that was the gateway address)

Code:

Pinging 213.106.163.1 with 32 bytes of data:

Reply from 213.106.163.1: bytes=32 time=16ms TTL=255
Reply from 213.106.163.1: bytes=32 time=25ms TTL=255
Reply from 213.106.163.1: bytes=32 time=10ms TTL=255
Reply from 213.106.163.1: bytes=32 time=11ms TTL=255
Reply from 213.106.163.1: bytes=32 time=11ms TTL=255
Reply from 213.106.163.1: bytes=32 time=9ms TTL=255
Reply from 213.106.163.1: bytes=32 time=12ms TTL=255
Reply from 213.106.163.1: bytes=32 time=10ms TTL=255
Reply from 213.106.163.1: bytes=32 time=9ms TTL=255
Reply from 213.106.163.1: bytes=32 time=97ms TTL=255
Reply from 213.106.163.1: bytes=32 time=10ms TTL=255
Reply from 213.106.163.1: bytes=32 time=10ms TTL=255
Reply from 213.106.163.1: bytes=32 time=8ms TTL=255
Reply from 213.106.163.1: bytes=32 time=9ms TTL=255
Reply from 213.106.163.1: bytes=32 time=28ms TTL=255
Reply from 213.106.163.1: bytes=32 time=9ms TTL=255
Reply from 213.106.163.1: bytes=32 time=9ms TTL=255
Reply from 213.106.163.1: bytes=32 time=10ms TTL=255
Request timed out.
Reply from 213.106.163.1: bytes=32 time=10ms TTL=255
Reply from 213.106.163.1: bytes=32 time=13ms TTL=255
Reply from 213.106.163.1: bytes=32 time=14ms TTL=255
Reply from 213.106.163.1: bytes=32 time=11ms TTL=255
Reply from 213.106.163.1: bytes=32 time=11ms TTL=255
Reply from 213.106.163.1: bytes=32 time=11ms TTL=255
Reply from 213.106.163.1: bytes=32 time=10ms TTL=255
Reply from 213.106.163.1: bytes=32 time=9ms TTL=255
Reply from 213.106.163.1: bytes=32 time=10ms TTL=255
Reply from 213.106.163.1: bytes=32 time=14ms TTL=255
Reply from 213.106.163.1: bytes=32 time=11ms TTL=255
Reply from 213.106.163.1: bytes=32 time=10ms TTL=255
Reply from 213.106.163.1: bytes=32 time=11ms TTL=255
Reply from 213.106.163.1: bytes=32 time=10ms TTL=255
Reply from 213.106.163.1: bytes=32 time=15ms TTL=255
Reply from 213.106.163.1: bytes=32 time=58ms TTL=255
Reply from 213.106.163.1: bytes=32 time=10ms TTL=255
Reply from 213.106.163.1: bytes=32 time=8ms TTL=255
Reply from 213.106.163.1: bytes=32 time=11ms TTL=255
Reply from 213.106.163.1: bytes=32 time=27ms TTL=255
Reply from 213.106.163.1: bytes=32 time=11ms TTL=255
Reply from 213.106.163.1: bytes=32 time=10ms TTL=255
Reply from 213.106.163.1: bytes=32 time=15ms TTL=255
Request timed out.
Reply from 213.106.163.1: bytes=32 time=54ms TTL=255
Request timed out.
Reply from 213.106.163.1: bytes=32 time=11ms TTL=255
Reply from 213.106.163.1: bytes=32 time=13ms TTL=255
Request timed out.
Reply from 213.106.163.1: bytes=32 time=11ms TTL=255
Reply from 213.106.163.1: bytes=32 time=13ms TTL=255
Request timed out.
Reply from 213.106.163.1: bytes=32 time=11ms TTL=255
Reply from 213.106.163.1: bytes=32 time=36ms TTL=255
Reply from 213.106.163.1: bytes=32 time=10ms TTL=255
Reply from 213.106.163.1: bytes=32 time=11ms TTL=255

Ping statistics for 213.106.163.1:
    Packets: Sent = 55, Received = 50, Lost = 5 (9% loss),
Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 97ms, Average = 15ms

I think my girlfriend was changing channels at the last bit, but this should not affect it?

Have a pace stb so did Pgup/PgDn/Blue

Downstream power level = ??
SNR = 33.5 and sometimes 38.5, differs as I keep checking it...
Upstream power level = ??

Have had to give up trying to attach anything to emails (web or local client send).

Darren

Ignition · 10-09-2004, 20:56

Darren, please private message me with your current IP address.

Cheers

BBKing · 10-09-2004, 22:18

Quote:

Pinging STB (gather that was the gateway address)

UBR, rather than STB. The packet loss didn't look too clever though

[darren] · 11-09-2004, 16:48

Been onto ntl support today and after extensive testing it's my PC.... according to them.

Few facts;

- ping and tracert dropping packets is ok, that's normal for ntl network
- the netstat results below are acceptable (resent)
- I should reinstall my network card drivers as this can have an affect

my netstat example is;

Code:

TCP Statistics for IPv4

  Active Opens                        = 174
  Passive Opens                       = 1
  Failed Connection Attempts          = 0
  Reset Connections                   = 26
  Current Connections                 = 4
  Segments Received                   = 3073
  Segments Sent                       = 2948
  Segments Retransmitted              = 292

Going to reinstall network driver just for the hell of it. My PC has not been changed for over four months, no new hardware or software. Regularly run spyware scans and never have much but cookies. I don't fancy reinstalling from scratch so I'm basically peeved off.

Might download a linux live cd and see if net is better, if that is slow then I'm just going to cancel my broadband.

D

DeadKenny · 12-09-2004, 01:43

Quote:

Originally Posted by [darren]

Been onto ntl support today and after extensive testing it's my PC.... according to them.

Yeah, and I wouldn't believe that for a second. It's just a stock answer. Blame the customer first and make them reinstall everything before even considering a problem on the network (or at least a problem with the modem). Reinstalling things on Windows can get the customer into a lot of mess if it goes wrong.

Quote:

Few facts;

- ping and tracert dropping packets is ok, that's normal for ntl network

They may say it's normal, but it's unacceptable.

From the traceroute above, your UBR looks to be 10.47.96.1. Ping that and report back with the packet loss. If it's significantly more than the packet loss to the STB, then it's most likely not the PC at fault.

Where you pinged the STB with the public IP address (213.106.163.1), doesn't mean it's the PC because you got packet loss. There's a possibility those packets are going out on the net and back again. If you can find a private IP address for the STB (if there is one), try pinging that.

As you've suggested, try a linux CD. Knoppix is especially good and runs completely from CD. If the results are the same, that should rule out the software on your PC which leaves only the PC hardware, the STB or NTL's network.

BBKing · 12-09-2004, 09:43

Quote:

From the traceroute above, your UBR looks to be 10.47.96.1. Ping that and report back with the packet loss. If it's significantly more than the packet loss to the STB, then it's most likely not the PC at fault.

Shouldn't be pingable on that IP - try your default gateway, as that has to be reachable.

Quote:

Where you pinged the STB with the public IP address (213.106.163.1), doesn't mean it's the PC because you got packet loss. There's a possibility those packets are going out on the net and back again. If you can find a private IP address for the STB (if there is one), try pinging that.

213.106.163.1 is the UBR, not the STB. The STB isn't pingable from the customer's side at all.

N00b may already be on the case with this one, but I can run a status monitoring script that alerts me to a change of status (i.e. if you drop offline) and a continuous ping to the STB. Just need the smart card number or MAC address.