Link to home
Start Free TrialLog in
Avatar of cfischer225
cfischer225Flag for United States of America

asked on

windows server 2003 clock fast by 5 minutes resulting in all clients clocks fast

i have a windows server 2003 DC and an exchange server that acts as a backup Dc, the clokc on my DC is 5 min fats and when all the clients sync they are 5 minutes fast, if i change the clock on the clients or the Dc it eventually goes back when it syncs wherever it synce to. how do i fix this?
Avatar of ryansoto
ryansoto
Flag of United States of America image

Avatar of cfischer225

ASKER

i followed the instructions to configure itself form the internal clock, is that what i want or should i configure it to an external source?
ASKER CERTIFIED SOLUTION
Avatar of ryansoto
ryansoto
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
can you please provide more details on how to set the group policy, i configured the time to synce with an external source already
i did it, thanks i'll let you know if it worked
Avatar of Darius Ghassem
You can import this reg file on your PDC to set the time sync settings automatically.

https://www.experts-exchange.com/questions/23630502/Authoritative-Time-Server.html
now how do i know if the change worked, how long till my clients see the new time?
You can run the w32tm /rsync /rediscover on a client which will sync to the PDC right then. The changes will work. I haven't had one time when the reg didn't sync correctly.
On one of your clients you can go into the event viewer and look under the system option - you should see an entry with w32 time as the header and in the body it will show synchronizing from server....
I did all of these things and when I ran the rediscover command on the client I got "The computer did not resync because no time data was available".
I had to make sure I put my internal computer name correctly in the NTP field:  servername.localdomainname.local

That worked. Just thought this might help someone else.