Forum Discussion
PaulvDam
Oct 08, 2021Copper Contributor
Windows 11 clients cannot authenticate to NPS server using computer authentication
We have a Windows server 2019 datacenter server running NPS. Our WiFi Office clients authenticate to this server for access to the corporate WiFi network. We use computer authentication, so members o...
- Oct 18, 2021Had this with 802.1x and AlwaysOn VPN. Maybe it's the same for your Wifi profile,. The reason is documented here https://directaccess.richardhicks.com/2021/09/23/always-on-vpn-error-853-on-windows-11/
ERose_VT
Feb 09, 2022Copper Contributor
We had the case mismatch between the server name listed in the PEAP properties, and the Subject Alternate Name on the server cert. PEAP properties is in the group policy, and SAN is on the NPS server. So, open certificates snap-in on the NPS server, open the server cert, and check the SAN. The PEAP properties (drill down, edit the profile, security tab, properties, "Connect to these servers:") have to match the exact case as shown on the SAN. This article has 3 likes. Soon it will have hundreds, as enterprises start to roll out Windows 11.