brendanheading
12-03-2007, 15:31
All,
I've just been on to NTL for a problem I've been having for many months. I'm connecting through by wireles Linksys router. On annoyingly frequent occasions, the connection to the internet dies. When I powercycle the cable modem the problem goes away, and then it dies again - sometimes it takes only five minutes to die, sometimes several hours. When it dies the cable modem's lights all look fine. The CM does not lose sync. During this time I can ping the router and access it's management page. But I cannot ping from the router out to the internet.
I'm defining a "dead connection" here as an inability to ping any normal websites. DNS lookups even fail during a "death". To spot the connection dying I'm doing ping -t www.google.com from my command prompt.
I checked the event logs of the cable modem. Here's what it currently has:
==============================
Time Not Established Time Not Established 3 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response. Sat Mar 10 18:44:17 2007 Sat Mar 10 18:44:17 2007 1 Critical(3) 73000200 REG RSP not received Time Not Established Time Not Established 3 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response. Time Not Established Time Not Established 1 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ... Time Not Established Time Not Established 2 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response. Sun Feb 25 17:56:32 2007 Sun Feb 25 17:56:32 2007 1 Critical(3) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC f... Sun Feb 25 16:44:44 2007 Sun Feb 25 16:44:44 2007 19 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ... Thu Feb 22 21:18:58 2007 Thu Feb 22 21:18:58 2007 65 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ... Sun Feb 18 15:11:52 2007 Sun Feb 18 15:11:52 2007 8 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ... Time Not Established Time Not Established 3 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response. Sat Feb 03 15:32:56 2007 Sat Feb 03 15:32:56 2007 1 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...================================
When I first started seeing this, I did some googling, and people are basically saying that this indicates a dead modem. However, I've just been on the phone to NTL support twice, and they say they are running diagnostics and all is fine. The first time I rang the connection was working. Despite my insistences, they wibbled on about spyware or viruses. I mentioned the above problem and they seemed to spark up, and said it might be a dud modem; they asked me to call back the next time the line went down. I did that - they ran their diagnostics again and found no problems. According to them the connection was up - even though I could not ping anything. I asked them to look at the CM's diagnostic logs, showing the above DHCP messages, but they did not seem to know what I was talking about, just repeating that their own diagnostics had passed fine.
Has anyone had any success recently getting NTL to accept that there is a problem ? If there are any NTL techs reading, I'd be very grateful if you could check against my MAC : 00:0e:9b:e4:5f:dc. I'm tearing my hair out with this, and I'm in the mood to cancel my connection and switch to ADSL if I can't find a way to sort this out.
---------- Post added at 15:31 ---------- Previous post was at 15:23 ----------
I've just looked at the sticky on power levels. According to that, my power levels are at the edge of the tolerated values :
Upstream transmit Power Level : 56.5 dBmV
Downstream Receive Power Level : 7.3 dBmV
Downstream SNR : 40.2 dB
Comments anyone ?
I've just been on to NTL for a problem I've been having for many months. I'm connecting through by wireles Linksys router. On annoyingly frequent occasions, the connection to the internet dies. When I powercycle the cable modem the problem goes away, and then it dies again - sometimes it takes only five minutes to die, sometimes several hours. When it dies the cable modem's lights all look fine. The CM does not lose sync. During this time I can ping the router and access it's management page. But I cannot ping from the router out to the internet.
I'm defining a "dead connection" here as an inability to ping any normal websites. DNS lookups even fail during a "death". To spot the connection dying I'm doing ping -t www.google.com from my command prompt.
I checked the event logs of the cable modem. Here's what it currently has:
==============================
Time Not Established Time Not Established 3 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response. Sat Mar 10 18:44:17 2007 Sat Mar 10 18:44:17 2007 1 Critical(3) 73000200 REG RSP not received Time Not Established Time Not Established 3 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response. Time Not Established Time Not Established 1 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ... Time Not Established Time Not Established 2 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response. Sun Feb 25 17:56:32 2007 Sun Feb 25 17:56:32 2007 1 Critical(3) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC f... Sun Feb 25 16:44:44 2007 Sun Feb 25 16:44:44 2007 19 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ... Thu Feb 22 21:18:58 2007 Thu Feb 22 21:18:58 2007 65 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ... Sun Feb 18 15:11:52 2007 Sun Feb 18 15:11:52 2007 8 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ... Time Not Established Time Not Established 3 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response. Sat Feb 03 15:32:56 2007 Sat Feb 03 15:32:56 2007 1 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...================================
When I first started seeing this, I did some googling, and people are basically saying that this indicates a dead modem. However, I've just been on the phone to NTL support twice, and they say they are running diagnostics and all is fine. The first time I rang the connection was working. Despite my insistences, they wibbled on about spyware or viruses. I mentioned the above problem and they seemed to spark up, and said it might be a dud modem; they asked me to call back the next time the line went down. I did that - they ran their diagnostics again and found no problems. According to them the connection was up - even though I could not ping anything. I asked them to look at the CM's diagnostic logs, showing the above DHCP messages, but they did not seem to know what I was talking about, just repeating that their own diagnostics had passed fine.
Has anyone had any success recently getting NTL to accept that there is a problem ? If there are any NTL techs reading, I'd be very grateful if you could check against my MAC : 00:0e:9b:e4:5f:dc. I'm tearing my hair out with this, and I'm in the mood to cancel my connection and switch to ADSL if I can't find a way to sort this out.
---------- Post added at 15:31 ---------- Previous post was at 15:23 ----------
I've just looked at the sticky on power levels. According to that, my power levels are at the edge of the tolerated values :
Upstream transmit Power Level : 56.5 dBmV
Downstream Receive Power Level : 7.3 dBmV
Downstream SNR : 40.2 dB
Comments anyone ?