replicating error

[Guest]

HI

I had only one domain controller (1 site) and then i added 2 new domain
controllers during the time when i had only one every thing was going
smoothly and good with no problems at all.

after i promoted this 2 servers to domain controllers the errors started to
come up.

domain name is: keponline, everything is based on win2k server


errors are as follow

Event Type: Warning
Event Source: NTDS Replication
Event Category: (5)
Event ID: 1586
Date: 8/30/2004
Time: 2:09:41 PM
User: Everyone
Computer: KEP-FILES
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.



Event Type: Warning
Event Source: NTDS KCC
Event Category: (1)
Event ID: 1265
Date: 8/30/2004
Time: 1:59:41 PM
User: N/A
Computer: KEP-FILES
Description:
The attempt to establish a replication link with parameters

Partition: CN=Schema,CN=Configuration,DC=keponline
Source DSA DN: CN=NTDS
Settings,CN=MAIN,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=keponline
Source DSA Address: 66166f88-f808-4c6b-ae40-286f1617f78c._msdcs.keponline
Inter-site Transport (if any):

failed with the following status:

The DSA operation is unable to proceed because of a DNS lookup failure.

The record data is the status code. This operation will be retried.
Data:
0000: 4c 21 00 00 L!..



Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1265
Date: 8/31/2004
Time: 12:41:06 PM
User: N/A
Computer: KEP
Description:
The attempt to establish a replication link with parameters

Partition: CN=Schema,CN=Configuration,DC=keponline
Source DSA DN: CN=NTDS
Settings,CN=MAIN,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=keponline
Source DSA Address: 66166f88-f808-4c6b-ae40-286f1617f78c._msdcs.keponline
Inter-site Transport (if any):

failed with the following status:

The DSA operation is unable to proceed because of a DNS lookup failure.

The record data is the status code. This operation will be retried.
Data:
0000: 4c 21 00 00 L!..





DC Diagnosis

Performing initial setup:
* Verifing that the local machine kep, is a DC.
* Connecting to directory service on server kep.
* Collecting site info.
* Identifying all servers.
* Found 3 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\KEP
Starting test: Connectivity
* Active Directory LDAP Services Check
KEP's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
......................... KEP failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\KEP
Skipping all tests, because server KEP is
not responding to directory service requests
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Test omitted by user request: OutboundSecureChannels

Running enterprise tests on : keponline
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... keponline passed test Intersite
Starting test: FsmoCheck
GC Name: \\kep.keponline
Locator Flags: 0xe00001fd
PDC Name: \\kep.keponline
Locator Flags: 0xe00001fd
Time Server Name: \\kep.keponline
Locator Flags: 0xe00001fd
Preferred Time Server Name: \\kep.keponline
Locator Flags: 0xe00001fd
KDC Name: \\kep.keponline
Locator Flags: 0xe00001fd
......................... keponline passed test FsmoCheck


(e-mail address removed)
www.napair.net

 

[Tim Springston [MS]]

This stands out on the face of it as a relatively straightforward DNS
configuration issue.

I would suggest setting all three DCs (at least temporarily) to have one of
the their number as the preferred DNS server in the NIC properties.

Then ensure that the selected DNS server allows dynamic updates. Next,
restart the NETLOGON service on all three DCs. Following that, do an
IPCONFIG /FLUSHDNS on each DC at the respective command prompts.

Then go to DSSITE.MSC (AD Sites and Services) and see if AD replication will
work without error (taking into account that you may need to create some
replication connections yourself to save time).

Please repost if we can help.