CV0-003 · Question #30
After deploying new VMs, the systems administrator notices it is not possible to connect to them using network credentials; however, local accounts work. After logging in, the administrator notices…
The correct answer is D. There is a time synchronization issue. Kerberos authentication, used by Active Directory for network logins, requires clock skew between client and domain controller to be within 5 minutes. Without NTP configured on the new VMs, time drift causes Kerberos to reject authentication tickets while local accounts remain…
Question
After deploying new VMs, the systems administrator notices it is not possible to connect to them using network credentials; however, local accounts work. After logging in, the administrator notices the NTP servers are not set. Which of the following is MOST likely causing this issue?
Options
- ADirectory services requires the use of NTP servers.
- BThe VMs are insufficiently licensed.
- CThere is a directory services outage.
- DThere is a time synchronization issue.
How the community answered
(36 responses)- A8% (3)
- B3% (1)
- C11% (4)
- D78% (28)
Why each option
Kerberos authentication, used by Active Directory for network logins, requires clock skew between client and domain controller to be within 5 minutes. Without NTP configured on the new VMs, time drift causes Kerberos to reject authentication tickets while local accounts remain unaffected.
This restates a dependency rather than identifying a cause - it describes what directory services needs rather than naming the resulting failure condition of time being out of sync.
Licensing issues would not selectively block network credential authentication while allowing local account logins to succeed simultaneously.
A directory services outage would prevent all domain authentication from reaching controllers, but the specific clue of missing NTP servers points to a time synchronization failure rather than a service-level outage.
Kerberos, the authentication protocol underlying Active Directory network logins, enforces a maximum clock skew of 5 minutes between a client and the domain controller. New VMs without NTP configured have no authoritative time reference and will drift past this threshold, causing Kerberos ticket validation to fail - which blocks network credential logins while local accounts, which do not rely on Kerberos, continue to work.
Concept tested: Kerberos clock skew requirement for Active Directory authentication
Source: https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/kerberos-authentication-problems-if-not-synchronized
Topics
Community Discussion
No community discussion yet for this question.