Article ID: 288828
Article Last Modified on 2/28/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q288828
SYMPTOMS
Objects from Microsoft Exchange Server 5.5 may not be propagating to Active Directory, and the following error message may be logged in Windows NT Event Viewer:
Event ID: 8026
Event Source: MSADC
Event Type: Error
Description:
LDAP Bind was unsuccessful on directory SERVERNAME for distinguished name 'Windows nt\#adc'. Directory returned error:[0x31] Server Down. (Connection Agreement 'Connection Agreement Name' #2800)
CAUSE
This issue can occur if the Active Directory Connector (ADC) cannot bind to the Lightweight Directory Access Protocol (LDAP) port of the Exchange Server 5.5 computer. The ADC cannot bind to the LDAP port if the port number is not correctly configured in the Connection Agreement or if there are network issues that prevent communication between the computer that is running the ADC and the Exchange Server 5.5 computer.
RESOLUTION
To resolve this issue, verify that the Exchange Server 5.5 computer is listening on port 389 (LDAP communications occur on port 389 by default):
- On the computer that is running the ADC, click Start, and then click Run.
- Type the following command:
telnet (
servernameorIP address) 389
If LDAP is configured on port 389, when you run this command, a Telnet window opens, but you do not see a banner response. If LDAP is not configured on port 389, you receive the following message:
Could not open a connection to host on port 389: Connect failed.
If you cannot connect to port 389 of the Exchange Server 5.5 computer by using Telnet, use the Microsoft Exchange Server Administrator program to check the configuration:
- Start the Administrator program.
- Click to expand the Site container, and then click to expand the Configuration container.
- Click Protocols, and then double-click LDAP.
- Click the General tab, and then verify that the port number is set to 389.
- Compare this setting to the configuration of the Connection Agreement in the ADC. These settings must match.
MORE INFORMATION
For additional information about scenarios where a port other than 389 is used, click the article number below to view the article in the Microsoft Knowledge Base:
250989 XADM: Installing the ADC on a Windows 2000 Domain Controller That Also Runs Exchange Server
For additional information about how to troubleshoot ADC issues, click the article number below to view the article in the Microsoft Knowledge Base:
253841 XADM: Troubleshooting Active Directory Connector Replication Issues
Additional query words: exch2kp2w
Keywords: kberrmsg kbprb KB288828
