ADC Replication Not happening with new Ex2003 Server

[phillyTIM]

Greetings - I ask for your help in getting my new Exchange 2003 server running.

Right now, the basic problem is that the ADConnector that I have on my main Windows 2000 Domain Controller (ADC version 2003 (6.5)) is not connecting with new Exchange 2003 server I have installed.

The Exchange 2003 server was installed in mixed mode to co-exist with our current Ex5.5 server (which has NT4.0 installed, and LDAP set to port 1002) in our Windows 2000 domain. [I CAN see the Ex2003 server listed in the Servers area of Exchange 5.5 Administrator.]

At the ADConnector console, it has PubFolders and Users setup and seemingly replicating properly (I created a mailbox on 5.5, and now see it in AD), but the default CA_ between that domain server and the new Ex2003 server (apparently using port 1002 to connect, and that port IS open on the Ex2003 to be used) fails.

Connection authentication users are fine/verified and the Authentication methods used are from Kerberos (Windows Server) to Windows Challenge/Response (Exchange Server). I manually haven't done anything to open up port 1002, if that matters; because I haven't seen anything I needed to do; it is now just registered as open.

The connection is failing with Event Application Log ID 8026, MSADC, "LDAP Bind was unsuccessful on directory patriot (the new Ex2003 server)....Directory returned error 0x51 Server Down." error on the ADConnector domain server.

The patriot (Ex2003) server IS NOT down.

I'm at my wits end in trying things to do.

Do I also need the Exchange Server Manager 2003 installed on my domain controller with the ADC?

I humbly ask for your assistance in this matter, as it would really be appreciated. Thanks much!

 

[phillyTIM]

BTW: just to be SURE that you have the exact error message:

Source: MSADC Cat: LDAP Operations Event-ID: 8026 User: N/A

LDAP Bind was unsuccessful on directory patriot.(dom) for distinguished name "IS\EXCHADM". Directory returned error [0x51] Server Down. (Connection Agreement 'Config CA_1234 PATRIOT')

I will say that I do know & have verified the passwords used for EXCHADM (my domain's Exchange service account). It's odd that it would fail because of a password or somethin, because I know they've been entered correctly.

I turned on MSADC logging to medium, and am getting Event ID 8006 messages, which seem to be alright.

Please help!

 

[phillyTIM]

I found the problem - stupid me - shoulda checked my DNS for the server. It wasn't in there. Funny, if you can't ping something, how do you expect to do much else with it? ;-)

I guess this is a lesson for us all: ALWAYS check even the most basic, simple things!