Question

Locked

replication error windows 2003 server dns

By fox_x ·
I have 2 DC of windows 2003 server standard edition, and they cannot replicate, meaning that actually only one of them (the first one I installed) and the second one is not functioning as a DC (even though I ran there DCPROMO).

I'll paste here a message of the event viewer and after that the log of DCDIAG.
In the event viewer of Directory service I get this event 1863:
This is the replication status for the following directory partition on the local domain controller.

Directory partition:
DC=ForestDnsZones,DC=YogaEsoteric,DC=Net

The local domain controller has not received replication information from a number of domain controllers within the configured latency interval.

Latency Interval (Hours):
24
Number of domain controllers in all sites:
1
Number of domain controllers in this site:
1

The latency interval can be modified with the following registry key.

Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency error interval (hours)

To identify the domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>".

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


And this is from DCDIAG:

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\YESERVER
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly registered
with DNS
......................... YESERVER passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\YESERVER
Starting test: Replications
[Replications Check,YESERVER] A recent replication attempt failed:
From YESERVER2 to YESERVER
Naming Context: DC=ForestDnsZones,DC=YogaEsoteric,DC=Net
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2008-02-11 14:58:43.
The last success occurred at 2008-02-08 15:58:09.
71 failures have occurred since the last success.
[YESERVER2] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
[Replications Check,YESERVER] A recent replication attempt failed:
From YESERVER2 to YESERVER
Naming Context: DC=DomainDnsZones,DC=YogaEsoteric,DC=Net
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2008-02-11 14:58:44.
The last success occurred at 2008-02-08 15:58:09.
71 failures have occurred since the last success.
[Replications Check,YESERVER] A recent replication attempt failed:
From YESERVER2 to YESERVER
Naming Context: CN=Schema,CN=Configuration,DC=YogaEsoteric,DC=Net
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2008-02-11 14:59:05.
The last success occurred at 2008-02-08 15:58:09.
71 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,YESERVER] A recent replication attempt failed:
From YESERVER2 to YESERVER
Naming Context: CN=Configuration,DC=YogaEsoteric,DC=Net
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2008-02-11 14:58:43.
The last success occurred at 2008-02-10 17:24:27.
22 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,YESERVER] A recent replication attempt failed:
From YESERVER2 to YESERVER
Naming Context: DC=YogaEsoteric,DC=Net
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2008-02-11 14:59:26.
The last success occurred at 2008-02-10 17:20:42.
22 failures have occurred since the last success.
The source remains down. Please check the machine.
REPLICATION-RECEIVED LATENCY WARNING
YESERVER: Current time is 2008-02-11 14:59:34.
DC=ForestDnsZones,DC=YogaEsoteric,DC=Net
Last replication recieved from YESERVER2 at 2008-02-08 15:58:09.
DC=DomainDnsZones,DC=YogaEsoteric,DC=Net
Last replication recieved from YESERVER2 at 2008-02-08 15:58:09.
CN=Schema,CN=Configuration,DC=YogaEsoteric,DC=Net
Last replication recieved from YESERVER2 at 2008-02-08 15:58:09.
CN=Configuration,DC=YogaEsoteric,DC=Net
Last replication recieved from YESERVER2 at 2008-02-10 17:24:31.
DC=YogaEsoteric,DC=Net
Last replication recieved from YESERVER2 at 2008-02-10 17:20:46.
......................... YESERVER passed test Replications
Starting test: NCSecDesc
......................... YESERVER passed test NCSecDesc
Starting test: NetLogons
......................... YESERVER passed test NetLogons
Starting test: Advertising
......................... YESERVER passed test Advertising
Starting test: KnowsOfRoleHolders
......................... YESERVER passed test KnowsOfRoleHolders
Starting test: RidManager
......................... YESERVER passed test RidManager
Starting test: MachineAccount
......................... YESERVER passed test MachineAccount
Starting test: Services
......................... YESERVER passed test Services
Starting test: ObjectsReplicated
......................... YESERVER passed test ObjectsReplicated
Starting test: frssysvol
......................... YESERVER passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the

SYSVOL has been shared. Failing SYSVOL replication problems may cause

Group Policy problems.
......................... YESERVER failed test frsevent
Starting test: kccevent
......................... YESERVER passed test kccevent
Starting test: systemlog
......................... YESERVER passed test systemlog
Starting test: VerifyReferences
......................... YESERVER passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : YogaEsoteric
Starting test: CrossRefValidation
......................... YogaEsoteric passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... YogaEsoteric passed test CheckSDRefDom

Running enterprise tests on : YogaEsoteric.Net
Starting test: Intersite
......................... YogaEsoteric.Net passed test Intersite
Starting test: FsmoCheck
......................... YogaEsoteric.Net passed test FsmoCheck


Thanks a lot,
Yoav

This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Back to Networks Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums