Active Directory Kerberos Logons Fail Because a Member Server Clock Is Skewed
Overview
Diagnose Kerberos authentication failures caused by clock skew on a Windows member server and safely restore time synchronization before validating logons.
Destructive operation
This intervention contains destructive operations. Proceed with extreme caution and ensure database backups exist before execution.
Diagnose
Symptom
What responders observe.
Kerberos-authenticated logons or service connections fail from one Windows member server while the same accounts continue to work from other domain-joined hosts.
Detection
Metrics, logs and confirmation commands.
-
On the affected server, run
w32tm /query /statusand record the source, stratum, last successful synchronization time, and phase offset. -
Run
w32tm /stripchart /computer:<DC_FQDN> /samples:5 /dataonlyand compare the member server with a reachable domain controller. -
Run
klistand record the Kerberos ticket cache and any ticket errors. -
Run
nltest /sc_verify:<AD_DOMAIN>to verify the secure channel without changing it. -
Review the System event log for Time-Service events and the Security/System logs for Kerberos errors at the incident time.
Commands in these steps
w32tm /query /statusw32tm /stripchart /computer:<DC_FQDN> /samples:5 /dataonlyklistnltest /sc_verify:<AD_DOMAIN>
Root cause
Why the incident occurred.
-
The affected member server's clock has drifted beyond the Kerberos tolerance or it is using an incorrect time source.
-
Kerberos relies on bounded clock skew to resist replay attacks, so otherwise-valid tickets can be rejected while the time difference persists.
Contain and prevent
Blast radius
What else this can affect.
Kerberos authentication from the skewed member server can fail for users and services.
NTLM fallback may mask the incident for some applications while weakening the expected authentication path.
If the incorrect time source affects multiple domain members or a domain controller, the authentication impact can expand beyond one host.
Prevention
Controls and guardrails that stop it recurring.
-
Monitor Windows Time Service synchronization state and offset on domain members and domain controllers.
-
Keep the forest-root PDC emulator synchronized to an approved reliable external source and preserve the domain time hierarchy for other domain members.
-
Alert on repeated Time-Service errors and clock offsets approaching the organization's Kerberos tolerance.
Fix
Pre-flight checks
Check these before you change anything.
-
Confirm the affected host is the intended member server and not the forest-root PDC emulator; stop and escalate if the PDC emulator is affected.
-
Run
whoami /groupsand confirm the session has the local administrator rights required to manage Windows Time Service. -
Record
w32tm /query /configuration,w32tm /query /status,w32tm /query /source, and the current system time. -
Confirm DNS resolves the intended domain controller and
nltest /dsgetdc:<AD_DOMAIN>returns the approved site-local controller. -
Confirm the server has network reachability to that controller and that no approved maintenance is changing time configuration.
-
Windows Time Service has no true dry-run for resynchronization. Immediately before the change, use
w32tm /stripchart /computer:<DOMAIN_CONTROLLER> /samples:5 /dataonlyas the equivalent impact preview; record all five samples and abort if the source is unexpected, any sample is unavailable, or the largest absolute offset exceeds the application owner's written<MAX_APPROVED_OFFSET>. -
Treat starting Windows Time Service if stopped, resynchronizing the clock, and purging only the current operator's ticket cache as explicit mutations. Do not restart an already-running service.
-
Obtain incident commander and application-owner approval for the measured offset before resynchronizing a latency-sensitive or transaction-processing host.
Commands in these steps
whoami /groupsw32tm /query /configurationw32tm /query /statusw32tm /query /sourcenltest /dsgetdc:<AD_DOMAIN>w32tm /stripchart /computer:<DOMAIN_CONTROLLER> /samples:5 /dataonly
Commands
w32tm /stripchart /computer:<DOMAIN_CONTROLLER> /samples:5 /dataonly; if ($LASTEXITCODE -ne 0) { throw 'Offset preview failed; aborting before mutation' }; if ((Get-Service -Name w32time).Status -ne 'Running') { Start-Service -Name w32time -ErrorAction Stop }; w32tm /resync /rediscover; if ($LASTEXITCODE -ne 0) { throw 'Time resynchronization command failed' }; klist purge; w32tm /query /source; w32tm /query /status
Verify and recover
Verification
Evidence required before you close the incident.
-
Confirm
w32tm /query /statusreports a domain-hierarchy source and a recent successful synchronization. -
Repeat
w32tm /stripchart /computer:<DC_FQDN> /samples:5 /dataonlyand confirm the measured offset is within the approved Kerberos tolerance. -
Obtain a new ticket with
klist get <SERVICE_PRINCIPAL_NAME>for the interactive context. -
Separately repeat the originally failing authenticated request under the actual affected service account or application identity; do not treat the operator's ticket cache as proof for another identity.
-
Monitor Time-Service and Kerberos events for at least 15 minutes.
Commands in these steps
w32tm /query /statusw32tm /stripchart /computer:<DC_FQDN> /samples:5 /dataonlyklist get <SERVICE_PRINCIPAL_NAME>
Rollback
The safe way back.
-
A time resynchronization must not be rolled back to a known-skewed value.
-
Abort further changes if the post-resync source is not the expected domain-hierarchy source, if the measured offset still exceeds the approved threshold, or if the application reports time-ordering errors.
-
Isolate the affected application, restore only the recorded approved time-service configuration, stop further manual clock changes, and escalate to the Windows/Active Directory owner before restarting dependent workloads.
Escalate when
Conditions that need another owner.
-
The affected system is the forest-root PDC emulator or a virtualized domain controller with conflicting host time synchronization.
-
The secure channel is broken after time is corrected.
-
Multiple domain controllers disagree on time or Kerberos failures continue after new tickets are issued.
-
Resynchronization would violate a database, trading, logging, or forensic time-integrity requirement.
Fixed? Get the next one before it hits you: The KBY Brief
Practical fixes for the systems you run, by email about twice a week. Unsubscribe at any time.
About this page
Credited to
Dates
Published
Last updated
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Sources
Based on the vendor sources listed below. Check each step against your environment before acting.
First published 20 August 2026 · Last updated 9 November 2026
Windows Time service tools and settings
Cited for: Supported w32tm diagnostic and resynchronization commands and Windows domain time-service behavior.
Kerberos authentication troubleshooting guidance
Cited for: Kerberos failure diagnosis, ticket inspection, clock synchronization, and domain-controller checks.
Restart-Service
Cited for: The supported PowerShell command for stopping and starting Windows Time Service by service name.
klist
Cited for: Kerberos ticket-cache inspection, purge behavior, and requesting a ticket for a target service principal.
Start-Process
Cited for: Waiting for a native process to finish and inspecting its process object for reliable command completion handling.