Baguley behaving badly?

[altis]

It's really playing up for me at the momentTracing route to bbc.co.uk [212.58.224.131]

over a maximum of 30 hops:

1 8 ms 20 ms 9 ms 10.15.80.1
2 9 ms 9 ms 15 ms bagu-t2cam1-b-ge-wan52-122.inet.ntl.com [80.5.162.217]
3 85 ms 276 ms 206 ms bagu-t2core-b-ge-wan63.inet.ntl.com [80.5.161.137]
4 10 ms 11 ms 10 ms lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29]
5 18 ms 80 ms 19 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
6 * 15 ms 16 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
7 14 ms 15 ms 18 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 25 ms 37 ms 37 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86]
9 22 ms 16 ms 18 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
10 22 ms 21 ms 21 ms 212.58.238.129
11 18 ms * 17 ms bbc.co.uk [212.58.224.131]

Trace complete.

Tracing route to bbc.co.uk [212.58.224.131]

over a maximum of 30 hops:

1 * * 27 ms 10.15.80.1
2 10 ms 9 ms 9 ms bagu-t2cam1-b-ge-wan52-122.inet.ntl.com [80.5.162.217]
3 9 ms 8 ms 8 ms bagu-t2core-b-ge-wan63.inet.ntl.com [80.5.161.137]
4 11 ms 10 ms 9 ms lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29]
5 11 ms 12 ms 10 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
6 17 ms 16 ms 16 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
7 16 ms * 15 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 29 ms 27 ms 16 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86]
9 16 ms 16 ms 16 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
10 21 ms 20 ms 22 ms 212.58.238.129
11 16 ms 16 ms 17 ms bbc.co.uk [212.58.224.131]

Trace complete.
:(

[Neil]

Have you rung ntl Tech Support m8?

[Roy MM]

Must be local area fault, no problems N Manchester.

[Bill C]

It's really playing up for me at the momentTracing route to bbc.co.uk [212.58.224.131]

snip


Trace complete.
:(

Altis

I am on the same nodal area as you. I get this


Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:

1 13 ms 7 ms 7 ms 10.15.16.1
2 9 ms 11 ms 9 ms bagu-t2cam1-b-ge-wan52-121.inet.ntl.com [80.
2.213]
3 8 ms 7 ms 8 ms bagu-t2core-b-ge-wan62.inet.ntl.com [80.5.16
3]
4 8 ms 8 ms 9 ms lee-bb-b-so-200-0.inet.ntl.com [213.105.174.

5 9 ms 8 ms 10 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
6 12 ms 15 ms 14 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.2

7 17 ms 14 ms 33 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 28 ms 30 ms 46 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.

9 52 ms 54 ms 23 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.21
10 22 ms 19 ms 20 ms 212.58.238.129
11 24 ms 23 ms 24 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]

Trace complete.

C:\Documents and Settings\bill>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:

1 6 ms 16 ms 8 ms 10.15.16.1
2 8 ms 7 ms 10 ms bagu-t2cam1-b-ge-wan52-121.inet.ntl.com [80.
2.213]
3 22 ms 7 ms 9 ms bagu-t2core-b-ge-wan62.inet.ntl.com [80.5.16
3]
4 11 ms 15 ms 15 ms lee-bb-b-so-200-0.inet.ntl.com [213.105.174.

5 14 ms 15 ms 14 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
6 15 ms 13 ms 22 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.2

7 16 ms 15 ms 17 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 27 ms 32 ms 23 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.

9 14 ms 16 ms 51 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.21
10 22 ms 36 ms 20 ms 212.58.238.129
11 25 ms 23 ms 20 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]

[altis]

Hi Bill. The traces above were taken just before 4pm. Things had been stuttering for a while but they seem back to normal now :) Tracing route to bbc.co.uk [212.58.224.131]

over a maximum of 30 hops:

1 9 ms 15 ms 10 ms 10.15.80.1
2 28 ms 31 ms 9 ms bagu-t2cam1-b-ge-wan52-122.inet.ntl.com [80.5.162.217]
3 42 ms 9 ms 10 ms bagu-t2core-b-ge-wan63.inet.ntl.com [80.5.161.137]
4 13 ms 12 ms 12 ms lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29]
5 13 ms 94 ms 11 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
6 16 ms 15 ms 14 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
7 15 ms 33 ms 17 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 28 ms 31 ms 37 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86]
9 17 ms 17 ms 16 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
10 31 ms 44 ms 22 ms 212.58.238.129
11 20 ms 17 ms 17 ms bbc.co.uk [212.58.224.131]

Trace complete.
I notice that NTL now has it's own port into the Beeb - that's useful!

[kvetner]

I've been having very slow web access in the Baguley area for the last 2 weeks or so. Web, news etc are unaffected, only the web, and https pages more so than http (although both are poor). Pages that used to take about 5 seconds to load now take 30-60 or fail entirely. Just getting on this forum has been a pain.
My anti-virus, firewall, adaware and zonealarm are all up-to-date; I've checked netstat for funny connections and gone through several other steps suggested by NTL on the phone. PC is running Win 98 SE, connecting at 1mbps through the STB. Nothing has changed on the PC (i.e. no new software) other than the web suddenly grinding to a halt. Switching proxies seems to help a little, but not very much. Perhaps some filesharer on my street is hosing the connection (but then why would email still be fine)? NTL haven't replied to my query through their web problem submission page at all.
Anyone else experiencing the same, or at NTL able to assist? Or anyone able to suggest a way to contact NTL which will actually get a meaningful reply?

[Ignition]

http uses the caches, https, news, etc, do not, so I'm lost as to why https pages whould be in strife but other applications which aren't cached would not.

[th'engineer]

Could it be the proxy servers have been using a none ntl one and have no problems was having similar problems recently.But specified none NTL


Could a couple of the proxies be down again

[etccarmageddon]

I've been having very slow web access in the Baguley area for the last 2 weeks or so. Web, news etc are unaffected, only the web, and https pages more so than http (although both are poor). Pages that used to take about 5 seconds to load now take 30-60 or fail entirely. Just getting on this forum has been a pain.
My anti-virus, firewall, adaware and zonealarm are all up-to-date; I've checked netstat for funny connections and gone through several other steps suggested by NTL on the phone. PC is running Win 98 SE, connecting at 1mbps through the STB. Nothing has changed on the PC (i.e. no new software) other than the web suddenly grinding to a halt. Switching proxies seems to help a little, but not very much. Perhaps some filesharer on my street is hosing the connection (but then why would email still be fine)? NTL haven't replied to my query through their web problem submission page at all.
Anyone else experiencing the same, or at NTL able to assist? Or anyone able to suggest a way to contact NTL which will actually get a meaningful reply?no problems here at all during the last 2 weeks and I'm probably connecting to the same nodes as you. try their 0800 number and speak to technical support.

[kvetner]

Aaargh, it's only getting worse and NTL seem unable to help ...

Web pages are still slow and often failing, but upload speeds have gone to pot. I've always found it nigh-on-impossible to upload photos to websites, or via ftp, with NTL, but in addition I'm now unable to send anything other than the smallest emails, and they take forever (anything with more than a couple of lines of text times out at the smtp server) - I've run some upload speed tests and when they get anything above 0kbps it's no more than 5kbps.

NTL's very helpful telephone support technician agrees that this isn't right, but is stymied. Like the last one, he blames anti-virus, firewall or filesharing, but I'm not running the latter, and even temporarily wiping McAfee and ZoneAlarm out of the registry so none of their componets start at all makes no difference whatsoever to the speed. Resetting the PC, STB etc doesn't help either. I sympathise with the technician's conclusion - there's not much else they can say from a call centre on the other side of the world. But does anyone have any suggestions as to how I can get someone more local to investigate e.g. maybe the local UBR is knackered, for example?

My next step is to call out an engineer; or borrow a laptop and plug that in to try and rule out the PC as being part of the problem. Any other ideas?

[MovedGoalPosts]

How are you connecting to the STB, ethernet or USB. Ethernet can be more reliable, but make sure you have current drivers.

Many of the older PACE STBs will struggle with 1Mbps. It's on the limits of their capacity. My own broadband improved markedly when my old PACE 1000 series STB was replaced with a Samsung at the end of last year, and then I was only on the old 750kpbs service.

I'd suggest you keep pestering ntl to show that it is not their network at fault. Best way of doing that is to keep phoning CS: faults.

[kvetner]

I connect via USB, numerous attempts to connect via Ethernet have failed although I haven't got around to sticking in a replacement Ethernet card yet (the current Ethernet card certainly isn't entirely at fault since I've used it recently for local networking successfully). I don't see how the USB connection can be the cause though: this slowness just started a couple of weeks ago, I've had a USB connection happily since I got NTL over a year ago; the STB (Pace 4000) hasn't changed; and I was running quite happily on 1mbps for some time after upgrading. This is all what makes me think it's a problem on the network rather than on the PC or STB.

Yes, I will keep pestering them :rolleyes: It's either that or switch to another supplier and I'm keen to avoid the upheaval ...

[MovedGoalPosts]

Main reason for lack of preference for USB is that it relies on hardware (CPU) and other resources in your PC, rather than dedicated functionality of the ethernet card.

If your ethernet card works locally, then there is no reason why you should not be able to use it connected to the STB. Make sure you fully power down the PC and STB (unplug the STB from the wall), connect the wires then switch on.

You should now be able to browse. If not, go to internet explorer (or other browser) and type in the address box "start:ntl" should take you to the registration page.

Before you try that, it might be worth just looking in your internet connections and deleting any settings that might be buried in there. Best setup for ethernet connection is to allow everything to connect automatically.

[phinix]

Main reason for lack of preference for USB is that it relies on hardware (CPU) and other resources in your PC, rather than dedicated functionality of the ethernet card.

If your ethernet card works locally, then there is no reason why you should not be able to use it connected to the STB. Make sure you fully power down the PC and STB (unplug the STB from the wall), connect the wires then switch on.

You should now be able to browse. If not, go to internet explorer (or other browser) and type in the address box "start:ntl" should take you to the registration page.

Before you try that, it might be worth just looking in your internet connections and deleting any settings that might be buried in there. Best setup for ethernet connection is to allow everything to connect automatically.


before he starts deleting anything the best advice that noone
seems to give is simply download (ftp/html/torrent whatever)
a smallish selfbooting :Yikes: linux liveCD and trying to browse through the NTL connection with that.

for instance Slax 5.0.2 works nice with my madwifi pcmcia
laptop machine , never tryed it with a standard rtl PCI net card
(OR whatever U have) but if not, many work just fine.
http://www.alltheinternet.com/texis/open/all?q=livecd+mini
if that can work than it points to a problem with
his (i assume- shouldnt really LOL ) windows OS install.

ohh and just for reference im on 2meg and in wythenshawe too
----------------------------------------------------------------------------------
Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:
1 * * * Request timed out.
2 19 ms 22 ms 27 ms bagu-t2cam1-b-ge96.inet.ntl.com [80.5.162.145]
3 107 ms 205 ms 222 ms bagu-t2core-b-ge-wan63.inet.ntl.com [80.5.161.13
7]
4 160 ms 149 ms 217 ms lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29]
5 356 ms 319 ms 322 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
6 190 ms 151 ms 161 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
7 155 ms 268 ms 246 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 230 ms 111 ms 88 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86]
9 108 ms 19 ms 26 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
10 17 ms 35 ms 18 ms 212.58.238.153
11 22 ms 28 ms 22 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]
Trace complete.

tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:
1 * * * Request timed out.
2 29 ms 97 ms 98 ms bagu-t2cam1-b-ge96.inet.ntl.com [80.5.162.145]
3 7 ms 9 ms 10 ms bagu-t2core-b-ge-wan63.inet.ntl.com [80.5.161.13
7]
4 9 ms 9 ms 8 ms lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29]
5 20 ms 95 ms 96 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
6 22 ms 15 ms 16 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
7 15 ms 18 ms 16 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 146 ms 91 ms 67 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86]
9 37 ms 135 ms 394 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
10 69 ms 93 ms 67 ms 212.58.238.153
11 42 ms 22 ms 27 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]
Trace complete.
the first 1 hop gets me LOl

as you can see its getting worse....................

[kvetner]

I haven't tried a linux CD yet to rule out the OS, but I did plug in a different PC last night and it experienced exactly the same problems, especially with upload speed (2kbps was about the best either machine recorded). Obviously this makes me think that the problem lies outside my machine, either with the STB or with the network beyond. Another call to be made to NTL today ...