Checkpoint with PDC Unsuccessful

[MIke C.]

I keep getting the following Warning in my Windows 2000
Server Directory Services Event Log:

Event ID: 1586
The checkpoint with the PDC was unsuccessful. The
checkpointing process will be retried again in four hours.
A full synchronization of the security database to
downlevel domain controllers may take place if this
machine is promoted to be the PDC before the next
successful checkpoint. The error returned was: The naming
context is in the process of being removed or is not
replicated from the specified server.

The server is a domain controller - but this is the only
DC that is giving me this message (the other 20 are okay).
I've compared network settings with other servers, DNS
appears to be okay (no name resolution problems). Is there
anything else that I can check for to fix this problem?

 

[Guest]

The reason this is the only DC you are seeing this message on is because it is the only one holding the FSMO PDC Emulator Role. You are receiving this message because that system is unable to communicate with a down-level NT4 BDC. For further information see:

http://support.microsoft.com/default.aspx?scid=kb;en-us;269417

If there are no NT4 Domain Controllers, and you do not plan to ever have NT4 Domain controllers in your Domain, investigate changing to Native Mode. This should be a planned and tested operation as it can not be switched back.

See:
http://support.microsoft.com/default.aspx?scid=kb;en-us;186153

Ian Bagnald
MCSE:Security W2K
MCSA:Security W2K
COMPTIA A+

 

[Mikey]

Actually, the FSMO PDC Emulator Role is on a completely
different server on the same subnet as this one - which is
why the error message confused me. It has no problem
pinging or seeing the server that is the PDC Emulator as
far as I can tell. I don't forsee ever having Windows NT 4
domain controllers in this domain, but I would rather wait
until we upgrade to Windows Server 2003 to start changing
roles. Is there anything else I can check?

-----Original Message-----
The reason this is the only DC you are seeing this

message on is because it is the only one holding the FSMO
PDC Emulator Role. You are receiving this message because
that system is unable to communicate with a down-level NT4
BDC. For further information see:

http://support.microsoft.com/default.aspx?scid=kb;en- us;269417

If there are no NT4 Domain Controllers, and you do not

plan to ever have NT4 Domain controllers in your Domain,
investigate changing to Native Mode. This should be a
planned and tested operation as it can not be switched
back.

 

[Guest]

Try creating a manual connection object between the server that is recieving the error and the PDC Emulator.

Ian Bagnald