NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
How to confirm C6300 hardware issues?
How can I confirm if my C6300 AC1750 is having hardware problems? I started having intermittent internet connection issues around May, approximately two years after I purchased the device. Conne...
Unexpected intermittent power reset issue confirmed as a hardware problem. Just purchased a new modem router and no further intermittent internet troubles. T3/T4 timeout issues were a byproduct of modem loss of power and reboot, coincidental with power reset events. New modem has had no T3/T4 timeouts in the event log.
cybrmstrwhat ended up being the root cause of your issue?
https://community.netgear.com/t5/Cable-Modems-Routers/C6300-Randomly-Rebooting/td-p/1306871
What you describe sounds very similar to what's happening to my C6300.
It's a bit of chicken or egg, does the T3 time-out cause the unit to power cycle, or does the power cycle of the unit then cause the T3 time-out? I can't believe that a network communications timeout would cause the unit to power cycle reboot.....
| Time | Priority | Description |
| Oct 13 2020 01:02:02 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Oct 13 2020 00:35:44 | Error (4) | Map Request Retry Timeout |
| Oct 13 2020 00:34:02 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Oct 12 2020 18:25:52 | Error (4) | Map Request Retry Timeout |
| Oct 12 2020 15:18:50 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Oct 12 2020 14:48:23 | Error (4) | Map Request Retry Timeout |
| Oct 12 2020 14:40:48 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Oct 12 2020 14:37:52 | Error (4) | Map Request Retry Timeout |
| Oct 12 2020 14:35:39 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Oct 12 2020 14:30:29 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Oct 12 2020 14:18:10 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Oct 12 2020 06:58:13 | Error (4) | Map Request Retry Timeout |
| Oct 12 2020 06:51:28 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Oct 12 2020 05:24:40 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Oct 11 2020 22:38:14 | Error (4) | Map Request Retry Timeout |
| Oct 11 2020 22:36:16 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Oct 11 2020 22:35:52 | Critical (3) | No Ranging Response received - T3 time-out |
| Oct 11 2020 22:35:21 | Critical (3) | REG RSP not received |
| Oct 11 2020 22:35:21 | Error (4) | T6 Timeout and retries exceeded |
| Oct 11 2020 22:35:10 | Critical (3) | No Ranging Response received - T3 time-out |
| Oct 11 2020 22:35:09 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Oct 11 2020 22:13:43 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Oct 11 2020 19:05:24 | Error (4) | Map Request Retry Timeout |
| Oct 11 2020 19:03:22 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Oct 11 2020 19:00:46 | Error (4) | Map Request Retry Timeout |
| Oct 11 2020 18:58:55 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Oct 11 2020 18:56:13 | Error (4) | Map Request Retry Timeout |
| Oct 11 2020 18:54:27 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
So here’s what the end result of that issue was. T3/T4 time-outs is a cause of an issue on the line but the additional issue was the problem with the modem resetting. Eventually a few days after posting these logs back in 2017 the modem wouldn’t even power up and died. The modem last be about 7 ish years. For about a year I rented the Comcast modem and then about a year ago i repurchased the same C6300 again for about $50 less then the 1st one. About 2 weeks ago I was having drops in internet. Same T3/T4 time-outs again and I had Comcast come out and check the line and it was a line issue that had to be resolved with an additional maint ticket that the tech had to put me in for. Hope that helps you.
Thanks cybrmstr, so your random router power reset issue was a hardware issue. My C6300 was about two years old when this first started happening. If I buy another cable modem router I'll buy one with a two year warranty instead of one year.
The T3/T4 timeout were separate, unrelated issues? So after you bought a new C6300 when those occurred the modem didn't power reset?
ISP tech just came out and confirmed signal levels were fine, even re-ran the drop into the house.
- Let me be clear. T3/T4 timeouts are a line issue or a connection to the modem inside your house. My problem with my modem back in 2017 was a problem with the modem resetting. If the modem wasn’t doing that then the t3/t4 timeouts is a line problem. Whether it’s inside or outside not sure but normally this is a an outside concern. When I purchased the 2nd c6300 there were 0 problems for the past 2 years until a couple of weeks ago.
Unexpected intermittent power reset issue confirmed as a hardware problem. Just purchased a new modem router and no further intermittent internet troubles. T3/T4 timeout issues were a byproduct of modem loss of power and reboot, coincidental with power reset events. New modem has had no T3/T4 timeouts in the event log.