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 ...
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.
- Got the same update. Still getting the same error. My device is the only device in the house that has this issue. And my phone is not the only Samsung, so I still believe it is directly related to the update from Oct/Nov last year. Never had this problem with my phone or my Orbi before then
I'm not sure why my experience is differnt. My issue clearly began with the November update to the Galaxy S6 on Verizon. I have two S6 in the house and they both experienced the same Authentication Error Occured issue at the same time. The same fix of moving to the guest network worked for both of them, but I have no idea why that worked.
In an effort to possibly help others, I'll describe a sequence of events that happened on my WiFi network over the past month.
I was out of town for a few days in January and when I returned my network wasn't working correctly. I had to power-cycle my Cable modem and Orbi system. When I power-cycle I usually power off satellites, then power on the base unit, attach and confirm it is working and then power up the satellites one at a time (I have two). If I'm doing the cable model also, I leave the Orbi powered off, power cycle the cable model, wait until it is fully initialized and then start the Orbi power up process. So I did this before I received the Samsung update. I later recieved the Samsung update. The next thing that happened last weekend we noticed the Bose Soundtouch system we have no longer connected to the network. This may have been a problem for a few days, but it was when I was fixing that system that I had to connect to the main WiFi network on the Orbi. That's when I also noticed one of my satellites was not connecting properly. I powered off the satellite. Re-initilzed the Bose Soundtouch system. Connected to the main WiFi network. Powered up the Orbi satellite. Tested all the speakers and just kept my Samsung device on the main network.
I don't beleive all of this stuff is really related, but the point being, I had some sort of an odd problem with my Orbi system that required me to go through this power-cycle sequence. That issue seemed to have affected my Bose Soundtouch as well. The Samsung update happened in amoungst all of this, so I can't be sure that it was definately the Samsung update or if was a combination of factors. I haven't checked to see if my strange issue with my Orbi system was due to a system update or not. I have mine set to an automatic update.