We help IT Professionals succeed at work.

Windows Domain time services

Info Tech
Info Tech used Ask the Experts™
on
I am having some major issues with my times jumping around on Sunday nights.  A member server always registers the Source W32Time Event ID 50.  "The time difference greater than 5000 milliseconds for 900 seconds...."  You know the rest.  

I have a 2008 server that holds all the FSMO roles.  That server sycronizes time with an outside time server, right now, I have it set to point to "nist1-chi.ustiming.org,0x1".  

All other server are supposed to sync with this server for their time source.  

Now, I have another domain controller that is a Server 2003 box.  It seems that is most often the authenticating server, so most of my workstations sync with that, and that should sync with my main domain server.  

I am lost as to why I keep getting time issues, and my clocks are jumping around as much as ten minutes.  I have read article upon article both on here and searching google.  I have everything set as suggested, but for some reason just Sunday nights this thing jumps around.  It throws off our time clocks, which then throws HR in a loop!  Then they come to me, you know the rest :

Any help would be greatly appreciated!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2012
Commented:
On the Windows 2003 Server run this command

http://technet.microsoft.com/en-us/library/cc758905(WS.10).aspx

If the Windows 2003 server at some point was the FSMO role holder it is most likely configured with external time source. Sometimes you need to run above command to remove external time source setting and get the server to get time from FSMO role holder.

Once you do above run w32tm /resync /rediscover

If you are having issues with some other systems go through the link with them as well
Info TechIT Department

Author

Commented:
OK, I ran those commands on the member server, and the old DC that used to hold the FSMO roles. We will see what happens.  It seems to only happen on Sunday nights so I may not get back to this thread for a couple days.  I beleive I ran those commands before, but I don't want to rule anything out at this point.  If there are any other suggestions please put them out there.

Thanks
Info TechIT Department

Author

Commented:
Well the problem happened again on the same servers.  I don't get what it is that it only happens Sunday nights.  Really hoping someone can help out here!
Info TechIT Department

Author

Commented:
Another solution that may help me here.  Is there any way to force a member server to sync time with an outside source and just ignore the domain time all together?  The particular server I am having so many issues with is our timeclock server, therefore when it jumps time, it really messes up the punches in the system.  
Top Expert 2012

Commented:
You can do the same commands you would on your primary DC on this member server
Info TechIT Department

Author

Commented:
Which commands would force this member server to look for an outside time source?
Top Expert 2012

Commented:
Same instructions for Windows 2003 server as XP
Info TechIT Department

Author

Commented:
Alright, I configured the member server to sync with a public NTP source.  Will the domain automatically change this back for any reason?
Top Expert 2012

Commented:
No