You have an atomic clock at work? How cool is that! On Wed, Oct 15, 2008 at 4:05 PM, mqcarp <[EMAIL PROTECTED]> wrote: > No that was not it. The source is the atomic clock. It is almost like it was > physically changed by one day. I do not see that something like that would > be logged in the event log if it occurred. > > On Tue, Oct 14, 2008 at 10:15 PM, Joseph L. Casale > <[EMAIL PROTECTED]> wrote: >> >> Bad NTP Time source? >> Enumerate and check them… >> >> >> >> From: mqcarp [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, October 14, 2008 9:14 PM >> To: NT System Admin Issues >> Subject: DC changing time? >> >> >> >> We had a weird issue where apparently a DC rolled back exactly one day in >> time (6:30PM Monday became 6:30PM Sunday). This wreaked havoc on policy >> issues. All I can see in the event logs is the change in policy where it was >> denying log ins all of a sudden. The DC time was updated and we are back on >> track but I can not see what would cause something like this. No one was at >> the office in IT when this occurred. The only thing odd was an admin had >> left himself logged into the server at the end of the day. Has anyone seen >> this before? >> >> AD 2003 2003 Server Standard >> >> >> >> >> >> >> >> > > > >
~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
