NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

LuciferDN's avatar
LuciferDN
Initiate
Jul 17, 2017

C6300 wifi problem

Really tired about the router. it keeps disconnected only my wifi in every 10 to 15 minutes. Anyone can help me solve this problem? My Firmware Version is V2.01.18 The largest packet size from pin...
Hardware
Troubleshooting
DarrenM's avatar
DarrenM
Sr. NETGEAR Moderator
Jul 19, 2017

Hello luciferDN

 

is it all wifi or certain devices? have you tried to adjust the wireless channel?

 

DarrenM

LuciferDN's avatar
LuciferDN
Initiate
Jul 22, 2017

All the devices. I try to restarted it but it disconnected about 10 mins later.

  • DarrenM's avatar
    DarrenM
    Sr. NETGEAR Moderator
    Jul 26, 2017

    Can you post the logs from the modem?


    DarrenM

    • hawkeye7's avatar
      hawkeye7
      Aspirant
      Aug 10, 2017

      Same issue. Firmware v 2.01.18. Log files:

       

      TimePriorityDescription
      Aug 08 2017 21:47:53Critical (3)No Ranging Response received - T3 time-out
      Aug 06 2017 21:23:04Critical (3)SYNC Timing Synchronization failure - Loss of Sync
      Aug 06 2017 19:40:33Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out
      Aug 06 2017 19:40:32Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
      Aug 06 2017 19:34:14Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
      Aug 06 2017 19:32:13Warning (5)Lost MDD Timeout
      Aug 06 2017 19:32:07Critical (3)SYNC Timing Synchronization failure - Loss of Sync
      Aug 06 2017 19:14:49Critical (3)No Ranging Response received - T3 time-out
      Aug 01 2017 15:26:10Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
      Aug 01 2017 15:22:19Critical (3)No Ranging Response received - T3 time-out
      Aug 01 2017 15:19:47Critical (3)No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
      Aug 01 2017 15:19:42Warning (5)Lost MDD Timeout
      Aug 01 2017 15:19:38Critical (3)SYNC Timing Synchronization failure - Loss of Sync
      Aug 01 2017 15:14:30Critical (3)No Ranging Response received - T3 time-out
      Aug 01 2017 14:49:41Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
      Aug 01 2017 14:47:14Warning (5)Lost MDD Timeout
      Aug 01 2017 14:47:08Critical (3)SYNC Timing Synchronization failure - Loss of Sync
      Aug 01 2017 14:10:02Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
      Jul 04 2017 15:47:15Critical (3)No Ranging Response received - T3 time-out
      Jun 20 2017 05:15:07Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
      Jun 20 2017 05:14:08Critical (3)No Ranging Response received - T3 time-out
      Jun 20 2017 05:14:08Critical (3)Unicast Ranging Received Abort Response - initializing MAC
      Jun 19 2017 11:38:52Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
      Jun 10 2017 05:52:37Critical (3)No Ranging Response received - T3 time-out
      Jun 05 2017 04:53:49Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
      Jun 05 2017 04:52:38Critical (3)No Ranging Response received - T3 time-out
      Jun 05 2017 04:52:38Critical (3)Unicast Ranging Received Abort Response - initializing MAC
      Jun 05 2017 04:30:06Critical (3)No Ranging Response received - T3 time-out
      Jun 05 2017 00:38:13Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
      Jun 05 2017 00:37:45Critical (3)No Ranging Response received - T3 time-out
      Jun 05 2017 00:17:31Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
      Jun 05 2017 00:15:11Warning (5)Lost MDD Timeout
      Jun 05 2017 00:15:05Critical (3)SYNC Timing Synchronization failure - Loss of Sync
      Jun 04 2017 13:34:56Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
      Jun 01 2017 12:28:18Critical (3)No Ranging Response received - T3 time-out
      May 31 2017 13:27:19Warning (5)Lost MDD Timeout
      May 25 2017 15:59:14Critical (3)No Ranging Response received - T3 time-out
      May 25 2017 12:43:56Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
      May 25 2017 12:43:37Critical (3)No Ranging Response received - T3 time-out
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received
      May 25 2017 12:43:14Critical (3)REG RSP not received

       

       

    • hawkeye7's avatar
      hawkeye7
      Aspirant
      Aug 10, 2017
      DescriptionCountLast OccurrenceTargetSource
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.241Thursday, 10 Aug 2017 15:18:590.0.0.00.0.0.0
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.241Thursday, 10 Aug 2017 15:18:570.0.0.00.0.0.0
      [admin login] from source 192.168.0.341Thursday, 10 Aug 2017 15:15:070.0.0.0192.168.0.34
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.241Thursday, 10 Aug 2017 15:05:100.0.0.00.0.0.0
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.241Thursday, 10 Aug 2017 15:05:090.0.0.00.0.0.0
      [admin login] from source 192.168.0.341Thursday, 10 Aug 2017 15:01:330.0.0.0192.168.0.34
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.241Thursday, 10 Aug 2017 14:58:420.0.0.00.0.0.0
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.241Thursday, 10 Aug 2017 14:58:410.0.0.00.0.0.0
      [admin login] from source 192.168.0.341Thursday, 10 Aug 2017 14:51:460.0.0.0192.168.0.34
      [DHCP IP: (192.168.0.34)] to MAC address 80:00:0b:48:c8:441Thursday, 10 Aug 2017 14:51:420.0.0.00.0.0.0
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.241Thursday, 10 Aug 2017 14:51:410.0.0.00.0.0.0
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.241Thursday, 10 Aug 2017 14:51:390.0.0.00.0.0.0
      [DHCP IP: (192.168.0.24)] to MAC address 00:24:b2:0e:52:691Thursday, 10 Aug 2017 14:51:360.0.0.00.0.0.0
      [admin login] from source 192.168.0.341Thursday, 10 Aug 2017 14:51:130.0.0.0192.168.0.34
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.241Thursday, 10 Aug 2017 14:45:210.0.0.00.0.0.0
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.241Thursday, 10 Aug 2017 14:45:200.0.0.00.0.0.0
      [admin login] from source 192.168.0.341Thursday, 10 Aug 2017 14:41:550.0.0.0192.168.0.34
      [DoS attack] ICMP Flood from 128.10.18.521Thursday, 10 Aug 2017 14:39:3524.98.137.22128.10.18.52
      [DoS attack] ICMP Flood from 129.22.150.781Thursday, 10 Aug 2017 14:39:1424.98.137.22129.22.150.78
      [DoS attack] ICMP Flood from 129.10.120.1931Thursday, 10 Aug 2017 14:38:4624.98.137.22129.10.120.193
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.241Thursday, 10 Aug 2017 14:38:440.0.0.00.0.0.0
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.241Thursday, 10 Aug 2017 14:38:420.0.0.00.0.0.0
      [DoS attack] ICMP Flood from 128.8.126.1111Thursday, 10 Aug 2017 14:38:1924.98.137.22128.8.126.111
      [DoS attack] ICMP Flood from 165.230.49.1181Thursday, 10 Aug 2017 14:37:5124.98.137.22165.230.49.118
      [DoS attack] ICMP Flood from 128.223.8.1131Thursday, 10 Aug 2017 14:36:5724.98.137.22128.223.8.113
      [DoS attack] ICMP Flood from 129.110.125.521Thursday, 10 Aug 2017 14:36:2924.98.137.22129.110.125.52
      [DoS attack] ICMP Flood from 198.133.224.1471Thursday, 10 Aug 2017 14:36:0124.98.137.22198.133.224.147
      [DoS attack] ICMP Flood from 129.110.125.521Thursday, 10 Aug 2017 14:35:3524.98.137.22129.110.125.52
      [admin login] from source 192.168.0.341Thursday, 10 Aug 2017 14:34:200.0.0.0192.168.0.34
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.241Thursday, 10 Aug 2017 14:31:230.0.0.00.0.0.0
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.241Thursday, 10 Aug 2017 14:31:220.0.0.00.0.0.0
      [DoS attack] ICMP Flood from 128.10.18.521Thursday, 10 Aug 2017 14:30:5224.98.137.22128.10.18.52
      [DoS attack] ICMP Flood from 170.140.119.701Thursday, 10 Aug 2017 14:29:3724.98.137.22170.140.119.70
      [DoS attack] ICMP Flood from 156.56.250.2271Thursday, 10 Aug 2017 14:29:0924.98.137.22156.56.250.227
      [DoS attack] ICMP Flood from 137.165.1.1141Thursday, 10 Aug 2017 14:28:4124.98.137.22137.165.1.114
      [DoS attack] ICMP Flood from 129.22.150.781Thursday, 10 Aug 2017 14:28:1624.98.137.22129.22.150.78
      [DoS attack] ICMP Flood from 129.10.120.1931Thursday, 10 Aug 2017 14:27:4624.98.137.22129.10.120.193
      [DoS attack] ICMP Flood from 128.8.126.1111Thursday, 10 Aug 2017 14:27:1924.98.137.22128.8.126.111
      [DoS attack] ICMP Flood from 165.230.49.1181Thursday, 10 Aug 2017 14:26:5424.98.137.22165.230.49.118
      [DoS attack] ICMP Flood from 128.223.8.1131Thursday, 10 Aug 2017 14:25:5724.98.137.22128.223.8.113
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.241Thursday, 10 Aug 2017 14:25:420.0.0.00.0.0.0
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.241Thursday, 10 Aug 2017 14:25:410.0.0.00.0.0.0
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetNATRSIPStatus] from source 192.168.0.241Thursday, 10 Aug 2017 14:25:380.0.0.00.0.0.0
      [UPnP set event: urn:schemas-upnp-org:service:WANIPConnection:1#GetConnectionTypeInfo] from source 192.168.0.241Thursday, 10 Aug 2017 14:25:370.0.0.00.0.0.0
           
      • DarrenM's avatar
        DarrenM
        Sr. NETGEAR Moderator
        Aug 16, 2017

        Hello Hawkeye7

         

        You have alot of T3 timeouts this maybe a cable line issue I suggest contacting your ISP and having them come out and check your lines.

         

         

        DarrenM