You may receive messages that indicate that domain controllers cannot be found when you use the "AD Replication Partner Op Master Consistency" script in Microsoft Operations Manager 2000 (875425)

CAUSE

This problem occurs if the following conditions are true:

The domain controllers are in different domains than the domain of the MOM server.
The domain controllers are not registered in the same Windows Internet Name Service (WINS) database as the domain controller that runs the script.

For example, suppose that the script runs on a domain controller that is named maindc.corp.domain1.com. This domain controller has a replication partner that is named partner01.sub.domain2.com. In this scenario, the script tries to bind to ldap://partner01/RootDSE instead of binding to ldap://partner01.sub.domain2.com/RootDSE.

RESOLUTION

To resolve this problem, modify the script to use the fully qualified domain name (FQDN) of the domain controller instead of the NetBIOS name. To do this, follow these steps:

Start the MOM Administrator console.
Double-click Microsoft Operations Manager (Default) double-click Rules, double-click Advanced, and then click Scripts.
Double-click AD Replication Partner OP Master Consistency, and then click the Script tab.
Locate the following lines.

Note Starting from the top of the script, these lines are typically 66 and 68.
```
objPartner.Server = strDC

strPartnerDomain = objPartner.GetDomainForDC(strDC)
```
In each of these lines, change "strDC" to "strDnsDc" so that the lines read as follows:
```
objPartner.Server = strDnsDc

strPartnerDomain = objPartner.GetDomainForDC(strDnsDC)
```
Click OK to save the changes.

You may receive messages that indicate that domain controllers cannot be found when you use the "AD Replication Partner Op Master Consistency" script in Microsoft Operations Manager 2000 (875425)

SYMPTOMS

CAUSE

RESOLUTION