Cable Forum - View Single Post - Question for NTL - packetloss and disconnection problem in Luton area

Heedyheed · 07-11-2006, 19:26

Glad to hear you don't have similar problems. I'm not actually in Luton, but I connect to the 'Luton' infrastructure as far as NTL is concerned; for instance the third hop in a tracert gets a response from lutn-t2core-a-ge-wan61-inet.ntl.com.

I'd have been surprised if the whole 'Luton area' had been similarly affected with packet loss and disconnections - NTL would have been swamped in customer complaints. The problem I had is obviously something that's much more local - maybe just affecting users who connect to the same local cabinet as I do. Or maybe it was only affecting me all along - although it's still working fine at the moment and I've made absolutely NO changes to my PC/modem, etc. Looking at the pattern of packet loss v time, it looks like the problem was dependent on network load - nothing to do with traffic generated by my PC. For that reason I believe it was an NTL problem.

That's why I was hoping for a response from one of the NTL engineering employees who monitor this forum. It would be useful to know to what level they are able to monitor the network for performance bottlenecks and faults. It would also be interesting to hear why NTL are so coy about admitting when they have a problem.

Anyone from NTL care to respond to the points raised in my original post?

Mike

07-11-2006, 19:26	#3
Heedyheed Inactive Join Date: Jun 2006 Location: Bedfordshire Posts: 63	Re: Question for NTL - packetloss and disconnection problem in Luton area Glad to hear you don't have similar problems. I'm not actually in Luton, but I connect to the 'Luton' infrastructure as far as NTL is concerned; for instance the third hop in a tracert gets a response from lutn-t2core-a-ge-wan61-inet.ntl.com. I'd have been surprised if the whole 'Luton area' had been similarly affected with packet loss and disconnections - NTL would have been swamped in customer complaints. The problem I had is obviously something that's much more local - maybe just affecting users who connect to the same local cabinet as I do. Or maybe it was only affecting me all along - although it's still working fine at the moment and I've made absolutely NO changes to my PC/modem, etc. Looking at the pattern of packet loss v time, it looks like the problem was dependent on network load - nothing to do with traffic generated by my PC. For that reason I believe it was an NTL problem. That's why I was hoping for a response from one of the NTL engineering employees who monitor this forum. It would be useful to know to what level they are able to monitor the network for performance bottlenecks and faults. It would also be interesting to hear why NTL are so coy about admitting when they have a problem. Anyone from NTL care to respond to the points raised in my original post? Mike