Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a DC server that runs a network of about 20 computers. This is also the DC and pushes out the time to all the client computers.

However the time on the server is 10 minutes fast and is causing problems with some syncing applications. So far I have tried the regfix from MS:

Next I tried to set an external server for time as per this technote:

I updated the /manualpeerlist but whenever I run w32tm /resync it fetches the time but its always 10minutes too fast.

I'm stuck for ideas on how to debug this further.

share|improve this question
Are the internal clients and the DC the same (ie. all are 10min fast according to the "external source") or are you saying the DC is 10min ahead of the 20 internal clients? – TheCleaner Feb 20 '13 at 19:00
So you've synced your server to an external NTP source and all the client machines think it's 10 minutes fast? The real question is: Where are those client machines getting their time from, and why is that 10 minutes slow? – Sammitch Feb 20 '13 at 19:30
The DC is ten minutes fast and this gets pushed to all the clients. If I manually change the time on server or clients it will stick for about 15minutes and then it changes (presumably when it syncs to NTP) to 10mins fast. – Alex Feb 21 '13 at 12:58
When the DC syncs with the NTP, it updates exactly 10minutes ahead of the actual time – Alex Feb 21 '13 at 12:58
@Sammitch - that's why I asked the question in the comment. This isn't what's happening. – TheCleaner Feb 21 '13 at 16:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.