Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


Time Synchronization Issues

Posted on 2012-03-19
Medium Priority
Last Modified: 2013-01-24
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)
Question by:silver1386
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
LVL 57

Accepted Solution

Mike Kline earned 2000 total points
ID: 37738325
So it sounds like your PDCe in the forest root is not getting time from a reliable source (that is step 1)

Look at Matt's great blog entry   http://tigermatt.wordpress.com/2009/08/01/windows-time-for-active-directory/

Ace has an even more in-depth blog   https://msmvps.com/blogs/acefekay/archive/2009/09/18/configuring-the-windows-time-service-for-windows-server.aspx

Your PDCe will sync and then the rest should use the AD hiearchy.  Read those blogs first and let us know what questions you have.


LVL 30

Expert Comment

ID: 37738341
are you using an external time source like pool.ntp.org it all the errors point to the fact you are and its being blocked by a firewall or something then it will get the clock from the server system board that can be 8 minutes out and send it round the network please confirm
LVL 57

Expert Comment

by:Mike Kline
ID: 37738696
admodify is also a nice tool http://admodify.codeplex.com/

Author Comment

ID: 37739161
From what I'm seeing, it looks like my PDCe is not pointing to an external source.  Should I use the instructions here (http://support.microsoft.com/kb/816042) under "Configuring the time service to use an external time source" to set it up?  The guy in the article (http://tigermatt.wordpress.com/2009/08/01/windows-time-for-active-directory/) says to use a script to automate it (w32tm /config /manualpeerlist:”uk.pool.ntp.org,0×8 europe.pool.ntp.org,0×8¿ /syncfromflags:MANUAL /reliable:yes /update).  But I'm not sure if they're doing the same thing.  Even if they did, I'm not sure which address I use.  If I look at my secondary DC, it has an NtpServer entry of time.windows.com,0x9.  The PDCe had it as well, until I did the reset that the article recommended; now it does not have an NtpServer entry.

So which method is the right one to use, and what address do I use?  Does it matter if I'm running Server 2008 R2?

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This process allows computer passwords to be managed and secured without using LAPS. This is an improvement on an existing process, enhanced to store password encrypted, instead of clear-text files within SQL
Let's recap what we learned from yesterday's Skyport Systems webinar.
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…
Suggested Courses

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question