"Chris Burgess" wrote:

> Hi,
>
> I have a W2K3 Std server in a domain with a W2k server as a PDC. The W2K3
> server holds all of the FSMO roles
>
> Just recently we noticed the time on the network was always 10-12 minuties
> slow.
>
> After changing the time on both servers back to the real time several times,
> I then reconfigured time settings of both servers, the W2K server looks to
> the W2K3 server for time.
>
> The W2K3 server has been set to pickup time from tock.usno.navy.mil and
> tick.usno.navy.mil every 15 minutes.
>
> Now the time appears to be staying syncronized most of the time, but about
> twice a day it slips back by 10-12 minutes, then is corrected the next time
> it syncs with tock.usno.navy.mil.
>
> Any ideas as to where I should be looking?

"Chris Burgess" <ChrisBurg***@discussions.microsoft.com> wrote in message
news:98894979-9132-45B5-88F1-4A5C31B588CA@microsoft.com...
> Hi,
>
> I have a W2K3 Std server in a domain with a W2k server as a PDC. The W2K3
> server holds all of the FSMO roles
>
> Just recently we noticed the time on the network was always 10-12 minuties
> slow.
>
> After changing the time on both servers back to the real time several
> times,
> I then reconfigured time settings of both servers, the W2K server looks to
> the W2K3 server for time.
>
> The W2K3 server has been set to pickup time from tock.usno.navy.mil and
> tick.usno.navy.mil every 15 minutes.
>
> Now the time appears to be staying syncronized most of the time, but about
> twice a day it slips back by 10-12 minutes, then is corrected the next
> time
> it syncs with tock.usno.navy.mil.
>
> Any ideas as to where I should be looking?

"Cary Shultz" wrote:

> Chriss,
>
> Your terminology is a bit off (er, I think).  I think that you mean that you
> have a Windows Server 2003 Domain Controller with an additional Domain
> Controller (the WIN2000 box).  If the WIN2003 Domain Controller holds all of
> the FSMO Roles then it would be the 'PDCe' - Primary Domain Controller
> Emulator.  However, there is no more PDC/BDC in Active Directory.  This is
> more of a WINNT term.  Now, this is not exactly correct.  But mostly.
>
> This specific FSMO Role holds a lot of extra responsibilities.  Among other
> things, it is the Time Source.  More specifically, the Domain Controller for
> the Forest Root Domain is the Time Source Master.  But it seems that you
> have this as the WIN2003 Domain Controller is the one on which you have
> configured tick and tock.
>
> Do you have a pure Windows environment?  I have seen this exact problem in
> environments that were originally Novel Netware.  The Netware client is
> installed on a lot of systems and this seems to cause problems.
>
> And, beware that you will have Kerberos problems if you stay more than 5
> minutes out of time (this is the default).
>
> Does this help?
>
> --
> Cary W. Shultz
> Roanoke, VA  24012
> "Chris Burgess" <ChrisBurg***@discussions.microsoft.com> wrote in message
> news:98894979-9132-45B5-88F1-4A5C31B588CA@microsoft.com...
> > Hi,
> >
> > I have a W2K3 Std server in a domain with a W2k server as a PDC. The W2K3
> > server holds all of the FSMO roles
> >
> > Just recently we noticed the time on the network was always 10-12 minuties
> > slow.
> >
> > After changing the time on both servers back to the real time several
> > times,
> > I then reconfigured time settings of both servers, the W2K server looks to
> > the W2K3 server for time.
> >
> > The W2K3 server has been set to pickup time from tock.usno.navy.mil and
> > tick.usno.navy.mil every 15 minutes.
> >
> > Now the time appears to be staying syncronized most of the time, but about
> > twice a day it slips back by 10-12 minutes, then is corrected the next
> > time
> > it syncs with tock.usno.navy.mil.
> >
> > Any ideas as to where I should be looking?
>
>
>