![]() This issue looks to be Windows Server 2022 using LE certificates for NPS Policies.Īny information would be greatly appreciated. Accepting certificate connected to the WiFi connection. Connecting to the AP correctly provided the self signed certificate for acceptance as trusted. Windows Server 2022 - NPS - Created a self signed certificate, assigned Certificate to NPS Policy for AP using PEAP. What I have done to verify AP has connectivity to NPS: Connecting to the AP correctly provided the Certificate for acceptance as trusted. Windows Server 2012R2 - NPS - Policy for AP using PEAP assigned the LE certificate. What I have done to prove the certificate is ok: ![]() ![]() WiFi connection continuously spins and eventually faults out. NPS Policies using PEAP assigned the LE certificate initially connect, but do not provide the certificate to the device for acceptance. ![]() Certificate generated with posh-ACME ( Powershell script )Ĭertificate shows as valid, and ISRG Root X1 is in the Trusted Root Certification Authorities.Ĭonfirmed the Certificate's chain is valid and is using X1 instead of X3. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |