wpa2-8021x

when setting up the radius server, it returns the below error, i've enabled MSCHAPv2/MSCHAP/PAP still not work. OS: WIN2022

The client could not be authenticated  because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server.

Hello,

Root Cause
The EAP authentication types (such as PEAP-MSCHAPv2, EAP-TLS, etc.) sent by the client are not supported or configured by the server.
This commonly occurs in enterprise wireless networks when the EAP type selected by the terminal device (e.g., iPhone) does not match the configuration of the RADIUS server.
Typical Scenarios
The client is configured to use PEAP-MSCHAPv2 (i.e., WPA/WPA2 enterprise-level authentication), but the server only supports EAP-TLS or other EAP subtypes.
The server may not have enabled the EAP protocol required by the client (e.g., Microsoft’s MS-PEAP).
Solutions
Check Server Configuration: Verify whether the list of EAP types supported by the RADIUS server includes the type requested by the client.
Unify Authentication Protocols: Enforce the use of the same EAP subtype on both the client and server sides (e.g., unify to PEAPv0-MSCHAPv2).
Log Troubleshooting: Use device logs (such as %DOT1X-5-FAIL) to locate the specific MAC address and port of the failure, and verify the protocol compatibility between the two ends.
Compatibility Notes
Mainstream terminals (such as Android/iOS) natively support PEAP-MSCHAPv2, but ensure the server also enables this protocol.
Special systems (such as Windows XP) may require manual configuration or auxiliary tools (such as Ruijie WIFI Assistant) to complete parameter synchronization.

For further troubleshooting, it is recommended to provide the specific device model, device firmware version and server log to analyze the protocol interaction details.

Best regards,
Micca