...so clearly it's an issue with this guy's laptop and not the Meraki Wi-Fi. Other users can connect to this 802.1x SSID with their laptops. This guy can also successfully join the SSID with his iPhone, so it's not a user credentials issue. We have 3 Meraki APs in the office and he can't connect to any of them. I have not yet done a packet capture. The SSID config on the client is "managed by your org's administrator" so there's only so much I can do on the client itself. It's a Windows 10 Pro machine, fully patched. We have a guest SSID (PSK) and he can connect to that fine. Connectivity tests from Meraki dashboard to RADIUS server with my own credentials pass (I don't know his creds to test with).   A client history entry in the dashboard says this below. Wondering if the user's old password is still somehow cached and trying to send that upon connecting... Failed connection to SSID <<>> on AP <<>> during authentication because the auth server rejected the auth request. Then I saw this thread below and its solution, but I'm not able to 'Forget' the SSID and get the laptop to re-prompt for creds when I join it, probably because of the "managed by your org's admin". Other suggestions?   https://community.meraki.com/t5/Wireless-LAN/802-1X-EAP-failure-with-Windows-AD-Radius-Help/m-p/51700#M7833 ... View more