Skip to content
SecuritykerberosRequires audit policy

Windows Event ID 4771: Kerberos pre-authentication failed

Event 4771 is logged on domain controllers when Kerberos pre-authentication fails, most often because of a wrong password (Status 0x18).

Overview

Event ID
4771
Log / channel
Security
Provider
Microsoft-Windows-Security-Auditing
Category
kerberos
Enabled by default
No
How to enable
Advanced Audit Policy Configuration > Account Logon > Audit Kerberos Authentication Service (Failure). Only meaningful on domain controllers.

What event 4771 logs

Event 4771 is the domain controller's record of a failed Kerberos logon at the pre-authentication step. The most common cause is a wrong password (0x18); others are an expired password, a disabled or locked account, or clock skew.

Because Kerberos is the default protocol in a domain, failed password attempts against domain accounts appear here rather than in 4625 on the DC. A password spray over Kerberos shows up as one IP producing 4771 for many accounts — and never touches member servers, so this event may be the only trace.

Fields

Every field recorded in event 4771, with the values that matter for investigation.

TargetUserName

Account whose pre-authentication failed.

TargetSid

SID of that account.

ServiceName

Requested service, normally krbtgt/<DOMAIN>.

TicketOptions

Ticket options (hex).

Status

Kerberos failure code.

0x18
KDC_ERR_PREAUTH_FAILED — wrong password.
0x12
KDC_ERR_CLIENT_REVOKED — account disabled, expired or locked out.
0x17
KDC_ERR_KEY_EXPIRED — password expired.
0x25
KRB_AP_ERR_SKEW — clock skew too large.
0x10
KDC_ERR_PADATA_TYPE_NOSUPP — smart card logon problem (for example missing KDC certificate).
PreAuthType

Pre-authentication type attempted (2 = password, 15/16 = smart card or certificate).

IpAddress

Client IP address.

IpPort

Client source port.

How to enable this event

Advanced Audit Policy Configuration > Account Logon > Audit Kerberos Authentication Service (Failure). Only meaningful on domain controllers.

Detection and investigation

Typically benign

  • Users typing a wrong password; devices with a cached old password after a change.
  • Services or scheduled tasks still configured with an old password — repeated failures on a fixed schedule.
  • Clock problems on a client (0x25).

Worth investigating

  • Password spraying over Kerberos — one source, many accounts, Status 0x18, often a few attempts per account to stay under the lockout threshold (Kerbrute, Rubeus).
  • Password guessing against a single account, usually ending in 4740 lockout.

Investigation notes

  • Count distinct TargetUserName per IpAddress in short windows to separate spraying from user error.
  • Check for a 4768 with Status 0x0 for the same accounts and IP after the failures.
  • Map IpAddress to a host; failures from servers usually mean a misconfigured service account.
  • Correlate with 4740 on the PDC emulator for accounts that were locked.

MITRE ATT&CK techniques

Related event IDs

References