sometimes you just have to ask for help and then you figure out how to at least get things working. windows 10 is now connecting. I found the setting to "verify the server's identity by validating the certificate" for the wi-fi network profile in windows 10 and turned it off. the laptops are now able to connect. as a side note I had placed the certificate the freeradius server is using into the Local Computer Trusted Root Certification Authorities store and made sure the intermediate and root certificates were also in there on the computers that I was trying to connect on. this is a wildcard certificate issued by a public ca, I'm guessing that maybe because the radius servers name isn't in the subject alt name section it's failing to validate on Windows 10. I think we should be able to figure out our certificate problems from here. Thanks Gary *********************************** previous message I've recently setup freeradius and configured an ssid to use 802.1x authentication with this server. So far android, ipad, chromebook, and macOS devices seem to be connecting fine. Windows 10 devices are not working (seem to be failing at the radius level), following is the freeradius debugging info for one of these failed connections from a Windows 10 laptop. laptop: hp elitebook 750 g1 server: ubuntu 20.04.1 lts in aws FreeRADIUS Version 3.0.20 OpenSSL 1.1.1f 31 Mar 2020 Configured for PEAP/MSCHAPv2 Does anyone have insight into what might be wrong? I'm not sure how to interpret the error message in the debug output. ... debug output removed, see previous email ...