NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
C3700 randomly resets daily, often multiple times (error log included)
Hi there. N00b in the house. So, pretty much since I've had my N600 C3700 (October, 2015) I've experienced random daily resets/dropouts. I've had TWC come out a couple of times and they always check the line, report that all's well, and leave. I don't trust that they're correct, but I don't know how to interpret error logs either, so I've got no ground to stand on. I work from home and connect wirelessly from my laptop, plus have six SONOS components connected (typically only 1-3 streaming music at any time). Usually try to turn my iPhone wifi off at home, but not always. Same for an Android tablet in the house.
Anyhow, the resets most often happen 1 - 4 times a day, and occasionally terrorize me constantly throughout my workday. I've power cycled many many times, powering the router down, disabling device wifi, and unplugging all the SONOS components, then powering the router up and adding one connection at a time. I honestly can't tell if this accomplishes anything, as the resets/dropouts usually resolve themselves in a few minutes. Every so often, they don't, and in those cases, cycling does get the job done. I haven't tried a factory reset. Firmware is up to date and I don't see an option in the Genie to roll back or update anyway.
Here's today's event log*. Can someone let me know if the info here contains any hints as to the root problem? Thank you so so much.
*If it appears as a mess, I can try to repost. I copied it in as a table, but the system removed certain "invalid HTML." Ugh.
2017-6-12, 10:40:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.0;CM-VER=3.0;
2017-6-12, 10:40:30 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.0;CM-VER=3.0;
2017-6-12, 10:40:33 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2017-6-12, 10:40:45 Warning (5) ToD request sent - No Response received;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.0;CM-VER=3.0;
2017-6-12, 10:40:46 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 10:40:46 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 03:10:13 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 03:11:04 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 03:11:27 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.0;CM-VER=3.0;
2017-6-12, 03:11:39 Notice (6) Honoring MDD; IP provisioning mode = IPv4
2017-6-12, 11:11:42 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 11:11:42 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 11:11:42 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 11:11:52 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.0;CM-VER=3.0;
2017-6-12, 11:11:59 Notice (6) Honoring MDD; IP provisioning mode = IPv4
2017-6-12, 11:12:01 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 11:12:01 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 11:12:01 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 11:12:11 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.0;CM-VER=3.0;
2017-6-12, 11:12:14 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2017-6-12, 11:12:27 Warning (5) ToD request sent - No Response received;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.0;CM-VER=3.0;
2017-6-12, 11:12:28 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 11:12:28 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 06:41:55 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 06:42:35 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 06:43:03 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.0;CM-VER=3.0;
2017-6-12, 06:43:51 Notice (6) Honoring MDD; IP provisioning mode = IPv4
2017-6-12, 14:43:55 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 14:43:55 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 14:43:55 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 14:44:03 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.0;CM-VER=3.0;
2017-6-12, 14:44:11 Notice (6) Honoring MDD; IP provisioning mode = IPv4
2017-6-12, 14:44:15 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 14:44:15 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 14:44:15 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 14:44:25 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.0;CM-VER=3.0;
2017-6-12, 14:44:27 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2017-6-12, 14:44:39 Warning (5) ToD request sent - No Response received;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.0;CM-VER=3.0;
2017-6-12, 14:44:40 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
2017-6-12, 14:44:40 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f9:01:00;CMTS-MAC=00:01:5c:68:6e:52;CM-QOS=1.1;CM-VER=3.0;
Hello DailyDropout
I do see some T3 and T4 timeouts so this could be a line issue might be down the line from your house have they checked those lines or just the one coming into your home? Here is what those mean.
https://volpefirm.com/docsis_timout_descriptions/
DarrenM
7 Replies
Hello DailyDropout
I do see some T3 and T4 timeouts so this could be a line issue might be down the line from your house have they checked those lines or just the one coming into your home? Here is what those mean.
https://volpefirm.com/docsis_timout_descriptions/
DarrenM
Thanks DarrenM. Last time they just seemed to check the line in my apartment unit. I should say I'm in a complex with 20-odd units. It's been hard to get them to do more than their bare minimum, but knowing this is a possibility I may feel more confident in pushing.
I've been wondering if I should invest in a UPS. Is there any sign that buying one would be helpful? Or can one even tell from this?
Okay, one more thing. My previous log was the "event log". I went to the "logs" log after experiencing this dropout again moments ago, and I found this repreating many many times:
[DoS attack: Ping Of Death] from 96.3.123.0, port 0 1 Thu Jun 15 08:56:39 2017 168.53.251.2:0 96.3.123.0:0
[DoS attack: Teardrop or derivative] from 96.3.123.0, port 0 3 Thu Jun 15 08:56:38 2017 168.53.251.2:0 96.3.123.0:0
[DoS attack: Illegal Fragments] from 96.3.123.0, port 0 1 Thu Jun 15 08:53:50 2017 168.53.251.2:0 96.3.123.0:0The "from" IP seems to belong to an internet/cable provider in Sioux Falls, SD. I'm in Los Angeles.
The "target IP appears to the Texas Department of Information Resources. ?!?! What is happening?
Thanks to your expertise I was able to call my provider and sound like I knew what I was talking about. They agreed that the trouble seemed to be coming from down the line and they came out, replaced a couple of connectors, cleaned up the wall port (which the landlord had painted over) and ouila! The internet has been working consistently ever since. Thank you so much for your advice and knowledge.