New 2008 Server not replicating with W2k3, please help!

justcrash · 08-14-2009, 07:53 AM

Ok, created a new 2008 server with the intention of demoting our old schema master and making the new 2008 box the main box. however, it is not replicating with any of the other servers and I am getting a ton of errors, could someone please help me out?

Here are the error messages. I also noticed when I actually went to save the notepad file with the errors, it (the new server) did not see the network, but it sees the machines from a command line and I was able to put it on the domain AND promote it to a DC. Anyway... yes.. PLEASE.. any help you can give me would be great. The new server is named BOENEW.

From the Active Directory Domain Services role:
The attempt to establish a replication link for the following writable directory partition failed.

Directory partition:
CN=Configuration,DC=LHSD,DC=net
Source directory service:
CN=NTDS Settings,CN=VIRTUAL,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=LHSD,DC=net
Source directory service address:
fb061eb2-5c1e-45fa-81dc-1bbc589d6c87._msdcs.LHSD.net
Intersite transport (if any):

This directory service will be unable to replicate with the source directory service until this problem is corrected.

User Action
Verify if the source directory service is accessible or network connectivity is available.

Additional Data
Error value:
1722 The RPC server is unavailable.
=========================================================================================
From the application server role:
Event 10009 DistribuitedCOM
DCOM was unable to communicate with the computer LHHS3.LHSD.net using any of the configured protocols.
DCOM was unable to communicate with the computer BOE1.LHSD.net using any of the configured protocols.
(about 6 more, for the other servers... BOE1 is the one this one is replacing, the backbone)
==========================================================================================
From the DNS server role:
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.
The DNS server detected that it is not enlisted in the replication scope of the directory partition DomainDnsZones.LHSD.net. This prevents the zones that should be replicated to all DNS servers in the LHSD.net domain from replicating to this DNS server. For information on how to add a DNS server to the replication scope of an application directory partition, please see Help and Support.

To create or repair the domain-wide DNS directory partition, open the the DNS console. Right-click the applicable DNS server, and then click 'Create Default Application Directory Partitions'. Follow the instructions to create the default DNS application directory partitions. For more information, see 'To create the default DNS application directory partitions' in Help and Support.
The error was 8367.
===================================================================================

The DNS server detected that it is not enlisted in the replication scope of the directory partition DomainDnsZones.LHSD.net. This prevents the zones that should be replicated to all DNS servers in the LHSD.net domain from replicating to this DNS server. For information on how to add a DNS server to the replication scope of an application directory partition, please see Help and Support.

To create or repair the domain-wide DNS directory partition, open the the DNS console. Right-click the applicable DNS server, and then click 'Create Default Application Directory Partitions'. Follow the instructions to create the default DNS application directory partitions. For more information, see 'To create the default DNS application directory partitions' in Help and Support.
The error was 8367.
=====================================================================================
The DNS server was unable to connect to the domain naming FSMO BOE1.LHSD.net. No modifications to Directory Partitions are possible until the FSMO server is available for LDAP connections. The event data contains the error code.

From the File Services Role:
The File Replication Service is having trouble enabling replication from E101 to BOENEW for c:\windows\sysvol\domain using the DNS name e101.LHSD.net. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name e101.LHSD.net from this computer.
[2] FRS is not running on e101.LHSD.net.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
==================================================================================
The File Replication Service is having trouble enabling replication from LHHS1 to BOENEW for c:\windows\sysvol\domain using the DNS name LHHS1.LHSD.net. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name LHHS1.LHSD.net from this computer.
[2] FRS is not running on LHHS1.LHSD.net.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
======================================================================================
The File Replication Service is having trouble enabling replication from LHSE1 to BOENEW for c:\windows\sysvol\domain using the DNS name lhse1.LHSD.net. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name lhse1.LHSD.net from this computer.
[2] FRS is not running on lhse1.LHSD.net.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

08-14-2009, 07:53 AM	#1 (permalink)
justcrash Registered User Join Date: Sep 2008 Posts: 89 OS: Win XP Pro/Server 2003	New 2008 Server not replicating with W2k3, please help! Ok, created a new 2008 server with the intention of demoting our old schema master and making the new 2008 box the main box. however, it is not replicating with any of the other servers and I am getting a ton of errors, could someone please help me out? Here are the error messages. I also noticed when I actually went to save the notepad file with the errors, it (the new server) did not see the network, but it sees the machines from a command line and I was able to put it on the domain AND promote it to a DC. Anyway... yes.. PLEASE.. any help you can give me would be great. The new server is named BOENEW. From the Active Directory Domain Services role: The attempt to establish a replication link for the following writable directory partition failed. Directory partition: CN=Configuration,DC=LHSD,DC=net Source directory service: CN=NTDS Settings,CN=VIRTUAL,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=LHSD,DC=net Source directory service address: fb061eb2-5c1e-45fa-81dc-1bbc589d6c87._msdcs.LHSD.net Intersite transport (if any): This directory service will be unable to replicate with the source directory service until this problem is corrected. User Action Verify if the source directory service is accessible or network connectivity is available. Additional Data Error value: 1722 The RPC server is unavailable. ========================================================================================= From the application server role: Event 10009 DistribuitedCOM DCOM was unable to communicate with the computer LHHS3.LHSD.net using any of the configured protocols. DCOM was unable to communicate with the computer BOE1.LHSD.net using any of the configured protocols. (about 6 more, for the other servers... BOE1 is the one this one is replacing, the backbone) ========================================================================================== From the DNS server role: The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error. The DNS server detected that it is not enlisted in the replication scope of the directory partition DomainDnsZones.LHSD.net. This prevents the zones that should be replicated to all DNS servers in the LHSD.net domain from replicating to this DNS server. For information on how to add a DNS server to the replication scope of an application directory partition, please see Help and Support. To create or repair the domain-wide DNS directory partition, open the the DNS console. Right-click the applicable DNS server, and then click 'Create Default Application Directory Partitions'. Follow the instructions to create the default DNS application directory partitions. For more information, see 'To create the default DNS application directory partitions' in Help and Support. The error was 8367. =================================================================================== The DNS server detected that it is not enlisted in the replication scope of the directory partition DomainDnsZones.LHSD.net. This prevents the zones that should be replicated to all DNS servers in the LHSD.net domain from replicating to this DNS server. For information on how to add a DNS server to the replication scope of an application directory partition, please see Help and Support. To create or repair the domain-wide DNS directory partition, open the the DNS console. Right-click the applicable DNS server, and then click 'Create Default Application Directory Partitions'. Follow the instructions to create the default DNS application directory partitions. For more information, see 'To create the default DNS application directory partitions' in Help and Support. The error was 8367. ===================================================================================== The DNS server was unable to connect to the domain naming FSMO BOE1.LHSD.net. No modifications to Directory Partitions are possible until the FSMO server is available for LDAP connections. The event data contains the error code. From the File Services Role: The File Replication Service is having trouble enabling replication from E101 to BOENEW for c:\windows\sysvol\domain using the DNS name e101.LHSD.net. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name e101.LHSD.net from this computer. [2] FRS is not running on e101.LHSD.net. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. ================================================================================== The File Replication Service is having trouble enabling replication from LHHS1 to BOENEW for c:\windows\sysvol\domain using the DNS name LHHS1.LHSD.net. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name LHHS1.LHSD.net from this computer. [2] FRS is not running on LHHS1.LHSD.net. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. ====================================================================================== The File Replication Service is having trouble enabling replication from LHSE1 to BOENEW for c:\windows\sysvol\domain using the DNS name lhse1.LHSD.net. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name lhse1.LHSD.net from this computer. [2] FRS is not running on lhse1.LHSD.net. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.