Windows Domain time services
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,0x
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!
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,0x
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!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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!
ASKER
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.
You can do the same commands you would on your primary DC on this member server
ASKER
Which commands would force this member server to look for an outside time source?
Same instructions for Windows 2003 server as XP
ASKER
Alright, I configured the member server to sync with a public NTP source. Will the domain automatically change this back for any reason?
ASKER
Thanks