| Previous | Next |
| SEC_E_MUST_BE_KDC | SEC_E_TOO_MANY_PRINCIPALS |
SEC_E_STRONG_CRYPTO_NOT_SUPPORTED
SEC_E_STRONG_CRYPTO_NOT_SUPPORTED signals this condition: The remote side requires stronger cryptography than the local computer can use for the negotiation. The client and server do not share a compatible cryptographic capability for the required security context. The correct response is to determine the expected encryption types and update supported components, not to weaken the target security requirement without review.
What to check
- Identify the negotiated protocol and the encryption types or algorithms requested by the target.
- Check Kerberos and system events on both client and domain controller for the rejected capability.
- Bring the older component or policy into a supported configuration while preserving the required protection level.
Microsoft: Kerberos authentication troubleshooting
Looking for a different code? Search another status or error code.