What's new

Asus RT-AC66U disconnecting constantly

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

AzNBoY92

Occasional Visitor
Sorry if this question has been answered already but I've searched in a lot of forums and cannot find a fix. I just bought a new Asus RT-AC66U router and it's been working great but for past few days it's been disconnecting randomly on me for a couple of seconds and than starts working again. I've done a factory restore and even reset my cable modem but nothing is working. I have Merlin's latest build. I've check all settings and nothing seems to be wrong. Is this a faulty hardware issue?
 
I forgot to ask you; What exactly is connecting and disconnecting??

If its from your ISP modem, then go to WAN settings and change "DHCP query frequency - Normal".
 
Last edited:
I forgot to ask you; What exactly is connecting and disconnecting??

If its from your ISP modem, then go to WAN settings and change "DHCP query frequency - Normal".

It's just the router dropping the wireless and LAN at the same time for about 10 seconds and than comes back on. This happens at random. The modem is fine it doesn't reset.
 
Which firmware are we talking about exactly?
 
It's just the router dropping the wireless and LAN at the same time for about 10 seconds and than comes back on. This happens at random. The modem is fine it doesn't reset.


Have you tried all OEM Asus firmwares?

If HW/NAT Acceleration is OFF with all oem firmwares and you still having issues, then i honestly dont know. Faulty router perhaps?....
 
Have you tried all OEM Asus firmwares?

If HW/NAT Acceleration is OFF with all oem firmwares and you still having issues, then i honestly dont know. Faulty router perhaps?....

Should the HW/NAT Acceleration be off ? Cause they are defaulted on .
 
Should the HW/NAT Acceleration be off ? Cause they are defaulted on .

Set it to OFF and see what happens. Some people have better results with it being set at OFF. Its trial and error at this point.

And make sure that QoS is OFF as well.
 
It's just the router dropping the wireless and LAN at the same time for about 10 seconds and than comes back on. This happens at random. The modem is fine it doesn't reset.

Have you seen this on more than one computer? The reason I am asking is because I have a laptop that does this every now and then, but none of my other laptops or wired desktops do this. So the problem was with the wireless card on the laptop and not the router.
 
Have you seen this on more than one computer? The reason I am asking is because I have a laptop that does this every now and then, but none of my other laptops or wired desktops do this. So the problem was with the wireless card on the laptop and not the router.

It happens to all devices, LAN and wireless.
 
Set it to OFF and see what happens. Some people have better results with it being set at OFF. Its trial and error at this point.

And make sure that QoS is OFF as well.

Well last night I did a recovery of the router and installed the latest Merlin's firmware I was using before and I haven't turned off NAT acceleration yet but seems like it's working correctly, going to monitor and post back. Maybe it was a bad firmware install but too early to be sure.
 
Set it to OFF and see what happens. Some people have better results with it being set at OFF. Its trial and error at this point.

And make sure that QoS is OFF as well.

Just noticed that it disconnected again so now turning off NAT acceleration and monitor using Merlin's firmware still, if disconnected again will try stock firmware . Trial and error .
 
Post the content of System Log surrounding the time of the disconnection, it might contain clues as to what is actually happening.
 
I have noticed in the system log that it says notify_rc restart every time it does a disconnect! assuming this is the problem what is it?

c8:33:4b:30:2f:83 Dungs-iPhone-4S\
Jan 20 14:08:46 rc_service: ntp 405:notify_rc restart_upnp\
Jan 20 14:08:46 rc_service: ntp 405:notify_rc restart_diskmon\
Jan 20 14:08:46 rc_service: waitting "restart_upnp" via ntp ...\
Jan 20 14:08:46 miniupnpd[419]: HTTP listening on port 54915\
Jan 20 14:08:46 miniupnpd[419]: Listening for NAT-PMP traffic on port 5351\
Jan 20 14:08:46 disk monitor: be idle\
Jan 20 14:09:00 crond[301]: time disparity of 1606748 minutes detected\
Jan 20 14:09:29 nmbd[339]: [2014/01/20 14:09:29, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(392)\
Jan 20 14:09:29 nmbd[339]: Samba name server RT-AC66U is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.1\
Jan 20 14:39:11 dnsmasq-dhcp[374]: DHCPREQUEST(br0) 192.168.1.138 08:2e:5f:7b:70:83 \
Jan 20 14:39:11 dnsmasq-dhcp[374]: DHCPACK(br0) 192.168.1.138 08:2e:5f:7b:70:83 HP-ENVY-DV6\
 
I have noticed in the system log that it says notify_rc restart every time it does a disconnect! assuming this is the problem what is it?

c8:33:4b:30:2f:83 Dungs-iPhone-4S\
Jan 20 14:08:46 rc_service: ntp 405:notify_rc restart_upnp\
Jan 20 14:08:46 rc_service: ntp 405:notify_rc restart_diskmon\
Jan 20 14:08:46 rc_service: waitting "restart_upnp" via ntp ...\
Jan 20 14:08:46 miniupnpd[419]: HTTP listening on port 54915\
Jan 20 14:08:46 miniupnpd[419]: Listening for NAT-PMP traffic on port 5351\
Jan 20 14:08:46 disk monitor: be idle\
Jan 20 14:09:00 crond[301]: time disparity of 1606748 minutes detected\
Jan 20 14:09:29 nmbd[339]: [2014/01/20 14:09:29, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(392)\
Jan 20 14:09:29 nmbd[339]: Samba name server RT-AC66U is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.1\
Jan 20 14:39:11 dnsmasq-dhcp[374]: DHCPREQUEST(br0) 192.168.1.138 08:2e:5f:7b:70:83 \
Jan 20 14:39:11 dnsmasq-dhcp[374]: DHCPACK(br0) 192.168.1.138 08:2e:5f:7b:70:83 HP-ENVY-DV6\

Look at the lines before that. What I can see in this log is that ntp is restarting the upnp and disk monitoring services. We need to see what caused the ntp service to restart. Walk our way back up the chain until the source of all those service restarts.
 
Look at the lines before that. What I can see in this log is that ntp is restarting the upnp and disk monitoring services. We need to see what caused the ntp service to restart. Walk our way back up the chain until the source of all those service restarts.

But the lines before that says the date is from Dec. 31st and I just got this router less then a week ago. The information on those lines does not seem to correlate with today's disconnection date. Here are the lines before the problem occurred.

Dec 31 19:00:14 disk monitor: be idle
Dec 31 19:00:15 Samba Server: daemon is started
Dec 31 19:00:15 dnsmasq[290]: read /etc/hosts - 5 addresses
Dec 31 19:00:16 dnsmasq[290]: read /etc/hosts - 5 addresses
Dec 31 19:00:16 dnsmasq[290]: using nameserver 75.75.76.76#53
Dec 31 19:00:16 dnsmasq[290]: using nameserver 75.75.75.75#53
Dec 31 19:00:16 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Dec 31 19:00:16 dnsmasq[290]: exiting on receipt of SIGTERM
Dec 31 19:00:17 dnsmasq[374]: started, version 2.68 cachesize 1500
Dec 31 19:00:17 dnsmasq[374]: asynchronous logging enabled, queue limit is 5 messages
Dec 31 19:00:17 dnsmasq-dhcp[374]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Dec 31 19:00:17 dnsmasq-dhcp[374]: DHCP, sockets bound exclusively to interface br0
Dec 31 19:00:17 dnsmasq[374]: read /etc/hosts - 5 addresses
Dec 31 19:00:17 dnsmasq[374]: using nameserver 75.75.76.76#53
Dec 31 19:00:17 dnsmasq[374]: using nameserver 75.75.75.75#53
Dec 31 19:00:17 dnsmasq-dhcp[374]: DHCPREQUEST(br0) 192.168.1.129 50:1a:c5:20:14:d8
Dec 31 19:00:17 dnsmasq-dhcp[374]: DHCPACK(br0) 192.168.1.129 50:1a:c5:20:14:d8 XBOXONE
Dec 31 19:00:17 dnsmasq-dhcp[374]: DHCPREQUEST(br0) 192.168.1.129 50:1a:c5:20:14:d8
Dec 31 19:00:17 dnsmasq-dhcp[374]: DHCPACK(br0) 192.168.1.129 50:1a:c5:20:14:d8 XBOXONE
Dec 31 19:00:17 kernel: nf_conntrack_rtsp v0.6.21 loading
Dec 31 19:00:17 kernel: nf_nat_rtsp v0.6.21 loading
Dec 31 19:00:17 rc_service: udhcpc 341:notify_rc stop_upnp
Dec 31 19:00:17 rc_service: udhcpc 341:notify_rc start_upnp
Dec 31 19:00:17 rc_service: udhcpc 341:notify_rc stop_ntpc
Dec 31 19:00:17 rc_service: udhcpc 341:notify_rc start_ntpc
Dec 31 19:00:17 dhcp client: bound 71.226.1.60 via 71.226.1.1 during 283462 seconds.
Dec 31 19:00:17 miniupnpd[411]: HTTP listening on port 39696
Dec 31 19:00:17 miniupnpd[411]: Listening for NAT-PMP traffic on port 5351
Dec 31 19:00:18 WAN Connection: WAN was restored.
Dec 31 19:00:20 dnsmasq-dhcp[374]: DHCPDISCOVER(br0) 7c:1e:52:57:4f:58
Dec 31 19:00:20 dnsmasq-dhcp[374]: DHCPOFFER(br0) 192.168.1.231 7c:1e:52:57:4f:58
Dec 31 19:00:20 dnsmasq-dhcp[374]: DHCPDISCOVER(br0) 7c:1e:52:57:4f:58
Dec 31 19:00:20 dnsmasq-dhcp[374]: DHCPOFFER(br0) 192.168.1.231 7c:1e:52:57:4f:58
Dec 31 19:00:20 dnsmasq-dhcp[374]: DHCPREQUEST(br0) 192.168.1.57 e4:8b:7f:a2:ab:b5
Dec 31 19:00:20 dnsmasq-dhcp[374]: DHCPACK(br0) 192.168.1.57 e4:8b:7f:a2:ab:b5 Dungs-iPad
Dec 31 19:00:20 dnsmasq-dhcp[374]: DHCPREQUEST(br0) 192.168.1.231 7c:1e:52:57:4f:58
Dec 31 19:00:20 dnsmasq-dhcp[374]: DHCPACK(br0) 192.168.1.231 7c:1e:52:57:4f:58
Dec 31 19:00:40 dnsmasq-dhcp[374]: DHCPREQUEST(br0) 192.168.1.146 c8:33:4b:30:2f:83
Dec 31 19:00:40 dnsmasq-dhcp[374]: DHCPACK(br0) 192.168.1.146 c8:33:4b:30:2f:83 Dungs-iPhone-4S
 
But the lines before that says the date is from Dec. 31st and I just got this router less then a week ago. The information on those lines does not seem to correlate with today's disconnection date. Here are the lines before the problem occurred.

This actually indicate that your router had crashed and rebooted itself.
 

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top