AD REPLICATION FAILURE. HELP!!!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have 2 servers that seem to be having trouble communicating with each
other. The computer names are as follows: WESS.EDGE1 and WESS.EDGE2. I think
these replication failures are causing one of my Windows XP Pro machines to
have issues logging into network resources. If I restart the main controller,
WESS.EDGE1, it allows him to connect for a while and then fails again later.
This issue actually occured first in a Windows 2000 workstation and then
moved to a different Windows XP Pro machine. Those first two machines no
longer have the issue and they only had a problem once. I admit that I do not
know the details of how AD works though I understand the premise. Below is a
log pulled from the Active Directory Replication Monitor. Let me know if I am
shooting at the correct issue or if I am way off track here.
---------------------------
Active Directory Replication Domain Controller Replication Failure Output
Printed at 10/31/2005 8:07:13 AM

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

Domain Controller Name: EDGE1
Directory Partition: CN=Schema,CN=Configuration,DC=WESS
Replication Partner: Default-First-Site-Name\EDGE2
Failure Code: 5
Failure Reason: Access is denied.

Domain Controller Name: EDGE1
Directory Partition: CN=Configuration,DC=WESS
Replication Partner: Default-First-Site-Name\EDGE2
Failure Code: 5
Failure Reason: Access is denied.

Domain Controller Name: EDGE1
Directory Partition: DC=WESS
Replication Partner: Default-First-Site-Name\EDGE2
Failure Code: 5
Failure Reason: Access is denied.

Domain Controller Name: EDGE2
Directory Partition: CN=Schema,CN=Configuration,DC=WESS
Replication Partner: Default-First-Site-Name\EDGE1
Failure Code: 5
Failure Reason: Access is denied.

Domain Controller Name: EDGE2
Directory Partition: CN=Configuration,DC=WESS
Replication Partner: Default-First-Site-Name\EDGE1
Failure Code: 5
Failure Reason: Access is denied.

Domain Controller Name: EDGE2
Directory Partition: DC=WESS
Replication Partner: Default-First-Site-Name\EDGE1
Failure Code: 5
Failure Reason: Access is denied.
---------------------------
 
I figured it out. There must have been some sort of corruption associated
with the information AD stored for the Computer Name. I changed the name of
the computer on the network and the issue seems to have disappeared.
 
I have 2 servers that seem to be having trouble communicating
with each
other. The computer names are as follows: WESS.EDGE1 and
WESS.EDGE2. I think
these replication failures are causing one of my Windows XP
Pro machines to
have issues logging into network resources. If I restart the
main controller,
WESS.EDGE1, it allows him to connect for a while and then
fails again later.
This issue actually occured first in a Windows 2000
workstation and then
moved to a different Windows XP Pro machine. Those first two
machines no
longer have the issue and they only had a problem once. I
admit that I do not
know the details of how AD works though I understand the
premise. Below is a
log pulled from the Active Directory Replication Monitor. Let
me know if I am
shooting at the correct issue or if I am way off track here.
---------------------------
Active Directory Replication Domain Controller Replication
Failure Output
Printed at 10/31/2005 8:07:13 AM

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

Domain Controller Name: EDGE1
Directory Partition:
CN=Schema,CN=Configuration,DC=WESS
Replication Partner:
Default-First-Site-NameEDGE2
Failure Code: 5
Failure Reason: Access is denied.

Domain Controller Name: EDGE1
Directory Partition:
CN=Configuration,DC=WESS
Replication Partner:
Default-First-Site-NameEDGE2
Failure Code: 5
Failure Reason: Access is denied.

Domain Controller Name: EDGE1
Directory Partition: DC=WESS
Replication Partner:
Default-First-Site-NameEDGE2
Failure Code: 5
Failure Reason: Access is denied.

Domain Controller Name: EDGE2
Directory Partition:
CN=Schema,CN=Configuration,DC=WESS
Replication Partner:
Default-First-Site-NameEDGE1
Failure Code: 5
Failure Reason: Access is denied.

Domain Controller Name: EDGE2
Directory Partition:
CN=Configuration,DC=WESS
Replication Partner:
Default-First-Site-NameEDGE1
Failure Code: 5
Failure Reason: Access is denied.

Domain Controller Name: EDGE2
Directory Partition: DC=WESS
Replication Partner:
Default-First-Site-NameEDGE1
Failure Code: 5
Failure Reason: Access is denied.
---------------------------
Click to expand...

If I’m reading it correct you have configured your AD domain with a
single labeled DNS domain name. That is not recommended and needs
additional configurations.

See:
http://support.microsoft.com/?id=300684
http://www.petri.co.il/active_directory_installation_requirements.htm
 
I am not sure where I see how that effects the replication of AD data between
domain controllers? This seems to mention only issues with client
authentication and syncronization. Even with a single label domain name I was
operating fine for almost 5 years.
 
Back
Top