NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
TWC
3 TopicsC3700 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;Solved5.2KViews0likes7Commentsdisable ipv6 CM 500
TWC is telling me that they don't support IPv6 from my cable modem. I don't see an option to disable it in the GUI. Here is what I see: Startup Procedure Procedure Status Comment Acquire Downstream Channel 633000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode IPv6 Only ipv6Only(1) Hardware Version C312T00-01 Firmware Version V1.01.04 Ideas?3.9KViews0likes3CommentsTWC in NYC and Netgear C3000 Cable Modem - No One is Helping
Hello Everyone, Since last week my internet is not working (Nov 3rd). Somehow my personal (not TWS) Netgear C3000 Firmware is "upgraded" to V2.02.26. Up until that it was working very good! Apparently TWC did some changes on their side, i have had quite a few calls with them since then, and they say they are working with Netgear to fix the issue. Meanwhile since it is my personal (1+ year old netgear router/modem) they have asked me to contact Netgear to downgrade the firmware (not sure who upgraded it in first place!!!). Netgear is requesting to renew the warranty for a price that is more expensive then buying a brand new router/modem from them (or from another company) and TWC is not willing to help. From what i read over the forums there is no way to manually downgrade the firmware to V1.01.11 that TWC is requesting. They don't have any ETA for a support to the issue they caused, I guess the only options i have are: 1. Disconnect from TWC 2. Buy a new modem/router (probably not netgear!) any thoughts?4.3KViews0likes8Comments