NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Mattst
Jan 11, 2017Aspirant
N450 CG3000Dv2 dropping wired and wireless connection repeatedly
A few days ago I started losing my connection from my N450 CG3000Dv2 modem/router. This occurs on both a hard-wired (gigabit) connection to the router and on other devices connected wirelessly. I contacted Comcast support the first time this happened and they sent refresh signals to the router (which hasn't helped). On the next call to Comcast, they said everything looked good on their end and that I'd need to contact Netgear.
Is there any diagnostic I can run locally in order to determine if the router itself is failing? It's not quite 3 years old, but I've had routers before that dropped connections like this and I'm not sure if they lasted more than 3 years either.
thanks,
Matt
7 Replies
- DarrenMSr. NETGEAR Moderator
Hello Mattst
You could post the logs when it happens you can find them in the settings under Maintenance and then event log. This may tell us what is happening.
DarrenM
- MattstAspirant
Thanks. Here's the log:
Time Priority Description
2017-01-12, 01:33:52.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
2017-01-12, 01:33:23.0 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
2017-01-12, 01:30:34.0 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
2017-01-12, 01:25:45.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.1;CM-VER=3.0;
2017-01-12, 01:23:42.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.1;CM-VER=3.0;
2017-01-12, 01:21:55.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.1;CM-VER=3.0;
2017-01-12, 01:21:49.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=my:ff:ff:ff:ff:my;CMTS-MAC=00:01:02:02:03:03;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Notice (6) WiFi Interface [wl0] set to Channel 3 (Side-Band Channel:N/A) - Reason:INIT- DarrenMSr. NETGEAR Moderator
Hello Mattst
Those T3 timeouts typically mean its a signal issue on your lines so you might need your ISP tech to come out and check everything out. I linked a article on what the timeouts mean below.
https://volpefirm.com/docsis_timout_descriptions/
DarrenM