NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Authentication Error Occurred
My wife and I both have Samsung S6. Recently received an update to the phone and afterwards it no longer stays connected to Orbi. My Orbi is on version 2.0.0.74. I tried rolling back to 1.11.0.20 like some posts suggested but within a 60 seconds it auto-updates its firmware back to the latest.
Both phones says "Authenication Error Occurred" under the WiFi network. If I turn off WiFi and back on it will reconnect. But within 30-60 seconds it disconnects with the error again.
In addition to firmware I have factory reset the Orbi which didn't resolve the issue.
Thanks
70 Replies
- My wife and I are in the same boat. We both have samsung galaxy S6 phones and received the same update. We too can no longer stay connected to our orbi. Our phones display an authentication error and we must turn Wi-Fi off and back on to re-connect. I have factory reset the phones and reloaded all phone updates yet the problem persists. We have loved our orbi up til now. I would love some help in fixing this problem.
Same for me... after I updated last week on our phones (two Galaxy S6 and one Galaxy S7 - Verizon), none of our phones can keep a solid WiFi signal. Sometimes it disconnects after 5 minutes, sometimes 30 minutes. Often the phone says 'Authentication Error Occured'. I have also had massive issues using both my Satellite and main Router, so I have take the Satellite offline (powered off) to simplify the situation. I am also running the latest BETA firmware (2.0.0.76).
The funny part is that today I have turned the WiFi back on with my ISP router and even tho it sucks, it still works better than the ORBI.
This is completely maddening for a system so expensive.
I have the same issue on a Samsung A5 (but not on a OnePlus 3T),,,
- I am in the same boat. I am randomly being forced offmy network by this again and again after updating the S6.
Any netgear folks have hints as to how to debug the logs? Same here. Pretty aggrevating. Not sure if it's Orbi or Samsung. At this point I wish I would have invested in a Nighthawk instead. Hopefully someone figures a work around or updates the firmware QUICKLY.
YMMV but I set my phone as a static IP mapping in the Orbi settings and it seems to be roaming fine....
- I spoke too soon still happening. Super frustrating.
- Well since I am still in the return window for my orbi I am considering taking it back. I don't have time to troubleshoot a $400 router for weeks on end. Anybody heard anything about the linksys velop system?
My wife and I also have two Samsung S6 phones with Verizon. Some time after the last Samsung update, we can no longer retain connections to our home WiFi via ur Orbi system (1 router, 2 sats). It's SUPER annoying, after having relative success with Orbi prior... The message against the SSID in our wireless settings reads "Authetication issue has occurred". We have no issue connecting to WiFi outside our home (at Starbucks, work, etc.), so it is definitely an issue between our phones and Orbi's system.
Though there is definitely responsibility on Android's part for this issue, it appears that Netgear/Orbi has not done sufficient testing to resolve since this was reported within this community.
While I'm happy with the performance of our system, when working, a lack of support responsiveness would definitely sour me to buying further products from Netgear.
Getting the same authentication errors as others on this post.
android version 7.0
kernal 3.10.61
Are steps being taking to resolve this issue?
FYI... The solution to turn off the 5GHz transmission under the Advanced Network Settings does work to temporarily resolve the connectivity issues described above. I performed this change this weekend, and my wife & I have had consistent connections to our WiFi since... after not having consistent connectivity for >1week (likely longer).
Though this is not a valid solution long-term, as we would like to take advantage of 5GHz connection speeds, atleast it's a stop-gap for now.
The right solution is for Netgear to fix the root cause issue.
Hi - I have the same problem. Waited 6-months for a good deal on the Orbi AC3000 system and just got it. Disappointed to find that it does no work with my GS6 Active.
One more comment that may be helpful or not. On Orbi I turned off the "Enable SSID Broadcast" after I already had many devices connected because of this problem. What is interesting however is that many of the devices still show they are connected at 5 GHz. I'm not sure if they really are but that's what they show. I guess it would be because since they found the 5GHZ band before I turned the broadcast off and they remembered it. Just guessing that if someone has the same problem they can turn the broadcast off and still not be limited to 2.5GHz for devices already connected. My phone still shows 2.5 and also doesn't disconnects all the time. Just my 2 cents.
- A quick question about splitting SSID's. Have you found that you need to connect the s6 to just the 2G channel to get it to work or can you have it connect to the 5G as well?
Wife and I both have this issue with the S6 as well. I used the link posted earlier and noticed a suggestion to use the guest network. I don't know why that works, but it does. I enabled the guest network and connected our S6 phones to it. No more authentication errors. Because we use our phones to control a number of things on our home network, I also enabled the guest network to access the local network. Yes, I have enabled WPA security with a password even for the guest network. This has returned full functionality to our phones without disrupting the other devices on the network that have been working fine.
There is one glitch in the process and that is with the Bose Soundtouch system. Some of our speakers seem to randomly be available and then not available, but I'm still working on that one. Could just as well be a Bose issue at this point.
Issue seems to have occured with the S6 early November update. A more recent update from Samsung did not fix the problem. It's a compatibility issue of some type since I'm not having any issue with my iPhone and Orbi and I'm not having any issue with my S6 and other WiFi systems (and now no problem with Orbi Guest Network).
Anyone know what is different about the Guest Network setting that may allow it to work better?
- Very interesting about the guest network workaround. Have you noticed any speed throttling compared to using main SSID?
What is working for me currently is using my router in AP mode and disconnect my satellite. Downside to this is parental controls are disabled.
When I get a chance I'll try it guest network in router mode.I have not noticed any speed differential. I just ran SpeedTest from the Android app and it shows 92.87Mbps. A lot of variables influence the number, but it's certainly fast enough. I received a 312 yesterday. No configuration changes. Most everything I do with my smartphone though isn't bandwidth intensive. Even music streaming doesn't require much bandwidth and I only do that occasionally. All other devices remain on the main SSID. Only my smartphone is on the guest network.
Many people facing this annoying issue. This can happen due to many reasons. For me, its work properly after modifying network connection, try this solution. And if it's not working for you, the best option will be to call customer care and ask for a technical visit.
I actually went the route of doing a factory reset of my phone and it started to work again, had some drops but would reconnect pretty quickly... especially when moving from main to satellite... this seemed to be the solution... for about 3 days. Then when I tried to connect to the WiFi for my Phantom 3 the issues came back full force... cleared cached... deleted WiFi networks and apps... no real look. I'm moving on to the guest network solution to see if that works.
I have a S6 Edge.
The only fix for me was the guest network option, which is not ideal. Even my Ring Doorbell was having issues and had to get a Ring Chime Pro to fix it.
Received a recent update to my Samsung S6 and I am no longer experiencing the issue on the main network. I switched one device back over to the main network and left the other device (my wife) on the guest network. No more authentication issue.
I have not seen any issues with other devices either as some are reporting.
I'm now on G920VVRSRDRA1 that was updated on January 26.
Galaxy S6.
I'll be switching by guest network back to a true guest network soon and will be back to loving my Orbi.
Interested to hear from other S6 users to see if this update has worked for them.