NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
KenSimmons
Jun 13, 2018Aspirant
C6300 dropping Wifi connection
I haven't found any solutions on the forum and this seems to have been a problem for years now. I have the latest firmware from suddenlink, and everything seems to be in check. My C6300 will drop i...
KenSimmons
Jun 13, 2018Aspirant
I am only using wifi connections with my desktop and my phone. The desktop is only 2.4ghz capable but my i-Phone loses 5g as well, so yes, I am losing both bands.
The disconnects seem to be infrequent - at times the connection will only last a few seconds before a restart, but as of this post I can last up to 20-30 minutes. Another factor that seems to trigger a failure to broadcast is connecting to certain high traffic sites/games.
I can send a list of system specifications but for now here are the ip v4 ping test, ip v6 ping test and event log from the router page.
PING 192.168.0.1 (192.168.0.1): 64 data bytes
72 bytes from 192.168.0.1: seq=0 ttl=64 time=0.000 ms
72 bytes from 192.168.0.1: seq=1 ttl=64 time=0.000 ms
72 bytes from 192.168.0.1: seq=2 ttl=64 time=0.000 ms
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.000/0.000/0.000 ms
PING 2001:192:168:0::1 (2001:192:168::1): 64 data bytes
ping6: sendto: Network is unreachable
Jun 13 2018 08:35:36 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
Time Not Established | Error (4) | Primary lease failed, IPv4 fallback initiated |
Time Not Established | Critical (3) | DHCP failed - RS sent, no RA received |
Jun 13 2018 08:25:55 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
Time Not Established | Error (4) | Primary lease failed, IPv4 fallback initiated |
Time Not Established | Critical (3) | DHCP failed - RS sent, no RA received |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
Jun 13 2018 07:37:22 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
Time Not Established | Error (4) | Primary lease failed, IPv4 fallback initiated |
Time Not Established | Critical (3) | DHCP failed - RS sent, no RA received |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
Jun 13 2018 06:44:07 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
Time Not Established | Error (4) | Primary lease failed, IPv4 fallback initiated |
Time Not Established | Critical (3) | DHCP failed - RS sent, no RA received |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
Jun 13 2018 06:11:26 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
Time Not Established | Error (4) | Primary lease failed, IPv4 fallback initiated |
Time Not Established | Critical (3) | DHCP failed - RS sent, no RA received |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
Time Not Established | Critical (3) | TFTP Request Retries exceeded, CM unable to register |
Time Not Established | Critical (3) | TFTP failed - Request sent - No Response |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Time Not Established | Warning (5) | ToD request sent - No Response received |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Time Not Established | Warning (5) | Lost MDD Timeout |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Time Not Established | Warning (5) | ToD request sent - No Response received |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Time Not Established | Warning (5) | ToD request sent - No Response received |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Time Not Established | Warning (5) | ToD request sent - No Response received |
Time Not Established | Warning (5) | Lost MDD Timeout |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Time Not Established | Warning (5) | ToD request sent - No Response received |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Time Not Established | Warning (5) | Lost MDD Timeout |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Time Not Established | Error (4) | Primary lease failed, IPv4 fallback initiated |
Time Not Established | Critical (3) | DHCP failed - RS sent, no RA received |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Time Not Established | Critical (3) |
SYNC Timing Synchronization failure - Loss of Sync |
DarrenM
Jun 14, 2018Sr. NETGEAR Moderator
You do seem to have alot of T3 timeouts which is typically a issue with the ISP. you may want a tech to come out and check the cable lines.
DarrenM