Signal to modem

[Chris W]

Originally Posted by Rough.D

But last night I got ntl to change my UBR t osee if that made any difference but it did not so I am back onto the Birmingham UBR.

I very much doubt that they changed your UBR...

[Rough.D]

This is possible

Hopefully this attenuator will sort out the problem once and for all

[MikeyB]

Hello there,

Sorry to hear about your troubles Rough.D
I too am in Swindon, and go via Birmingham (....brhm.cable.ntl.com) but never have any problems like you describe (oh dear, thats blown it!)

[Rough.D]

Hi MikeyB
Glad to hear you are not having the same probs as I am its been a right royal pain.

The engineer told me that there is a problem in the SN3 area of swindon
as the callout rate for modem problems has increased some 10 fold.

So far so good on a fix my signal was weak so he has boosted it from the box in the street and put in an attenuator (I think) its a filter of sorts lol
Its now a matter of waiting to see if it goes off again.

[mmm]

Originally Posted by Rough.D

This is possible

Hopefully this attenuator will sort out the problem once and for all

I'm pretty sure the uBR is a local thing, that your local fibre connects to, don't see how this can be changed. Other things can be changed such as web proxy DHCP server etc.

My uBR is just an Ip address, no name

Tracing route to www.ntlworld.com [62.253.162.30]
over a maximum of 30 hops:

  1   350 ms   498 ms   643 ms  my-uBR [10.150.71.254]
  2   116 ms   604 ms   455 ms  oxfd-t2cam1-a-ge95.inet.ntl.com [213.106.246.13]
  3   336 ms   427 ms   250 ms  oxfd-t2cam1-b-v99.inet.ntl.com [213.106.247.10]
  4   402 ms   251 ms   632 ms  oxfd-t2core-b-ge-wan61.inet.ntl.com [213.106.245.165]
  5   401 ms   467 ms   248 ms  bre-bb-b-so-700-0.inet.ntl.com [62.253.187.13]
  6   340 ms   289 ms   406 ms  win-bb-a-so-400-0.inet.ntl.com [213.105.172.233]
  7   317 ms   449 ms   245 ms  win-dc-a-v900.inet.ntl.com [62.253.188.162]
  8   384 ms   227 ms   212 ms  www.ntlworld.com [62.253.162.30]

What you are connected to is given by the name of your Ip address, ie my (munged) is

cpc1-oxfd4-3-0-custxx.oxfd.cable.ntl.com

which I'm sure an ntl tech could decode to the location

NB they should boost the signal at the cabinet then fit a Forward Pass Attenuator, so only the downstream is attenuated, not your return path.