Club PA 2.0 has arrived! If you'd like to access some extra PA content and help support the forums, check it out at patreon.com/ClubPA
The image size limit has been raised to 1mb! Anything larger than that should be linked to. This is a HARD limit, please do not abuse it.
Our new Indie Games subforum is now open for business in G&T. Go and check it out, you might land a code for a free game. If you're developing an indie game and want to post about it, follow these directions. If you don't, he'll break your legs! Hahaha! Seriously though.
Our rules have been updated and given their own forum. Go and look at them! They are nice, and there may be new ones that you didn't know about! Hooray for rules! Hooray for The System! Hooray for Conforming!

Authentication error when phone reconnects to home wireless

TofystedethTofystedeth veni, veneri, vamoosiRegistered User regular
A couple weeks ago I finally replaced my venerable WRT54GL.
I kept the SSID and password the same, but just to be safe, told my phone (Galaxy S6) to forget the network and manually reconnected to it. However it frequently fails to properly reconnect, such as when I come home from work or being idle overnight.

The wifi networks thing just shows "authentication error", and all it takes to fix it is just toggling wifi off (either from the actual wifi menu or the notification pulldown menu) and back on.

With my old router this happened occasionally, usually in the overnight scenario, but it also had no error message, but it's an every day kind of thing now.

Is there some weird cache i need to blow out or something?

steam_sig.png

Posts

  • bowenbowen How you doin'? Registered User regular
    Delete the saved network in your device, reboot it, and then re-add it. It probably still has remembered WPA1 stuff instead of WPA2 stuff and it might be somewhat lazy about how it handles re-authing ever so often, after the initial connect.

    Ladies.
    Feral
  • FeralFeral MEMETICHARIZARD along with you if I get drunk well I know I'm gonna be gonna be the man whoRegistered User regular
    bowen wrote: »
    Delete the saved network in your device, reboot it, and then re-add it. It probably still has remembered WPA1 stuff instead of WPA2 stuff and it might be somewhat lazy about how it handles re-authing ever so often, after the initial connect.

    I have definitely seen it where a client device keeps trying to use TKIP even after the network is upgraded to AES and the only way to fix it is to delete the saved wifi profile from the client and readd it.

    That was a long time ago, but still

    every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
    the "no true scotch man" fallacy.
    bowenShadowfire
  • TofystedethTofystedeth veni, veneri, vamoosi Registered User regular
    bowen wrote: »
    Delete the saved network in your device, reboot it, and then re-add it. It probably still has remembered WPA1 stuff instead of WPA2 stuff and it might be somewhat lazy about how it handles re-authing ever so often, after the initial connect.

    Dang, I thought this might have taken care of it since it was well behaved the last several days, but it did it again just now when I got back from shopping.

    steam_sig.png
  • bowenbowen How you doin'? Registered User regular
    I've been thinking about this on and off but I can't put my finger on what might be the cause.

    Try updating the firmware of the router and then if that doesn't solve it, perhaps make a whole new AP with security key just to rule out something isn't cached somewhere? Nothing else is having this trouble right?

    Ladies.
    Shadowfire
Sign In or Register to comment.