Time is not syncing correctly on DC's

Yesterday on 7/2 I noticed this timeclock issue when I went to open the Exchange Console and it gave me an error. Two of the five domain controllers were incorrect. One of the ESXi clusters had the time off by six mins on two servers and NTP was not running. I corrected the time on all of them by

net stop w32time
w32tm /unregister
w32tm /register
net start w32time
w32tm /resync /rediscover

Today 7/3 time clocks are not syncing again.  We have two ESXi clusters in two different offices. When I review the time config on all of them they show the correct time and NTP is running.  They are all set to auto adjust. I havent the slightest idea why its not syncing on our DC's
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Make sure you virtual servers are not SYNCING TIME with the hosts!

1. Sync Hosts time to External Internet Time Source.

2. Sync DC time to same source as 1.

3. Windows Domain Servers sync with domain, do not sync with Host.

4. Linux servers, sync with source as in 1.
Will SzymkowskiSenior Solution ArchitectCommented:
If you have not done so already, the link below explains how to setup an External Time Source for your PDC role holder. All other DC's should get the time source from the PDC by default unless it is specifically gettting it from the ESX host.



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
stlhostAuthor Commented:
Sorry for the late response holidays and all.. The VMs dont sync with ESXi, I checked. The PDC has the correct time on it. As of this morning all of our DCs are correct. Our workstations however are not.
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

stlhostAuthor Commented:
For now I have psexec to all system and ran w32tm /config /manualpeerlist:time.windows.com /syncfromflags:manual /reliable:yes /update. Still need to find out why our workstations didnt sync correctly
Will SzymkowskiSenior Solution ArchitectCommented:
Check the logs on the clinet machines for the ones that were not syncing correctly.

There should not be any need for additional configuration syncing clients to the Time Source. This happens by default when adding a machine to the domain.

If all machines are affected then check the logs on your domain controllers to make sure that they are advertising as a Time Source.

stlhostAuthor Commented:
So I am looking at two machines. One is a workstation the other is a workstation. Both show event ID 50 in the event logs. https://technet.microsoft.com/en-us/library/cc756549(v=ws.10).aspx

Workstation, time is correct after running psexec command

C:\Windows\system32>W32TM /query /status
Leap Indicator: 3(last minute has 61 seconds)
Stratum: 0 (unspecified)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0625000s
Root Dispersion: 10.5367571s
ReferenceId: 0x00000000 (unspecified)
Last Successful Sync Time: 7/3/2015 6:37:51 AM
Source: Free-running System Clock
Poll Interval: 10 (1024s)

Terminal Server, time is incorrect

Leap Indicator: 0(no warning)
Stratum: 3 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0682537s
Root Dispersion: 3.8361809s
ReferenceId: 0x68299644 (source IP:
Last Successful Sync Time: 7/6/2015 9:15:18 AM
Source: time.windows.com
Poll Interval: 10 (1024s)

This is just from two systems. Keep in mind almost all of our workstations and servers were effected. Looks like it started around 7/2

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.
Will SzymkowskiSenior Solution ArchitectCommented:
You need to make sure that your DC's are configured properly and they have the proper flags set in the registry. You also need to make sure that you have configured an External Time Source on your PDC role holder.

stlhostAuthor Commented:
Got it working, thanks
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.