C3700-100NAS connection drops multiple times a day

[khumbert45]

I was tired of paying a monthly fee to rent my modem from my ISP so I purchased the C3700 modem/router combo late last year. I installed it and have been using it but have had many issues with the connection dropping multiple times a day, sometimes 2 or 3 times in an hour and it is very frustrating.

I have a computer (Windows 10) hooked up to the modem/router through a wired connection and another through wifi. When it drops connection, it drops for both computers and I either have to wait for the connection to come back on it's own or reboot the router. My cell phones always have issues with the wifi actually working for them as well. Even when the connection is up, our phones don't seem to connect properly. it shows connected but sometimes things run very slow or e-mails won't come through. If I switch to 4G sometimes, I will suddenly have a bunch of notifications for new e-mails and messages which didn't come through when connected to wifi.

I have gone through the troubleshooting process. I called my ISP (Spectrum) multiple times and they confirmed the connection is not dropping on their end. They suggested I try wireless channels 1, 6 and 11, which is what they use. I tried 6 and 11 but can't even select 1. I have tried other channels than 1, 6 or 11 as well and got no better results.

I don't have any splitters in the line. I have the current firmware (V2.02.08). I have power cycled my network more times than i care to say in this discussion.

I am outside of my 90 day window of free support (which is complete BULLCRAP, by the way...) and refuse to pay another $50 for "support" of a product that from what I can tell, is pure garbage. I have seen many others with these same issues on discussion boards but I haven't really heard of anyone having their problems fixed, so this is likely a pointless discussion...

If some sort of resolution isn't made, I will just have to buy another product and it will not be Netgear...

[mikepiet]

I have the exact same problem. So far, Cox cable says "the connection\line is strong and without issue. Your problem is you cable modem."

GREAT! Sadly Netgear has no fix and I am pretty much sure they will not release a new firmware for it.

We have a $100 paperweight friends. I knew I was making the wrong decision when buying a Netgear product.

[khumbert45]

Here is my event log. Hopefully this gets some sort of response:

Time	Priority	Description
2017-3-23, 21:11:10	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:11:14	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:11:42	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:12:02	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:12:15	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:12:26	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:12:47	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:12:49	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:13:20	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:13:37	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:13:52	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:14:01	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:14:25	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:14:25	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:14:57	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:15:13	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:15:30	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:15:37	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:16:02	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:16:25	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:16:35	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:16:49	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:17:07	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:17:13	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:17:40	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:18:01	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:18:12	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:18:25	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:18:45	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:18:49	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:19:17	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:19:37	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:19:50	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:20:01	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:20:22	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:20:27	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:20:53	Warning (5)	Dynamic Range Window violation
2017-3-23, 21:26:04	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;
2017-3-23, 21:28:56	Warning (5)	Dynamic Range Window violation
2017-3-23, 22:18:31	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:79:5b:d8;CMTS-MAC=00:01:5c:9d:e0:4a;CM-QOS=1.1;CM-VER=3.0;

[DarrenM]

Hello Khumbert45

You have alot of T4 timeouts this is typically a line issue and I would suggest having your ISP come out and check the lines.

DarrenM