Why does Server 2003 clock run 4 minutes slow?

Recently I have noticed that the clock on our domain server insists on running 4 minutes slow.  I reset it in Control Panel and within a few minutes (sometimes as little as 1 minute) it switches back to 4 minutes slow.  I have also received complaints from some of my 35 users on the network that the same thing is happening to their desktop PCs running Windows XP Pro.
DaleCarlsAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
murgroupConnect With a Mentor Commented:
You need to be syncing it with an external time server. you will note that the below example is using a pool of ntp servers. I was not able to get that to work so I only use one. Also you can do a search for time server IP's or names on google ie. time.windows.com or time.nist.gov. Hope this helps.

w32tm /config /manualpeerlist:0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org pool.ntp.org,0×8 /syncfromflags:MANUAL /reliable:yes
w32tm /config /update
net stop w32time
net start w32time
w32tm /resync /rediscover
That should do it. However, always make sure you firewall is open to port 123 outbound!  I initially was receiving this error after running a w32tm /resync :
0
 
MightySWCommented:
Yes, this also HAS to be done on the domain controller that holds the PDC emulator operations role.  You can find this out by opening up Active directory users and computers, Right click on ADUC at the top, select all tasks and select operations masters.  You will see the PDCe listed under the PDC tab.

If you only have one domain controller then I guess this is moot.

HTH
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.