What's new

RT-AC87R Connection Drops

  • 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!

Ivrim

New Around Here
Hello, I've been browsing around the forums and I couldn't seem to find anyone with the same issue so here goes. I have the RT-AC87R currently running firmware 3.0.0.4.378_6117 which is a beta firmware.

All wired connections are perfectly fine.

My issue is that on my Samsung Note 4 I use a backup application called Titanium Backup to backup my phone every night at 3 AM. These backups usually take around 1-2 hours and they are synced to my Dropbox account. If you're not an Android person, think of it as iCloud on steroids. Anyways just about 50% of the time I wake up in the morning to find that the upload has failed due to a network error as stated by Titanium Backup. I have tried tweaking just about every setting in the router, I emailed ASUS customer support and applied their recommended settings, and I have tried various firmwares such as the beta i'm using now, the latest public release firmware, and the latest Merlin build as well, and this problem still persists.

Another issue is that I have someone in my house who uses an iPhone 6 and basically any time they are on a phone call and walk into the kitchen, the call will drop because they are using wifi calling. Now the interesting part about this is that, this isn't even the furthest part of the house from the router and yet the phone will do fine while on a call anywhere else in the house.

Lastly, I use the same SSID for both my 2.4 and 5 GHz bands, is this a bad thing? I figured that it would just let my devices pick the best connection, permitted that they can support the 5GHz.

If more info is required let me know as these problems are driving me insane and I just want this router to work!

Thank you.
 
I have a few ideas:

1. Generally, I'd recommend setting different SSIDs for your different bands (2.4 and 5). The vast majority of the trouble I had with this router related only to 5Ghz, so separating which devices connected to 2.4Ghz was helpful in diagnostics.

2. The iPhone 6 wifi calling issue will be easier to diagnose when you stick on one band. It is possible something in your kitchen is throwing off a bunch of noise and killing 5 or 2.4 Ghz for the phone. It's also possible the phone is swapping between the 2.4 and 5 bands due to interference, this might cause the call to drop if it cannot negotiate the handoff.

3. I have a Samsung Galaxy S6 regularly connected to my 5Ghz band, but sometimes at random times during the day I'll watch it swap over to the 2.4Ghz network automatically (and then stay there until I come back from work the next day). I don't know if this is due to a signal issue, or if the phone is detecting a loss of connectivity on 5Ghz. I wonder if this might be occurring at night during your automatic backup. Even if your phone was just swapping bands, it would potentially kill the backup procedure (which I assume requires one continuous connection, and does not handle interruptions very well).
 
Just tried separate names for the SSID's and the problem still persists while connected to 2.4GHz and 5GHz bands by themselves. Crazy... I appreciate the advice though.
 
Just tried separate names for the SSID's and the problem still persists while connected to 2.4GHz and 5GHz bands by themselves. Crazy... I appreciate the advice though.
Hi,
Asus is trying to duplicate the problem and is aware of samsung wifi issues with the 87.

On IOS Well read this:)
Noticed your iPhone and Mac’s Wi-Fi weren’t so good over the last year? You’re not alone, and Apple is finally fixing it, albeit quietly.
Wi-Fi problems were one of the biggest complaints about Apple’s Yosemite update for Mac last year, with thousands of users taking to Apple’s support forums to air frustration.
Ever since upgrading to yosemite, discoveryd goes to 100% cpu and dns requests fail. What new nightmare is this?! pic.twitter.com/ErYAtAsAbM
— Michael Koziarski (@nzkoz) October 17, 2014
If you’re wondering exactly what happened, there are a few moving parts. First, you need to understand what the Domain Name System (DNS) does.
Each computer on the internet has an IP address, which is like where it can be found on a street. Domain names for websites, like thenextweb.com, have an attached IP address that locates these computers. Think of a domain name as a human-readable way to get to the right IP address.
DNS servers, like the ones Google or your internet provider offers, keep a directly of domain names and their IP addresses.
When you type thenextweb.com into your Web browser, your computer requests the address from a DNS server, then takes you to the right page. It all happens without your knowledge — at least, when it works.
For the better part of twelve years, Apple used a single piece of software called “mDNSResponder” to manage much of your Mac’s networking, including this lookup process. In general, it worked flawlessly.
When OS X Yosemite rolled around in late 2014, Apple decided to rip out the trusty DNS responder and replaced it with a new process called “discoveryd.”
We don’t know the exact reason for dropping it, but the replacement appeared to be related to the new Airdrop to iPhone feature that was part of the update. Apple re-wrote the discoveryd process from the ground-up in a new language, C++.
Screen Shot 2015-06-10 at 16.25.15
The problems with discoveryd have been vast and unpredictable. You’ve probably run into at least one: duplicate computer names, random crashes, slow page loading, slow reconnection after sleep — the list goes on.
Apple tried on three occasions to patch out the problems, but the complaints continued to flow in. When a beta build of OS X hit 10.10.4 in May, discoveryd suddenly vanished after months with no fix.
At first, many wondered if it was an accident, but mDNSResponder had miraculously returned and has stuck around in the latest beta builds.
At WWDC we’ve learned that Apple has killed discoveryd in both iOS 9 and OS X 10.11 and mDNSResponder is back once again. When we get the updates later this year, your devices’ Wi-Fi should be a lot more reliable.
In the meantime, OS X 10.10.4, which is currently in beta, also drops discoveryd and should be available soon for download.
Apple never officially commented on why it dropped the new app (we’ve asked, again) , but the change will be a welcome one for anyone who uses its products.

Hopefully the next IOS update does fix it:) (and maybe if and when Asus finds the samsung issue that fixes the rest)
 
Hi,
Asus is trying to duplicate the problem and is aware of samsung wifi issues with the 87.

On IOS Well read this:)


Hopefully the next IOS update does fix it:) (and maybe if and when Asus finds the samsung issue that fixes the rest)
Oh okay, well it's good to know that they are aware, I appreciate the feedback. Thanks!

Sent from my SM-N910T using Tapatalk
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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