No idea if this is helpful, but we are told to sign out of windows and sign back in with the new password after a password change otherwise we run into weird certificate or login issues. Sometimes i wipe the certificate list and reset and it fixes some of the quirky issues.
but we are told to sign out of windows and sign back in with the new password after a password change otherwise we run into weird certificate or login issues. Sometimes i wipe the certificate list and reset and it fixes some of the quirky issues.
Yeah that's to avoid login issues and be sure that the new pw is synced between the domain and AD. But: I expect that if I reset a pw to a user, he gets kicked out immediately from the wifi, but that's not the case!
I assume the thing doing the auth for wifi is a radius server. Radius servers have a cache, and they may interrogate any domain controller to validate credentials. I am quite rusty on radius, but there should be a setting for it to have a lower cache time, to the cost of more traffic and shorter resiliency if all domain controllers are down.
Yeah. Check the logs on the radius server or whatever. That'll tell you exactly what's happening. No need to speculate.
The tech in charge of the radius said that there is no memory of logged user. Radius server check with AD every time someone authenticates. Is this possible?
Community for discussing enterprise networks and the ensuing chaos that comes after inheriting or building one.