Re: AD 2003 - Time Services

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Doug Frisk (PublicNews_at_removeme.fazwak.com)
Date: 02/09/05

  • Next message: Phillip Renouf: "Re: cross domain group" 
    Date: Wed, 9 Feb 2005 15:34:01 -0600

    "ptwilliams" <ptw2001@hotmail.com> wrote in message
    news:Oke$xzuDFHA.392@TK2MSFTNGP14.phx.gbl...
    > You shouldn't have run the /setsntp command on anything other than the
    > PDCe.
    > All other domain members are set, by default, to use Nt5Ds -which means
    > the
    > domain hierarchy. You'll need to undo this on the other DCs.
    >
    > I can't remember if /setsntp: <nothing> will reset things (probably not).
    > So you'll need to drill down to HKLM\ SYSTEM\ CurrentControlSet\ Services\
    > W32Time\ Parameters and edit the Type REG_SZ to be Nt5Ds (I'm going from
    > memory here, but I think this is right) and delete the NtpServer REG_SZ
    > value.
    >
    > Try something like "windows time" | w32time site:support.microsoft.com in
    > google. There's an article that covers all registry values.
    >
    > You can also enable success logging, as by default it only logs errors and
    > warnings to the event log.

    Given he's going to tick or tock, it's unlikely that he's synching from a
    low accuracy time source.

    It sounds like there's a very bad clock skew on his current PDC emulator.
    I've occasionally seen boxes lose time when they're constantly running at
    100% CPU.

  • Next message: Phillip Renouf: "Re: cross domain group"