I purchased this modem back in April 2016 for use at my house with TWC. The modem has worked well for about 2 months but then one afternoon out of the blue it dropped connection for a minute or two. This continued to happen daily at about the same time consistently getting more frequent and random over time. I have adjusted the MTU setting and it doesn't seem to have changed anything. I have called TWC on multiple occasions but of course they have no clue what's wrong and have instructed me to investigate the modem/router for issues. However after reading these boards for support and elsewhere I am starting to question TWC. Does anyone know what this event log is telling me? TimePriorityDescriptionJul 01 2016 03:39:04Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jul 01 2016 03:38:13Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outJul 01 2016 02:49:45Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jul 01 2016 02:48:54Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outJul 01 2016 02:22:16Critical (3)No Ranging Response received - T3 time-outJul 01 2016 02:07:45Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jul 01 2016 00:00:21Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outJun 30 2016 23:59:51Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhaustedJun 30 2016 23:59:51Critical (3)Ranging Request Retries exhaustedJun 30 2016 23:59:35Critical (3)No Ranging Response received - T3 time-outJun 30 2016 22:42:24Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jun 30 2016 22:41:40Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outJun 30 2016 22:21:07Critical (3)No Ranging Response received - T3 time-outJun 30 2016 22:17:17Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jun 30 2016 22:16:25Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outJun 30 2016 22:15:02Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jun 30 2016 22:14:44Critical (3)No Ranging Response received - T3 time-outJun 30 2016 22:14:24Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jun 30 2016 22:14:13Critical (3)No Ranging Response received - T3 time-outJun 30 2016 22:13:30Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outJun 30 2016 21:43:31Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jun 30 2016 21:42:40Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outJun 30 2016 20:50:51Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jun 30 2016 20:50:22Warning (5)TCS Partial ServiceJun 30 2016 20:50:17Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-outJun 30 2016 20:50:16Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jun 30 2016 20:49:24Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outJun 30 2016 20:48:14Notice (6)Received REG-RSP while in REG-HOLD1 stateJun 30 2016 20:47:11Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jun 30 2016 20:46:40Warning (5)TCS Partial ServiceJun 30 2016 20:46:37Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-outJun 30 2016 20:46:37Critical (3)No Ranging Response received - T3 time-outJun 30 2016 20:46:36Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-outJun 30 2016 20:46:36Critical (3)No Ranging Response received - T3 time-outJun 30 2016 20:46:35Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-outJun 30 2016 20:46:34Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jun 30 2016 20:45:42Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outJun 30 2016 20:44:12Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jun 30 2016 20:43:03Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outJun 30 2016 20:42:39Critical (3)No Ranging Response received - T3 time-out Help Center Show/Hide Help Center

Hello kcjames You are correct T3 and T4 timeouts are issues with your cable signal and TWC will have to come fix the issues I linked a article about these time outs. http://volpefirm.com/docsis_timout_descriptions/ DarrenM

kcjames

Aspirant

Jul 01, 2016

Solved

C6300 randomly loses connection with ISP T3/T4 Timeout

I purchased this modem back in April 2016 for use at my house with TWC. The modem has worked well for about 2 months but then one afternoon out of the blue it dropped connection for a minute or two. This continued to happen daily at about the same time consistently getting more frequent and random over time. I have adjusted the MTU setting and it doesn't seem to have changed anything. I have called TWC on multiple occasions but of course they have no clue what's wrong and have instructed me to investigate the modem/router for issues. However after reading these boards for support and elsewhere I am starting to question TWC. Does anyone know what this event log is telling me?

Time	Priority	Description
Jul 01 2016 03:39:04	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jul 01 2016 03:38:13	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jul 01 2016 02:49:45	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jul 01 2016 02:48:54	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jul 01 2016 02:22:16	Critical (3)	No Ranging Response received - T3 time-out
Jul 01 2016 02:07:45	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jul 01 2016 00:00:21	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jun 30 2016 23:59:51	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted
Jun 30 2016 23:59:51	Critical (3)	Ranging Request Retries exhausted
Jun 30 2016 23:59:35	Critical (3)	No Ranging Response received - T3 time-out
Jun 30 2016 22:42:24	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 30 2016 22:41:40	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jun 30 2016 22:21:07	Critical (3)	No Ranging Response received - T3 time-out
Jun 30 2016 22:17:17	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 30 2016 22:16:25	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jun 30 2016 22:15:02	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 30 2016 22:14:44	Critical (3)	No Ranging Response received - T3 time-out
Jun 30 2016 22:14:24	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 30 2016 22:14:13	Critical (3)	No Ranging Response received - T3 time-out
Jun 30 2016 22:13:30	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jun 30 2016 21:43:31	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 30 2016 21:42:40	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jun 30 2016 20:50:51	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 30 2016 20:50:22	Warning (5)	TCS Partial Service
Jun 30 2016 20:50:17	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Jun 30 2016 20:50:16	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 30 2016 20:49:24	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jun 30 2016 20:48:14	Notice (6)	Received REG-RSP while in REG-HOLD1 state
Jun 30 2016 20:47:11	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 30 2016 20:46:40	Warning (5)	TCS Partial Service
Jun 30 2016 20:46:37	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Jun 30 2016 20:46:37	Critical (3)	No Ranging Response received - T3 time-out
Jun 30 2016 20:46:36	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Jun 30 2016 20:46:36	Critical (3)	No Ranging Response received - T3 time-out
Jun 30 2016 20:46:35	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Jun 30 2016 20:46:34	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 30 2016 20:45:42	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jun 30 2016 20:44:12	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jun 30 2016 20:43:03	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jun 30 2016 20:42:39	Critical (3)	No Ranging Response received - T3 time-out

Help Center Show/Hide Help Center

Troubleshooting

Forum Discussion

C6300 randomly loses connection with ISP T3/T4 Timeout

3 Replies