Re: NTDS Replication Warning

see if the following helps:
http://www.eventid.net/display.asp?eventid=1586&eventno=781&source=NTDS%20Replication&phase=1

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Cybersteve" <Cybersteve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:23D1C7EA-24DC-4B82-9C08-E2DE5CF3F3A6@xxxxxxxxxxxxxxxx
On a recently promoted Win2k DC am receiving the following warning in the
Directory Service Log:

Log: Event Type: Warning
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1586
Date: 10/18/2006
Time: 7:19:01 PM
User: Everyone
Computer: Domain controller
Description:
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.

This computer doesn't have DNS installed on it as yet, but is a GC server.
In its DNS settings, it is presently pointing at the local site DNS server
as
preferred, with the secondary DNS server being the FSMO PDC. It's been
over
10 hours since I promoted this DC on a small network. Can't figure out
whay
it won't checkpoint with the PDC, though I noticed that in the AD Sites
and
Services it does not have a replication link with the PDC, while all my
other
DCs do.
--
Endurance is more important then truth.


.

Relevant Pages

  • Re: Windows 2003 server DNS problems
    ... you would disconnect the BDC not the PDC from the network. ... > server was promoted as a PDC and the original PDC was promoted to a BDC. ... The DNS server is setup as a forwarder and is pointing ...
    (microsoft.public.windows.server.setup)
  • Re: Directory Services Restore Help!!!
    ... and we had to restore from tape. ... The DNS server was unable to complete directory service enumeration of zone ... Server) and used directory services restore. ...
    (microsoft.public.windows.server.general)
  • Re: Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
    ... an SRV pdc record for my domain.com--but I receive an error: another DNS server is managing part of this domain. ... This is odd as I do not have another DNS server installed. ...
    (microsoft.public.windows.server.general)
  • Re: Cannot locate Domain after migrate from NT to Win2K3
    ... DNS server? ... I'd like to suggest you transfer FSMO to the Windows server 2003 DC to ... To identify the PDC emulator ... 1.Open Active Directory Users and Computers ...
    (microsoft.public.windows.server.migration)
  • Re: Active Directory: Very Slow Authentication
    ... > The IP Addresses on all server is fixed with the DNS server pointing to ... > DNS server running on the domain controller only has one entry for the AD ... >> Microsoft MVP - Directory Services ...
    (microsoft.public.win2000.active_directory)