Error in ExDeploy.log: Could not connect to the Exchange 5.5 server

I've gone through the diagnostic logs and the only errors I see were in the DCDiag log, but they don't look related or relevent (I'm not going to setup load balancing...)

         Starting test: frsevent
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
         Group Policy problems.
         ......................... IMS-MAIN failed test frsevent

         Starting test: systemlog
         An Error Event occured.  EventID: 0xC0001B58
         Time Generated: 04/18/2004   14:51:24
         Event String: The Network Load Balancing service failed to
         An Error Event occured.  EventID: 0xC0001B72
         Time Generated: 04/18/2004   14:51:24
         Event String: The following boot-start or system-start
         ......................... IMS-MAIN failed test systemlog

Okay, let me pump the points up a bit...

If I read this right, you have a 5.5 exch server and you want to migrate all the stuff to the e2k3 server?
After installing the w2k3 domain controller does your 5.5 server work, connect to AD, etc?
Did you check exdeploy.log and orgnamecheck.log files and review the log contents to ensure that SetupPrep didn't encounter any errors?

If all the above is ture did you go this route for the e2k3 server deploy:

Start the Exchange deployment tools by inserting the Exchange 2003 CD-ROM and selecting Exchange Deployment Tools from the Exchange 2003 dialog box.
When the Exchange Server Deployment Tools Wizard starts, click "Deploy the first Exchange 2003 server."
Click "Coexistence with Exchange 5.5," click Next to move to Phase 2 of the wizard, then click Next again to move to Phase 3 of the wizard.
I recommend running SetupPrep to ensure that you've completed all preparatory steps. Select the check box for Step 1 of Phase 3 of the wizard, which this figure shows.
Enter the Exchange 5.5 server name, the Global Catalog (GC) server name, and a log-file path, then click "Run SetupPrep now."
Open the exdeploy.log and orgnamecheck.log files and review the log contents to ensure that SetupPrep didn't encounter any errors.
Move to Step 3 of Phase 3, then click "Run Setup now."
Click Next to move past the introduction page of the Microsoft Exchange Installation Wizard.
Select "I agree" to the license, then click Next.
The installation wizard defaults to selecting a Typical installation. Click Next.
Select "Join or upgrade an existing Exchange 5.5 Organization," then click Next.
When prompted, enter the Exchange 5.5 server name, then click Next.
Click OK to tell the installation wizard to proceed with tests to ensure that the Exchange 2003 server can be introduced into the organization.
After the installation wizard finishes the tests, click "I agree that I have read and will be bound by the license agreements for this product" and click Next.
When prompted, enter the service account password used for Exchange 5.5, then click Next.
Click Next to move past the installation summary.
The installation wizard will begin installing the Exchange 2003 server and display its progress onscreen. After the server installation is complete, click Finish.

Your Exchange 2003 server will appear in the list of servers, and you can start moving mailboxes and services as required. If you follow the remaining steps of the Exchange Deployment Tools Wizard, you should change your connection agreements to replicate to the new Exchange 2003 server, then run the validation tools outlined in step 5 of the wizard.

Hi Ans-Ansdenver,

You're reading the situation right. To clarify, the new W2K3 DC is going to be the new W2K3 Exchange Server.

I can create AD users on both DCs. And I created in Exchange 5.5 a new recipient and linked it to the test user. And AD noted the link to the mailbox when I deleted the test user.

And I am following the path you've outlined. The error in the ExDeploy.log comes when I run DSScopeScan in the Phase 1 step.

I was wondering if LDAP was configured to a different port or even running, so I just ran a port scanner against the server. LDAP was found running on port 389.

Where is the LDAP port configured and how do I confirm that it's really running?

I figured it out. It was an LDAP port issue with Exchange 5.5. I guess I was supposed to move it to another port during the server upgrade from NT to W2K. I found an article that explained how to switch it to port 390. I then ran setup with the new port and the error disappeared from the ExDeploy.log.

I want to thank ans-ansdenver for providing a step-by-step guide. I wish I could award some points for the effort. But I was following several similar guides in my training manuals and textbooks. And the problem was happening during the first phases of the steps, so all hte other steps failed...