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.
Have a friend, family member or neighbor you can take the modem to and test at a different location?
Thanks, but since the ISP needs the MAC address of the device it's a bit difficult to just try it at another location, with same ISP
I've noticed that each time the internet drops out that all the LED lights go out on the front panel of the C6300. Then, they gradually come back on, and then the spotty internet connection persists.
Around the time of the device reset, the Event Log has this entry:
No Ranging Response received - T3 time-out Doesn't seem like a T3 timeout should cause the device to spontaneously reset.... In my experience with embedded controls, spontaneous resets are caused by software bugs, or looming hardware failure. Something in the line, or signal, shouldn't cause a downstream device reset.
If there was a bug in the firmware, I'm sure lots of people would be affected and Netgear would issue an update. So it's probably not a bug. Based on my experience I'm tending to think sudden reset of the C6300 is caused by either power supply problem, or modem/router electronics problem.
Signals seem to look good, when the internet is working. And when the internet isn't working, the router also doesn't seem to be working, takes a bit to reboot and all lights to come back online with connection to 192.168.0.1 restored. At which point the signals look fine again.
Rnaging issues are mostly a ISP line signal issue.
Can try to find a differnt power supply. Get a different modem and see if this different modem does the same thing or not.
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
