| Previous | Next |
| SEC_E_UNFINISHED_CONTEXT_DELETED | SEC_E_NO_IP_ADDRESSES |
SEC_E_NO_TGT_REPLY
SEC_E_NO_TGT_REPLY signals this condition: A user-to-user Kerberos negotiation expected a TGT reply but did not receive one. This is a specialized Kerberos scenario. The client attempted a user-to-user connection, but the peer did not provide the ticket-granting-ticket information required to complete that form of negotiation.
What to check
- Confirm that the application intentionally uses user-to-user Kerberos and that both endpoints support it.
- Review KDC and client events for the target principal and ticket request.
- Validate the application authentication design before changing general Kerberos policy.
Microsoft: Kerberos authentication troubleshooting
Looking for a different code? Search another status or error code.