Hi Cary
Client32 is not running on any W2K Servers within the Datacentre. The PDC's in
the child and parent Domain are holding the W2K PDC FSMO roles. The DC that jumps out
of sync is placed within a Site with 6 other DCs (each sync correctly) - one of which is the
child Domains W2K PDC Emulator.
Unfortunately when the time jumps forward System Event ID 593 doesn't get logged, so to identify
when the time changes the servers time is written to a file every minute. I have started to
compare the time at which the time jumps with Events in the Security Log and I've noticed
Directory Replication taking place - this would explain the random factor (ie not every 45 minutes
or 8 hours) and the frequency with which the time moves forward. All the other replication partners
sync time properly with the W2K root PDC, either directly or indirectly.
At the moment I have the luxury of removing Inbound Replication to this DC(which I've just done)
- if the time maintains its setting, I'll be a little closer to understanding this problem and I'll
append to this posting to let you know how it goes.
I have contemplated unregistering and re-registering the time service to return it to its default
values - do you know of any downside to doing this?
Thanks for you comments.
Joe
----- Cary Shultz [A.D. MVP] wrote: -----
Joe,
Just a question as I am experiencing something similar - only it is slow,
not fast: Do you have any Novell Servers in your environment? Does the DC
that is jumping ahead have the Novell Client32 installed on it? While the
DCs that are 'in sync' do not have the Novell Client32 installed on them?
Just a thought but it probably does not apply!
By 'PDC' I assume that you mean the WIN2000 Domain Controller that holds the
FSMO Role of PDC Emulator. In the Parent Domain that DC is the
authoritative time server for the entire forest ( Windows based ). All DCs
in the Parent Domain will sync with that DC. Each workstation or member
server in the Parent Domain will sync synch the DC that authenticates it.
In the Child Domain it is a bit more interesting. For each Child Domain the
DC that holds the role of PDC Emulator can synch with -EITHER- the DC that
holds the FSMO Role of PDC Emulator from the Parent Domain -OR- synch with
any other DC in the Parent Domain. Something similar can be said for the
other DCs in each Child Domain: it can either synch with the DC that holds
the FSMO Role of PDC Emulator in its domain or it can synch with any DC in
its Parent Domain. Naturally each workstation and member server synchs with
the DC that authenticates it.
This is just a little synopsis of how things work. I am sure that you knew
this already but just to make sure...
Do you have multiple Sites? I ask because the 'AvoidTimeSyncOnWan set to 1'
entry is usually used to prevent synchronization with DCs in another Site?
What are the settings in
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W32Time\Parameters on
each DC?
There should be a 'period' and 'type' entry amongst a couple of others. Adj
and msSkewPerDay should not be modified.
HTH,
Cary
Joe said:
The PDC in the root Domain and the W2K PDC in the child domain are in
Sync, however a DC in the child Domain's PDC site continually resets its
clocks 4 minutes 40 Seconds ahead of the PDC. Running w32tm /v Syncs the DC
with the PDC emulator, but this sync lasts for a period of several hours
before the time moves out of sync again. Not the CMOS.
