Technical Tip: FortiNAC Dot1x EAP-PEAP-MSCHAPv2 Authentication fail with error 'Credentials Invalid (MSCHAP2)'
| Description | This article describes how to address the dot1x EAP-PEAP-MSCHAPv2 Authentication failure with error 'Credentials Invalid (MSCHAP2)'. |
| Scope | FortiNAC, Windows 11 22H2. |
| Solution | In Windows 11 22H2 and above, Considerations and known issues when using Credential Guard feature were introduced, leading to EAP-PEAP-MSCHAPv2 authentication to fail with the following error returned by Active Directory to FortiNAC in the RADIUS logs: (11564) mschap-WININD: Creating challenge hash with username: hawada1
rlm_rest (rest_reject): Connecting to "http://127.0.0.1:8081/api/v2/radius"
To overcome this behavior, Disable Credential Guard on the Windows 11 machine or switch to EAP-TLS.
mountvol X: /s copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi" bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215} bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X: mountvol X: /d
Related article: Technical Tip: FortiNAC RADIUS debug errors and solutions |
