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 an offset >1000 sec. You can certainly do it with the old date, time, or net time. It must have been a really interesting case you had with PSS.. Yes, it was a very educational call. Learned a lot about resetting secure channels, resetting Kerberos tickets and klist. One point was that the PDCE "saw" the time difference was so large and killed the secure channel between it and all other DCs to keep from getting itself "hurt". Once it did that, the DCs on the left coast could no longer authenticate. The right coast users only had the PDCE DC to work with so they had no issues. Webster ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
