[Merged] BB Speed Upgrades - Page 80

madcap · 19-08-2004, 06:26

Quote:

Originally Posted by MatTman

ok, i just checked the Status page http://www.ntlworld.com/data-feeds/e...osites/upgrade and it tells me my area is upgraded?

does this Only mean the New boxes have been installed but not the Speed upgrade?

It means people on a lower tier and those with SACM's have had thier speed increased 1Mb STB users still have t wait for the switch on.

Stuart · 19-08-2004, 09:18

Quote:

Originally Posted by MatTman

ok, i just checked the Status page http://www.ntlworld.com/data-feeds/e...osites/upgrade and it tells me my area is upgraded?

does this Only mean the New boxes have been installed but not the Speed upgrade?

Nope. NTL won't be upgrading the 1Mb STB users to 1.5Mb untill all the 1Mb users have had their Pace boxes replaced.

No idea when this will happen though.

TheShadow · 19-08-2004, 17:45

Don't hold your breath.

Simply Gray · 20-08-2004, 17:12

Letter from Ntl dated August 2004 awaiting my return from holiday (3 weeks). Says someone will contact me to arrange STB exchange in connection with 1Mb to 1.5Mb upgrade. Some 30 plus telephone callers who didn't leave a message on the answerphone when I was away - Ntl would have left a message wouldn't they?

Dessimat0r · 20-08-2004, 17:26

I have speed problems with the new Samsung box in the Birkenhead area. Check this out.

Pinging www.google.akadns.net [216.239.59.147] with 32 bytes of data:

Reply from 216.239.59.147: bytes=32 time=45ms TTL=245
Reply from 216.239.59.147: bytes=32 time=546ms TTL=245
Reply from 216.239.59.147: bytes=32 time=150ms TTL=245
Reply from 216.239.59.147: bytes=32 time=32ms TTL=245
Reply from 216.239.59.147: bytes=32 time=161ms TTL=245
Reply from 216.239.59.147: bytes=32 time=64ms TTL=245
Reply from 216.239.59.147: bytes=32 time=31ms TTL=245
Reply from 216.239.59.147: bytes=32 time=270ms TTL=245
Request timed out.
Request timed out.
Reply from 216.239.59.147: bytes=32 time=312ms TTL=245
Reply from 216.239.59.147: bytes=32 time=31ms TTL=245
Reply from 216.239.59.147: bytes=32 time=324ms TTL=245
Reply from 216.239.59.147: bytes=32 time=32ms TTL=245
Request timed out.
Reply from 216.239.59.147: bytes=32 time=91ms TTL=245
Request timed out.
Reply from 216.239.59.147: bytes=32 time=31ms TTL=245
Request timed out.
Reply from 216.239.59.147: bytes=32 time=31ms TTL=245
Reply from 216.239.59.147: bytes=32 time=224ms TTL=245
Reply from 216.239.59.147: bytes=32 time=31ms TTL=245
Reply from 216.239.59.147: bytes=32 time=78ms TTL=245
Request timed out.
Reply from 216.239.59.147: bytes=32 time=56ms TTL=245
Reply from 216.239.59.147: bytes=32 time=150ms TTL=245
Reply from 216.239.59.147: bytes=32 time=247ms TTL=245
Request timed out.
Reply from 216.239.59.147: bytes=32 time=302ms TTL=245
Reply from 216.239.59.147: bytes=32 time=33ms TTL=245
Reply from 216.239.59.147: bytes=32 time=32ms TTL=245
Reply from 216.239.59.147: bytes=32 time=105ms TTL=245
Reply from 216.239.59.147: bytes=32 time=60ms TTL=245
Request timed out.
Request timed out.
Reply from 216.239.59.147: bytes=32 time=32ms TTL=245
Reply from 216.239.59.147: bytes=32 time=108ms TTL=245
Reply from 216.239.59.147: bytes=32 time=71ms TTL=245
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.239.59.147: bytes=32 time=30ms TTL=245
Reply from 216.239.59.147: bytes=32 time=280ms TTL=245
Request timed out.
Reply from 216.239.59.147: bytes=32 time=259ms TTL=245
Reply from 216.239.59.147: bytes=32 time=51ms TTL=245
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.239.59.147: bytes=32 time=341ms TTL=245
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.239.59.147: bytes=32 time=236ms TTL=245
Request timed out.
Request timed out.
Reply from 216.239.59.147: bytes=32 time=247ms TTL=245
Reply from 216.239.59.147: bytes=32 time=32ms TTL=245

And my netstat -s:

TCP Statistics for IPv4

Active Opens = 1138
Passive Opens = 260
Failed Connection Attempts = 204
Reset Connections = 55
Current Connections = 31
Segments Received = 178515
Segments Sent = 171253
Segments Retransmitted = 30119

DJ Dave · 21-08-2004, 08:52

lol mine has been done and changed to 300k, however at my sisters 5mins drive away it says she is not in a NTL Area

when she has NTL Broadband 150k.

21-08-2004, 12:03

Quote:

Originally Posted by Dessimat0r

I have speed problems with the new Samsung box in the Birkenhead area. Check this out.

Pinging www.google.akadns.net [216.239.59.147] with 32 bytes of data:

Reply from 216.239.59.147: bytes=32 time=45ms TTL=245
Reply from 216.239.59.147: bytes=32 time=546ms TTL=245
Reply from 216.239.59.147: bytes=32 time=150ms TTL=245
Reply from 216.239.59.147: bytes=32 time=32ms TTL=245
Reply from 216.239.59.147: bytes=32 time=161ms TTL=245
Reply from 216.239.59.147: bytes=32 time=64ms TTL=245
Reply from 216.239.59.147: bytes=32 time=31ms TTL=245
Reply from 216.239.59.147: bytes=32 time=270ms TTL=245
Request timed out.
Request timed out.
Reply from 216.239.59.147: bytes=32 time=312ms TTL=245
Reply from 216.239.59.147: bytes=32 time=31ms TTL=245
Reply from 216.239.59.147: bytes=32 time=324ms TTL=245
Reply from 216.239.59.147: bytes=32 time=32ms TTL=245
Request timed out.
Reply from 216.239.59.147: bytes=32 time=91ms TTL=245
Request timed out.
Reply from 216.239.59.147: bytes=32 time=31ms TTL=245
Request timed out.
Reply from 216.239.59.147: bytes=32 time=31ms TTL=245
Reply from 216.239.59.147: bytes=32 time=224ms TTL=245
Reply from 216.239.59.147: bytes=32 time=31ms TTL=245
Reply from 216.239.59.147: bytes=32 time=78ms TTL=245
Request timed out.
Reply from 216.239.59.147: bytes=32 time=56ms TTL=245
Reply from 216.239.59.147: bytes=32 time=150ms TTL=245
Reply from 216.239.59.147: bytes=32 time=247ms TTL=245
Request timed out.
Reply from 216.239.59.147: bytes=32 time=302ms TTL=245
Reply from 216.239.59.147: bytes=32 time=33ms TTL=245
Reply from 216.239.59.147: bytes=32 time=32ms TTL=245
Reply from 216.239.59.147: bytes=32 time=105ms TTL=245
Reply from 216.239.59.147: bytes=32 time=60ms TTL=245
Request timed out.
Request timed out.
Reply from 216.239.59.147: bytes=32 time=32ms TTL=245
Reply from 216.239.59.147: bytes=32 time=108ms TTL=245
Reply from 216.239.59.147: bytes=32 time=71ms TTL=245
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.239.59.147: bytes=32 time=30ms TTL=245
Reply from 216.239.59.147: bytes=32 time=280ms TTL=245
Request timed out.
Reply from 216.239.59.147: bytes=32 time=259ms TTL=245
Reply from 216.239.59.147: bytes=32 time=51ms TTL=245
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.239.59.147: bytes=32 time=341ms TTL=245
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.239.59.147: bytes=32 time=236ms TTL=245
Request timed out.
Request timed out.
Reply from 216.239.59.147: bytes=32 time=247ms TTL=245
Reply from 216.239.59.147: bytes=32 time=32ms TTL=245

And my netstat -s:

TCP Statistics for IPv4

Active Opens = 1138
Passive Opens = 260
Failed Connection Attempts = 204
Reset Connections = 55
Current Connections = 31
Segments Received = 178515
Segments Sent = 171253
Segments Retransmitted = 30119

Pm on its way

Kneebs · 21-08-2004, 12:25

There's definately something amiss with the samsungs - I've had an engineer out this morning, who's swapped the box for another samsung, and I still get the same rate of packet loss when up/downloading / P2P. I've switched the BB back to the pace and all is fine again.

I've now arranged for a SACM to be installed - I've just got to wait till 1st September for it to be installed.

Kneebs

MatTman · 21-08-2004, 19:06

thats strange, my Samsung is never dropping any Packets.

Dessimat0r · 21-08-2004, 20:11

Quote:

Originally Posted by MatTman

thats strange, my Samsung is never dropping any Packets.

Do netstat -s and put the results here, from under the IPv4 section. Those readings I took above are from when I had Azureus / eMule open.

RazorD · 21-08-2004, 20:57

What sites are you guys using to check? I'm in swindon - doesnt seem any quicker yet

SN3 Post code, like other guys in here, should be moving to 1.5MB.

Psychotext · 21-08-2004, 21:00

Not upgraded yet in Cardiff North. My friends / family in other areas of Cardiff have been upgraded already.

paulyoung666 · 21-08-2004, 21:14

Quote:

Originally Posted by RazorD

What sites are you guys using to check? I'm in swindon - doesnt seem any quicker yet

SN3 Post code, like other guys in here, should be moving to 1.5MB.

try this site for a quick check , try this site for a more comprehensive test

Quote:

Originally Posted by Psychotext

Not upgraded yet in Cardiff North. My friends / family in other areas of Cardiff have been upgraded already.

have you tried rebooting your modem to see if that solves it

Psychotext · 22-08-2004, 01:36

Quote:

Originally Posted by paulyoung666

have you tried rebooting your modem to see if that solves it

Yes, but it doesn't help. My area shows as not being upgraded until September on the postcode checker, must be some sort of difference.

22-08-2004, 01:52

I rebooted my cable modem a couple of weeks ago to see if the area had been upgraded and my connection speed went up to 1.5Mb. Downloading some files tonight I noticed that the connection speed had dropped back down to 1Mb, getting around 125K/s download in Getright and this is confirmed with the other speed tests I have done. Using the NTL postcode checker I`m supposed to not be getting upgraded until September.

I`m in the RG2 area of Reading, is this another area where NTL accidentally released the revised CM config ahead of time?

*Edit* Can`t drop from 1.5Mb to 1.5Mb, d'oh