troubleshooting Question

Time Synchronization Issues

Avatar of silver1386
silver1386 asked on
Active DirectoryWindows Server 2008
4 Comments1 Solution15583 ViewsLast Modified:
I had a user contact me saying that her computer clock is 8 or 9 minutes faster than her cell phone clock.  That concerned me because cell phone clocks are always synced.  I looked at my computer's clock, and it was the same, about 8 minutes ahead of my phone.  Eight minutes is a lot of time to be off.  So I looked at my two DC's.  The one that serves as the AD PDC Emulator is only 1 minute faster than my phone; that seems more reasonable.  But workstations aren't syncing with it.  So I looked at my other DC, which has none of the master roles.  It is exactly the same as the workstations, about 8 minutes fast.

So there are a couple of big problems here.  First, my DC's don't have the same time.  Second, my workstations have the same time as the faster DC (are they syncing to it?).  I looked in the error logs of both DC's and filtered for the Time-Service.  The PDC Emulator DC has Warning Event ID 144: The time service has stopped advertising as a good time source.  The other DC has Warning Event ID 142: The time service has stopped advertising as a time source because the local clock is not synchronized.  I am getting other Event ID warnings as well.  On the primary DC: Event IDs 12, 36, 144 (mentioned above), 131.  On the secondary DC: Event IDs 131, 24, 142 (mentioned above), 50, 129.  I will give more info on these at the bottom.

I am not a DC expert by any stretch.  And most of these warnings, I'm not even sure what exactly they mean.  But some of them seem pretty bad.  Could anyone shed some light on this and help me fix this?

Event ID 12: Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.

Event ID 36: The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.

Event ID 144: The time service has stopped advertising as a good time source.

Event ID 131: NtpClient was unable to set a domain peer to use as a time source because of DNS resolution error on ''. NtpClient will try again in 3473457 minutes and double the reattempt interval thereafter. The error was: The requested name is valid, but no data of the requested type was found. (0x80072AFC).

Event ID 24: Time Provider NtpClient: No valid response has been received from domain controller DC-DNS.domain.org [this is our primary DC] after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The peer is unreachable.

Event ID 142: The time service has stopped advertising as a time source because the local clock is not synchronized.

Event ID 50: The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.

Event ID 129: NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in 3145779 minutes and double the reattempt interval thereafter. The error was: The entry is not found. (0x800706E1)
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 4 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 4 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros