Over 4 hour outage

[Florence]

Well there is something still wrong since the outage. I have failed to get anywhere near 2mb. So looks like a third call to tech support if it continues to cost me to get the speed issues sorted I will request the cost refunded as since my last call and the speed problem being sorted I have had acceptable speed for 2mb.


Sun, 18 Jun 2006 14:53:53 GMT

1st 512K took 5531 ms = 92.6 KB/sec, approx 763 Kbps, 0.75 Mbps
2nd 512K took 4906 ms = 104.4 KB/sec, approx 860 Kbps, 0.84 Mbps
3rd 512K took 3734 ms = 137.1 KB/sec, approx 1130 Kbps, 1.1 Mbps
4th 512K took 5688 ms = 90 KB/sec, approx 742 Kbps, 0.72 Mbps

Overall Average Speed = approx 874 Kbps, 0.85 Mbps


The modem lost sync the only steady light on the modem was the power, sync was flashing all the time. Tech support checked the modem and agreed the outage had affected me also and was letting NTL know.

[James Henry]

Originally Posted by Florence

Well there is something still wrong since the outage. I have failed to get anywhere near 2mb. So looks like a third call to tech support if it continues to cost me to get the speed issues sorted I will request the cost refunded as since my last call and the speed problem being sorted I have had acceptable speed for 2mb.


Sun, 18 Jun 2006 14:53:53 GMT

1st 512K took 5531 ms = 92.6 KB/sec, approx 763 Kbps, 0.75 Mbps
2nd 512K took 4906 ms = 104.4 KB/sec, approx 860 Kbps, 0.84 Mbps
3rd 512K took 3734 ms = 137.1 KB/sec, approx 1130 Kbps, 1.1 Mbps
4th 512K took 5688 ms = 90 KB/sec, approx 742 Kbps, 0.72 Mbps

Overall Average Speed = approx 874 Kbps, 0.85 Mbps


The modem lost sync the only steady light on the modem was the power, sync was flashing all the time. Tech support checked the modem and agreed the outage had affected me also and was letting NTL know.

A fault in Oldham won't cause a modem connected to Ashton uBR to lose sync so tech support were wrong. You can only lose sync to your uBR and your connection to it will not go to Oldham before it goes to Ashton hubsite. The only thing in Oldham that could possible cause issues would be DHCP problems however it's quite unlikely that your modem is going to lose its' DHCP lease at the same time as there are issues in Oldham, so you probably got blagged.

I've said this before but.... why are you still with this company when you are every 2 - 3 weeks posting complaining about the service you receive? Isn't it getting just a little tiresome posting here complaining?

I dread reading your threads as you are without a doubt the biggest repeat complainer about your broadband service but you still have it and still even defend the company providing you this dodgy service. Why?

If I had anywhere near that level of trouble from my ISP I'd show them the door. I expect and demand at least a reasonable level of service.

Is it really that hard to cancel? You probably have a BT phoneline or could easily enough and don't take their TV. You could easily port the ntl number to BT and take DSL.

Still if you want to keep paying them £25 a month while complaining about the people who have cut deals to pay less, and enjoy an unreliable and unstable service for the privilege I guess that's your prerogative.

I'm not interested by the way in hearing about how bad DSL is by the way, I'm sure for some people it's poor and you see all sorts of horror stories on ISPR but you should be in with a fairly good chance of getting DSL that outperforms your cable. I've never had major issues with DSL, and I'd imagine out of the over 8 million on DSL most of them haven't either.

[Florence]

Originally Posted by James Henry

A fault in Oldham won't cause a modem connected to Ashton uBR to lose sync so tech support were wrong. You can only lose sync to your uBR and your connection to it will not go to Oldham before it goes to Ashton hubsite. The only thing in Oldham that could possible cause issues would be DHCP problems however it's quite unlikely that your modem is going to lose its' DHCP lease at the same time as there are issues in Oldham, so you probably got blagged.

I can only post what I was told, when I ask here first without calling them I get complained at by you and others for asking without contacting them, when I contact them then try to find if others had the same you again complain. I seem to be damned if I do and damned if I don't in your eyes.

Originally Posted by James Henry

I've said this before but.... why are you still with this company when you are every 2 - 3 weeks posting complaining about the service you receive? Isn't it getting just a little tiresome posting here complaining?

One main reason the phone is not in my name and they do not wish to ave to change teh telephone number just to move.

Originally Posted by James Henry

I dread reading your threads as you are without a doubt the biggest repeat complainer about your broadband service but you still have it and still even defend the company providing you this dodgy service. Why?

Nobody forces you to read them if you dread it then don't bother!!

Originally Posted by James Henry

If I had anywhere near that level of trouble from my ISP I'd show them the door. I expect and demand at least a reasonable level of service.

Is it really that hard to cancel? You probably have a BT phoneline or could easily enough and don't take their TV. You could easily port the ntl number to BT and take DSL.

The phone line is not in my name and they do not want to have to change the phone number if we move to BT as simple as that.

Originally Posted by James Henry

Still if you want to keep paying them £25 a month while complaining about the people who have cut deals to pay less, and enjoy an unreliable and unstable service for the privilege I guess that's your prerogative.

I'm not interested by the way in hearing about how bad DSL is by the way, I'm sure for some people it's poor and you see all sorts of horror stories on ISPR but you should be in with a fairly good chance of getting DSL that outperforms your cable. I've never had major issues with DSL, and I'd imagine out of the over 8 million on DSL most of them haven't either.

[AndrewJ]

Originally Posted by Florence

huge snip

I take it your stressed?

Originally Posted by Florence

The phone line is not in my name and they do not want to have to change the phone number if we move to BT as simple as that.

You can number port your number. That is what i did and it took no time at all. So you do NOT lose your number.

I will be moving to Be Unlimited as soon as there Dslam is up and running in Warrington. NTL cannot provide a service that is consistent and certainly STILL have not fixed my billing after 4 months. As for speed that's a complete joke where i live, but i only have 2 months left to put up with them. In the mean time they can continue to refund my payments every month as per there promise that if i have a billing fault i get my service for free .

[Florence]

I have had enough rows over trying to move the phone from NTL he will not listen to any suggestions that include moving the phone.

Its in his name so I am stuck.

[marky]

I'm manchester and ive no probs






OOPS i'm BT now

[AndrewJ]

Originally Posted by marky

I'm manchester and ive no probs






OOPS i'm BT now

Git

I love my ntl 10mb family pack tv and the phone.

All working perfectly fine yip no problems at all, not a single issue.


/smug ******* mode off

[Florence]

Perhaps someone could explain the logs on the modem as some I have never had before then it might be easier to spot the problem when it loses sync next time.

Time Not Established Time Not Established 1 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Time Not Established Time Not Established 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Time Not Established Time Not Established 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Sat Jun 17 09:34:37 2006 Sat Jun 17 09:34:37 2006 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un...

All since Sat when the internet was down from around 10.33am

[James Henry]

Nothing to say really, it's checking for a DOCSIS downstream it can lock on to, finding one then transmitting a request to el uBR and not receiving a ranging response back to help it fine tune upstream transmit power. All this does is point to an issue on the upstream path. The uBR doesn't respond with a ranging response as it didn't see the ranging request.

Originally Posted by James Henry

Nothing to say really, it's checking for a DOCSIS downstream it can lock on to, finding one then transmitting a request to el uBR and not receiving a ranging response back to help it fine tune upstream transmit power. All this does is point to an issue on the upstream path. The uBR doesn't respond with a ranging response as it didn't see the ranging request.

What he said.


I will be in the office for your area tomorrow and will ask the engineers for your area if they are seeing any complaints over and above what they normally get on a day to day basis. If they are seeing a lot will get them to have a look for you.

[Florence]

Originally Posted by unlimited

What he said.


I will be in the office for your area tomorrow and will ask the engineers for your area if they are seeing any complaints over and above what they normally get on a day to day basis. If they are seeing a lot will get them to have a look for you.

Thank you it would seem on Sat everything went downhill after this.

Sat Jun 17 09:34:37 2006 Sat Jun 17 09:34:37 2006 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un...

So I woud say someone requested the modem to respond with some info and it went down hill fast afterwards. There is no way to find out what the other info was after the But no Un... what was requested

Originally Posted by Florence

Thank you it would seem on Sat everything went downhill after this.

So I woud say someone requested the modem to respond with some info and it went down hill fast afterwards. There is no way to find out what the other info was after the But no Un... what was requested

Unicast might be what would have been next. I do not think anyone would have requested or would have been talking to your modem. All the information in the logs is created by normal everyday traffic to and from the various parts of NTL's network and equipment.

[James Henry]

Originally Posted by Florence

Thank you it would seem on Sat everything went downhill after this.



So I woud say someone requested the modem to respond with some info and it went down hill fast afterwards. There is no way to find out what the other info was after the But no Un... what was requested

No-one requested that the modem do anything, this is an automatic process during modem sync.

http://www.ct-magazine.com/archives/...gistration.htm

For more information on the DOCSIS modem registration process.

Also to finish off the other bit .....Unicast Maintenance opportunities received. Modem broadcast but did not receive a response back from the uBR providing a timeslot for it to transmit a unicast message.

Again to understand this bit better you need to look at time division multiplexing. I'm not convinced you've the uber techy skillz to really read and absorb all that gack so it'll all look like a foreign language. Can't really say I blame you it's all Greek to me.

I'd still say upstream fault is the most likely, simply because a downstream HFC fault would have harmed people's TV, and the errors suggest an upstream issue.

[Florence]

Thanks I will read up a little more.