APPENDIX B Kerberos AS_REQ, TGS_REQ, and AP_REQ Messages Result Codes
The Kerberos
field exists in security event 4768. In events 4771 and 4769 it is a named Result Code
. It represents a hexadecimal error code.Failure Code
Table B-1 contains information about possible Kerberos error codes. This information is taken from multiple Kerberos-related RFCs.
Table B-1: Kerberos Error Codes
CODE | CODE NAME | DESCRIPTION |
|
|
No errors. Status OK. |
|
|
Client's entry in KDC database has expired. |
|
|
Server's entry in KDC database has expired. |
|
|
Requested Kerberos version number not supported. |
|
|
Client's key encrypted in old master key. |
|
|
Server's key encrypted in old master key. |
|
|
The account name doesn't exist. |
|
|
This error can occur if the domain controller cannot find the server's name in Active Directory. This error is similar to except that it occurs when the server name cannot be found. |
|
|
This error occurs if duplicate principal names exist. |
|
|
No master key was found for client or server. |
|
|
This error can occur if a client requests postdating of a Kerberos ticket. Postdating is the act of requesting that a ticket's start time be set into the future.
It also can occur if there ... |
Get Windows Security Monitoring now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.