Solved

domain controller not replicating

Posted on 2008-10-22
4
2,896 Views
Last Modified: 2012-08-13
Hi guys
I have multiple domain controllers accross the globe.
one of the DC's in amsterdam has failed to replicate all of a sudden with any of the other domains.
In the error of the amsterdam server I get

Event Type:      Error
Event Source:      NTDS Replication
Event Category:      Replication
Event ID:      1864
Date:            22/10/2008
Time:            11:15:07
User:            NT AUTHORITY\ANONYMOUS LOGON
Computer:      FSNL
Description:
This is the replication status for the following directory partition on the local domain controller.
 
Directory partition:
DC=Hamburg,DC=DEAP,DC=local
 
The local domain controller has not recently received replication information from a number of domain controllers.   The count of domain controllers is shown, divided into the following intervals.
 
More than 24 hours:
1
More than a week:
1
More than one month:
0
More than two months:
0
More than a tombstone lifetime:
0
Tombstone lifetime (days):
60
 Domain controllers that do not replicate in a timely manner may encounter errors. It may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.
 
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.

Ive also run a replmon and done a 'search domain controllers for replication error'
and I get
Active Directory Replication Domain Controller Replication Failure Output
Printed at    22/10/2008 17:23:22

Below are the replication failures detected on Domain Controllers for this domain:

Domain Controller Name:                   MSTR
              Directory Partition:        CN=Configuration,DC=DEAP,DC=local
              Replication Partner:        Amsterdam\FSNL
              Failure Code:                1908
              Failure Reason:             Could not find the domain controller for this domain.

Domain Controller Name:                   MSTR
              Directory Partition:        CN=Schema,CN=Configuration,DC=DEAP,DC=local
              Replication Partner:        Amsterdam\FSNL
              Failure Code:                1908
              Failure Reason:             Could not find the domain controller for this domain.

Domain Controller Name:                   MSTR
              Directory Partition:        DC=ForestDnsZones,DC=DEAP,DC=local
              Replication Partner:        Amsterdam\FSNL
              Failure Code:                1256
              Failure Reason:             The remote system is not available. For information about network troubleshooting, see Windows Help.

Domain Controller Name:                   MSTR
              Directory Partition:        DC=Athens,DC=DEAP,DC=local
              Replication Partner:        Amsterdam\FSNL
              Failure Code:                1256
              Failure Reason:             The remote system is not available. For information about network troubleshooting, see Windows Help.

Domain Controller Name:                   MSTR
              Directory Partition:        DC=Beijing,DC=DEAP,DC=local
              Replication Partner:        Amsterdam\FSNL
              Failure Code:                1256
              Failure Reason:             The remote system is not available. For information about network troubleshooting, see Windows Help.

Domain Controller Name:                   MSTR
              Directory Partition:        DC=Warsaw,DC=DEAP,DC=local
              Replication Partner:        Amsterdam\FSNL
              Failure Code:                1256
              Failure Reason:             The remote system is not available. For information about network troubleshooting, see Windows Help.

Domain Controller Name:                   MSTR
              Directory Partition:        DC=Moscow,DC=DEAP,DC=local
              Replication Partner:        Amsterdam\FSNL
              Failure Code:                1256
              Failure Reason:             The remote system is not available. For information about network troubleshooting, see Windows Help.

Domain Controller Name:                   MSTR
              Directory Partition:        DC=Tokyo,DC=DEAP,DC=local
              Replication Partner:        Amsterdam\FSNL
              Failure Code:                1256
              Failure Reason:             The remote system is not available. For information about network troubleshooting, see Windows Help.

Domain Controller Name:                   MSTR
              Directory Partition:        DC=Amsterdam,DC=DEAP,DC=local
              Replication Partner:        Amsterdam\FSNL
              Failure Code:                1256
              Failure Reason:             The remote system is not available. For information about network troubleshooting, see Windows Help.

Domain Controller Name:                   MSTR
              Directory Partition:        DC=Hamburg,DC=DEAP,DC=local
              Replication Partner:        Amsterdam\FSNL
              Failure Code:                1256
              Failure Reason:             The remote system is not available. For information about network troubleshooting, see Windows Help.

Domain Controller Name:                   MSTR
              Directory Partition:        DC=London,DC=DEAP,DC=local
              Replication Partner:        Amsterdam\FSNL
              Failure Code:                1256
              Failure Reason:             The remote system is not available. For information about network troubleshooting, see Windows Help.

what the hell is going on, what could the possible reasons for this be, ive restarted the DC in amsterdam, restarted the netlogon service, done a dns flush and registerdns.

where is the problem lying,

Guys would appreciate as much help as I can get with this.
0
Comment
Question by:allawyg
  • 2
  • 2
4 Comments
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 22778457
Can you do a netdiag then post results?
0
 

Author Comment

by:allawyg
ID: 22778990
sure. I will do it tommorow morning, is there any specific commands I need to add
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 22779750
Do netdiag /v. Do a dcdiag with no switches.
0
 

Accepted Solution

by:
allawyg earned 0 total points
ID: 22902956
The solution was this.

I had to manually enter in the dns details to the dc it was replicating with and when i was half way through the dc picked up the rest and connection was established.

I dont know the science behind that. haha but it worked.
0

Join & Write a Comment

BIND is the most widely used Name Server. A Name Server is the one that translates a site name to it's IP address. There is a new bug in BIND (https://kb.isc.org/article/AA-01272), affecting all versions of BIND 9 from BIND 9.1.0 (inclusive) thro…
Synchronize a new Active Directory domain with an existing Office 365 tenant
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now