From: Free, Bob [mailto:[EMAIL PROTECTED]
Subject: RE: DC changing time?
My point was that the time service wouldn't set the clock that far off
because of a bad source because it won't accept an offset that large. Kind
of like NTPd on a *NIX box will panic if you try to throw it
time.
It must have been a really interesting case you had with PSS
From: Webster [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 16, 2008 10:52 AM
To: NT System Admin Issues
Subject: RE: DC changing time?
From: Free, Bob [mailto:[EMAIL PROTECTED]
Subject: RE: DC changing time?
From: Free, Bob [mailto:[EMAIL PROTECTED]
Subject: RE: DC changing time?
The time service on the DC wouldn't accept an offset that big.
I worked a call back in August where the point-to-point T3 went down for 8
hrs. When the link came back 1 DC on each side of the link each changed
The time service on the DC wouldn't accept an offset that big.
From: Joseph L. Casale [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 8:15 PM
To: NT System Admin Issues
Subject: RE: DC changing time?
Bad NTP Time source?
Enumerate and check them...
From: mqcarp [m
The only time Ive ever seen this is in a vm, where it auto syncs with the
host.
Outside of that someone accidentally changed it?
-Original Message-
From: Kurt Buff [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2008 19:16
To: NT System Admin Issues
Subject: Re: DC changing time
nt: 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
&g
me 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 exac
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
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
