New 10meg installed.... 56k performance !!

mpoynter · 21-12-2005, 20:59

This morning i had installed the new 10Meg service from NTL.
I was previuosly on a 3meg service via a Set Top box (samsung)
The guy turned up and simply added a cable model (blue ntl 250) it was from a splitter on the coax cable.
After going thro the install and finally getting it to work i have to say the performance is C%^P !!!! It's like an old 56K modem, a typical NTL page taking 40 to 60 secs to load completely. After spending nearly 1 hour to the new Indian Tech support (as much use as a chocolate Fire Guard) i decided to put the ethernet back into the old STB and low and behold back to a normal FAST service with down loads of over 330.

If it's of any use i'm in South Manchester (i've seen a lot of postings from here)

Any clues or similar experiences ???

SMHarman · 21-12-2005, 22:17

log on to the cable modem
http://192.168.100.1/
root
root

Look at the configuration and what the maximum upstream rate is and report back.

I would guess that the service has not been moved over to the CM.

Have you registered the CM

go to start.ntl ? You might need to go there and type in the UID and password, or have you done that?

quadplay · 21-12-2005, 22:28

Quote:

Originally Posted by SMHarman

go to start.ntl ? You might need to go there and type in the UID and password, or have you done that?

start.ntl is only for Broadband via a STB - the registration site for Cable Modems is https://autoreg.autoregister.net/

However, the SACM must be registered otherwise you wouldn't be able to browse at all, unless you had a proxy specified on a port other than 80, in which case you'd get speeds around 150k.

mpoynter · 26-12-2005, 22:50

Posted before but still no Joy.
I upgraded to 10 meg from 3 meg two days before xmas.
NTL installed a new NTL 250 blue Cable Modem.
Registered ok but then the problems... it's better with a 56K modem !!!
Microsoft, NTL, BBC pages taking between 1 and 2 minutes to complete....
Many times pages just never appear, often giving timeouts.
Downloading service pack 2 or similar from Microsoft gives between 10 / 20 KBsec at best.
NTL India tried to blame PC, which was like lightening with 3Meg.... so i grabbed a brand new Virgin Laptop from work and still no difference.
Latest from India... download a large file, then switch of for about half and hour and repeat for at least 3 times (speeds will gradulally get better he told me) this i've done and still no better..

HELP please where do i turn to next.... this is like having your right arm cut off with a next to useless broadband.

Both PC's tried are XP service pack 2. Ethernet connection to cable modem.
Browser IE 6. Living in the Manchester Area

Hope anyone can help

Martin Poynter

26-12-2005, 23:18

Can you get any stats from the CM (e.g. 192.168.100.1) e.g. power levels, SNR values?

Try tracert to the BBC to see where the packets are being lost e.g ethernet cable, CM, UBR or beyond.

Looks like it could be a network levels prob or dodgy CM. I would get back to CS with trace results and get them to chase the answers.

Good luck!

mpoynter · 26-12-2005, 23:37

As suggested in last post here is the info required I hope
I don't have a clue what it all means

Martin

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Mpoynter>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:
1 8 ms 5 ms 8 ms 10.13.192.1
2 8 ms 26 ms 8 ms oldh-t2cam1-b-ge-wan52-125.inet.ntl.com [80.5.16
4.229]
3 8 ms 7 ms 10 ms manc-t3core-1b-ge-012-0.inet.ntl.com [213.104.24
2.201]
4 8 ms 10 ms 10 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]
5 16 ms 13 ms 14 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
6 14 ms 16 ms 17 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
7 15 ms 19 ms 15 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
8 34 ms 16 ms 16 ms 212.58.238.189
9 17 ms 16 ms 33 ms 212.58.238.133
10 15 ms 14 ms 19 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]
Trace complete.
C:\Documents and Settings\Mpoynter>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:
1 8 ms 8 ms 7 ms 10.13.192.1
2 18 ms 22 ms 55 ms oldh-t2cam1-b-ge-wan52-125.inet.ntl.com [80.5.16
4.229]
3 7 ms 8 ms 9 ms manc-t3core-1b-ge-012-0.inet.ntl.com [213.104.24
2.201]
4 8 ms 9 ms 16 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]
5 18 ms 14 ms 15 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
6 15 ms 14 ms 25 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
7 20 ms 16 ms 16 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
8 17 ms 16 ms 17 ms 212.58.238.189
9 17 ms 15 ms 18 ms 212.58.238.133
10 24 ms 14 ms 15 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]
Trace complete.
C:\Documents and Settings\Mpoynter>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:
1 5 ms 6 ms 7 ms 10.13.192.1
2 7 ms 10 ms 9 ms oldh-t2cam1-b-ge-wan52-125.inet.ntl.com [80.5.16
4.229]
3 7 ms 8 ms 23 ms manc-t3core-1b-ge-012-0.inet.ntl.com [213.104.24
2.201]
4 15 ms 20 ms 18 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]
5 17 ms 21 ms 32 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
6 16 ms 14 ms 14 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
7 31 ms 17 ms 17 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
8 18 ms 16 ms 17 ms 212.58.238.189
9 17 ms 18 ms 16 ms 212.58.238.133
10 24 ms 15 ms 19 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]
Trace complete.
C:\Documents and Settings\Mpoynter>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:
1 6 ms 7 ms 7 ms 10.13.192.1
2 7 ms 10 ms 8 ms oldh-t2cam1-b-ge-wan52-125.inet.ntl.com [80.5.16
4.229]
3 8 ms 9 ms 9 ms manc-t3core-1b-ge-012-0.inet.ntl.com [213.104.24
2.201]
4 23 ms 25 ms 12 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]
5 16 ms 13 ms 13 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
6 15 ms 17 ms 15 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
7 24 ms 17 ms 15 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
8 19 ms 16 ms 17 ms 212.58.238.189
9 24 ms 23 ms 36 ms 212.58.238.133
10 22 ms 22 ms 17 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]
Trace complete.
C:\Documents and Settings\Mpoynter>

Downstream Lock : LockedDownstream Channel Id : 0Downstream Frequency : 586750000 HzDownstream Modulation : QAM64Downstream Symbol Rate : 6952 Ksym/sec

First Time Last Time Counts Level ID Text
Time Not Established Time Not Established 6 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Sat Dec 24 20:21:47 2005 Sat Dec 24 20:21:47 2005 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un...
Time Not Established Time Not Established 1 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Sat Dec 24 20:04:04 2005 Sat Dec 24 20:04:04 2005 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un...
Sat Dec 24 19:40:44 2005 Sat Dec 24 19:40:44 2005 1 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Time Not Established Time Not Established 1 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Wed Dec 21 14:05:13 2005 Wed Dec 21 14:05:13 2005 1 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Time Not Established Time Not Established 6 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Time Not Established Time Not Established 2 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 88 Critical(3) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC f...
Time Not Established Time Not Established 608 Critical(3) 84000100 SYNC Timing Synchronization failure - Failed to acquire QAM/Q...

Downstream Interleave Depth : taps12Increment17Downstream Receive Power Level : 3.6 dBmVDownstream SNR : 29.7 dB

Upstream Lock : LockedUpstream Channel ID : 5Upstream Frequency : 41584000 HzUpstream Modulation : QPSKUpstream Symbol Rate : 2560 Ksym/secUpstream transmit Power Level : 41.0 dBmVUpstream Mini-Slot Size : 2

27-12-2005, 00:13

SYNC issues are commonly to do with Downstream problems, looks like the Signal to noise ratio is not too good (at 25dB some CM's are known to often disconnect entirely) Power level is not too bad but not the best it could be.

CS should be able to check the SNR and Power levels and they should see a possible issue.

However traces don't look too bad (no hugely long responses).

You could try sending 100 or 200 pings to the BBC and see if any packets are being lost (if any).

Good luck!

carlingman · 27-12-2005, 02:45

Quote:

Originally Posted by mpoynter

snip Downstream Lock : LockedDownstream Channel Id : 0Downstream Frequency : 586750000 HzDownstream Modulation : QAM64Downstream Symbol Rate : 6952 Ksym/sec

Downstream Interleave Depth : taps12Increment17Downstream Receive Power Level : 3.6 dBmVDownstream SNR : 29.7 dB

Upstream Lock : LockedUpstream Channel ID : 5Upstream Frequency : 41584000 HzUpstream Modulation : QPSKUpstream Symbol Rate : 2560 Ksym/secUpstream transmit Power Level : 41.0 dBmVUpstream Mini-Slot

Hi, been a while since I worked for them and am not familiar with this new modem but unless they have changed the mhz frequency recently I think this maybe locking to the worng frequency as it used to be 402750000.

Unless of course your in an ex-cable and wireless area and then the 586750000 is correct as it is the eurodocsis frequency and is fine.

I will sit back and await more comments from the recent guys.

Maybe worth giving support a call and see if the levels are varying.

Ignition · 27-12-2005, 18:33

Note the chap mentions having his internet via an STB previously, which was never available on anything apart from the EuroDOCSIS platforms

Also

Downstream Symbol Rate : 6952 Ksym/sec

Says EuroDOCSIS, original standard DOCSIS doesn't have that symbol rate in any modulation profile.

(For the TW chap)

EuroDOCSIS is more particular about SNR at lower modulation rates than standard DOCSIS due to the wider carrier width. At 64QAM it's similar to 256QAM in terms of the SNR it requires to function properly.

Also sync issues tend to be due to upstream problems as this section of the plant is far more vulnerable to noise. The issues that TW might see on their network are due in no small part to the modulation upgrades they do on unsuitable areas of their network to resolve congestion knowing that some of the modems on there will fall off line. You guys tend to take the hit of faults and resolve them later. On the ntl network the vast majority of faults are due to upstream noise and power issues as that part of the network is the most inclined to noise and disruption and is at noisier frequencies.

-----------------

To the original poster, try connecting the modem on its' own directly to the cable point without the splitter or the STB involved and see how it goes. If it works alright, which I'm inclined to think it will considering you're reported no issues with TV, then you need a service call to investigate cables and splitter. If still faulty you will need a service call anyway to investigate the cable coming from the wall and the drop itself.

mpoynter · 28-12-2005, 22:44

Sorted !!!!

It turned out be an autosensing problem between my Ethernet Card (no name) and the cable Modem... new card end of problem and downloading at around 1.1meg from Microsoft.

Thanks for all suggestions

Martin

andybarker · 29-12-2005, 00:19

Crikey... CS blame the PC and they are right... that has to be a first!!

Ignition · 29-12-2005, 11:44

MMMmmm I'm still a bit concerned about the loss of synch your log showed but if it's all ok now maybe that was just a blip planned to send me the wrong way in the diagnosis

Glad it's sorted.

Andy, actually the vast majority of faults reported are due to the customer PCs