Samsung galaxy s2 wifi authentication error occurred

All forum topics Previous Topic Next Topic. ChrisM Moderator. Hi DocFar Are you still having this issue? Edgie70 Helping Hand. I had this on mine , I put it in to flight mode then put WiFi on. Stef29 Journeyman. Thank you for the reply I did a soft reset and did a hard reset and reinstalled and it still happens: it says authentication error..

Still having problems!!! I am wondering of this is some hardware problem with some pads but not all??? Chris: Have you seen my reply? Any suggestions? Post Reply. Related Content. If a phone has one installed, they can cause the phone to malfunction in certain ways. And your phone is not special and your setup is no different than the setup on my phone.

Or as you said "go out and buy an iPhone". You don't have to reset your phone, if you don't feel the need. Just make sure you blame the right people. Thanks - I tried that also Normal network and guest network. I dont remember if it worked any better for me. What I have found that helped to reduce the pain is: install "Wifi Automatic" by j4elin from the Google Play store.

Also in you phone Wifi settings It takes away some of the stuck "needs authentication" Wifi issues I find turning off and, on the Wi-Fi, usually fixes this. Try this bandaid I dont notice the pain anymore of my cellphone with stuck "needs authentication" wifi. I've been running into this for a while - can't remember when it started.

What's odd, like so many others, is that it's just one device - my Samsung Note10; my wife's Samsung S10 has been fine. This took a bit longer than I would have expected and through some states that I'm not able to recreate, particularly, at one point it was auto-reconnecting to my router with a message that said "Connected via Orbi" instead of just "Connected". Anyway, part of the key to getting where I am now was turning off "Auto-Reconnect" before trying to remove the network.

Then a bunch of delete, add, turn off auto-reconnect, turn off wi-fi, turn back on wi-fi, delete connection, restart phone For good measure, I removed the Orbi app after the 1st or 2nd restart of my phone, then re-installed after the 3rd or 4th restart. There were at least 2 or 3 times where I had "deleted" my connection, only for the phone to find and automatically connect to my network on resetart. I'm really not sure where this was coming from, but when this happened, I definitely was seeing "Connected via Orbi" for the connection.

My phone's now showing just "connected" no "via Orbi" with a Mbps network speed and no authentication errors that I've noticed since this afternoon, so I'm keeping my fingers crossed that there was some sort of weird interaction between Samsung and the Orbi software that's now been broken for better or worse? At least no authentication errors, so at least that part's better. I'll update if the problem comes back, but I'm feeling good that my previous attempts to "reset wifi" weren't successful at really getting me to a fresh restart, hence why following that advice forget, then reconnect didn't seem to fix my problem more than temporarily.

I'm starting to believe that there are several things that are happening and there's a certain amount of "bad luck" that has to happen when you add your Wi-Fi network to your phone.

If you happen to get a "bad" connection during setup, it will give you the intermittent "authentication" problem until you forget the connection. It's fairly likely that forgetting and re-adding once or twice or three times won't be enough. I just wish it was more definite than that, and I wish I had some understanding of what can be done to have a better chance of getting a "good" connection from the start.

I wish there was a good way of getting Samsung to put in the work to identify and fix the problem. I wish I had million dollars. I've seen a similar issue with file transfers using encryption where there was a mismatch in the implementation of the algorithm negotiated for security.

In this case, IF a particular algorithm picked and AND the data just happened to have a certain special character then negotiation failed, and, therefore, the authentication failed, but if the data in the negotiation didn't have the special character then it worked.

However, in that case, this was happening on a server where I had verbose debugging information and could see all the details. Unfortunately, the issue was deep in some 3rd party drivers that I had no control over, but, fortunately, the remote vendor changed protocols and the new algorithms in the new protocol were much more reliable. Working backwards from what I'm seeing, it's almost as if Samsung caches which algorithm was successful in negotiation at the time of setup maybe to save time on subsequent connections?

Maybe it only advertises that one "good" algorithm as compatible? What doesn't feel right to me is why that wouldn't be renegotiated fully each time or how it would ever settle on a better algorithm. Without logging tools to see exactly where and why the "authentication" is failing, as well as what algorithm was used, it's going to hard to collect any useful evidence to present to Samsung.

Anyone know of an easy, non-root, way to add this level of debugging to the Android wi-fi connection? Again, I'll update in a few more days, just to see if the "fix" sticks.

Is there a way to get more detailed logs out of Orbi than what is in the web UI administration area? However, there is nothing in the log showing the detail of a device attempting to join. I have these same problems of "couldn't authenticate connection". If we could see detailed protocol logs we could probably figure out what is actually going on here. We are investigating this as the highest priority and will provide updates at Status. Join Now Log In Help. All forum topics Previous Topic Next Topic.

I really dont want to move off of Android to an Apple cell phone to fix this issue. Jeff S. Message 1 of Labels: Troubleshooting. Me too. Message 2 of Message 3 of Message 4 of Message 5 of But I don't have any special device turned on when I do my tests Looking for more information about Wi-Fi signals, I discovered that frequencies from to MHz Wi-Fi channels 1 to are used by "radio amateur".

It would therefore be advisable to check within the neighborhood if anyone has such a hobby. This could likely be the case if the Wi-Fi issues are only experienced during certain period of the day e. I finally read that channels 1, 5, 9 and 13 are known to be used by some wireless transmitter and camera at least here in Europe.

As I don't have such devices, and taking into account the info about the frequencies used by "ham radio", I decided to use the channel 9 or Concretely I did switch from channel 6 to channel 13 on all my access points and could immediately connect flawlessly from all locations where I was experiencing issues previously. That being said, there are possibly some other locations still to be discovered where I will experience again the problem.

But for sure, changing the frequency has an impact on the connection! Your email address will not be published. Save my name, email, and website in this browser for the next time I comment. Notify me of followup comments via e-mail. You can also subscribe without commenting.