• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Server 2003 time issues

Monkey God

Mangina Full of Sand
Joined
May 7, 2007
Messages
6,723
So, question about windows time service. Server 2003 Active directory. Large number of servers. Both domain controllers have the proper time. For this example lets say 9:00AM.

Other servers in the domain (also server 2003) - are all showing 9:06AM which breaks Kerberos among other things. All other servers point to DC....restarting the w32 service makes the time correct...then 20-30 seconds later, it jumps forward 6 minutes. No group policies in place with regards to the service. What else can set system time that overrides w32time?
 
Just to be clear, are you talking physical or virtual servers?

I've seen lots of instances like this with virtual servers where the host server had different time than the guest VMs and the virtualization additions would override the guest OS clocks with the time for the host OS clock after the guests had sync'd properly.

The fix in that case is either to disable the resync with the host OS clock, or make sure the host OS clock is also pulling its time sync data from one of the DCs.
 
AH yes a good point. These servers are virtual on vmware...
I bet thats it!
 
Back
Top