NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
khumbert45
Mar 23, 2017Aspirant
C3700-100NAS connection drops multiple times a day
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 co...
khumbert45
Mar 24, 2017Aspirant
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
Mar 24, 2017Sr. NETGEAR Moderator
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