US Cable Support > Road Runner > [TWC] NEO, Dropping connection at night

[TWC] NEO, Dropping connection at night

Can you show us some signal levels and trace routes so we can try to help you diagnose a problem?

reply to xJumpManx
This happens to me all the time, and for me it has to do with temperatures. It has taken me at least 4 tech's to find the problem each time and it happens every fall and summer. In the summer when it gets hot, the SNR would fall and the internet stop working, of course when the techs show up it would be fine. Then finally they would see it happen and adjust something on the line and it would be ok until the next season change and it would happen when it got too cold, rinse and repeat. We had a couple of warm days the other day and my internet quit working until it got cold again, but I will wait for more warmer days before I call to help minimize the amount of techs that show up when its working.

This is not a rant against TWC, when the service is working its great, just sucks that I have to go through a few weeks of down time 2 times a year.

Mine has been dropping all the time at night, intermittently and then coming back on, same IP address and everything. SNR and everything stays constant. I always call TWC and they can't ever find out what is wrong with it. And I love TWC when it's working, just not all the time.

reply to xJumpManx
I've noticed a similar issue in NWO, the last couple mornings when I've gotten up, I've had to reset my modem in order to get any internet connectivity. The first morning, I had a fast blink on the cable light on the modem. This morning the light was solid, but again I couldn't get any internet access until I reset the modem.

I've also noticed in the evenings around 10 pm or so some issues. Watching Hulu, it would keep pausing like there wasn't enough bandwidth. So I went to my router config (DD-WRT) and was watching some of the network traffic it seem to be running along fine, then all of the sudden the bandwidth would just completely drop off. I don't know if it's a RR issue or Hulu, but i did find it odd as it doesn't normally happen, especially as consistently as it was the last couple nights.

I have been on the phone with them about a similar problem for two months now in NYC.
Early on someone on the phone said they saw a "frequency" problem and sent out a tech. He replaced the modem, which did actually get faster speeds, (was getting 7-10Mbps, but now 12-17 is more common) but it still hangs. Especially late at night.
They have tried to upsell me to a faster service, but even Pandora (which uses .15 Mbps) will quit sometimes and say it can't find a signal.
But when I call right away, they say everything is fine and has been for the past 5 days...

reply to xJumpManx
Same, NEO-TWC, has been dropping me all day for the past ~4days.

Before that it was a solid week, and the 'in-house' tech came out and replaced the connector to the pole (severely corroded), replaced the grounding line. In the end the signal was still too high (~53dBmV upstream); Motorola's cut of is about 54dBmV [upstream].

Called in the Field Techs to look at the pole-to-pole connection, while they were working the Network Tech came out saying they had an issue with their fiber node.

After all that the connection was perfect with a new Motorola SBG6580 replacing the SB5101 that TWC had installed years ago.

But with in the last 4days the same issues have come up, with soem new ones now that I got DOCSIS 3.0 compliance

Brief log (as in what's happened today [Feb. 18th, 2012]:

 Sat Feb 18 06:59:58 2012   Error (4)  Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 06:59:58 2012   Error (4)  Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Time Not Established  Warning (5)  DHCP WARNING - Non-critical field invalid in response ;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.0;CM-VER=3.0; 
 Sat Feb 18 06:59:10 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 06:58:37 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Time Not Established  Critical (3)  No Ranging Response received - T3 time-out  
 Sat Feb 18 06:26:51 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 06:26:18 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 05:14:29 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 05:13:56 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 05:10:39 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 05:10:07 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 04:42:40 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 04:42:07 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Time Not Established  Critical (3)  No Ranging Response received - T3 time-out  
 Sat Feb 18 04:06:12 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 04:05:40 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Time Not Established  Critical (3)  No Ranging Response received - T3 time-out  
 Sat Feb 18 03:55:37 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 03:55:04 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 03:38:54 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 03:38:22 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Time Not Established  Critical (3)  No Ranging Response received - T3 time-out  
 Sat Feb 18 03:00:46 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 03:00:14 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 02:50:51 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 02:50:19 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 02:36:25 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 02:35:52 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 01:50:11 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 01:49:39 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 01:32:00 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 01:31:27 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 01:25:23 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 01:24:50 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Time Not Established  Critical (3)  No Ranging Response received - T3 time-out  
 Sat Feb 18 01:17:07 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 01:16:34 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 01:03:52 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 01:03:20 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Time Not Established  Critical (3)  No Ranging Response received - T3 time-out  
 Sat Feb 18 00:37:10 2012   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0; 
 Sat Feb 18 00:36:38 2012   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e4:83:99:6b:84:43;CMTS-MAC=00:24:14:60:af:7b;CM-QOS=1.1;CM-VER=3.0;