Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

5.5 on 2k to 2k3 on 2k3 same domain and org 1

Status
Not open for further replies.

HeleneP

Technical User
Apr 18, 2002
64
US
We are planning on migrating our 5.5 servers to 2k3. We already have a 2k domain running AD with 3 exchange 5.5 servers. We're buying new kit with 2k4 and want to install exch 2k3. We've set up a test environment with 2 machines. As there's only the 2 the one with 5.5 is the global catalogue server and they're both domain and DNS controllers. This does not reflect our existing 'real' setup.

We've hit a problem running the deployment tools. Initially dsscopescan stated in exdeploy.log that it "could not connect to the exch 5.5 server <FQDN>. tools that require an exchange 5.5 server will not run" but orgreport and gvercheck we fine. We've carried on and got to running ADC tools but are stuck on step 2 data collection. When we run it we get "server <FQDN>:389 is not an exchange 5.5 server or srs service"

What are we missing? Any help would be great.

Thanks in advance
 
Launch Exchange 5.5 admin tool, find LDAP, change the port number you are using.
 
Thanks quincyju.

It dawned on me that the 2k AD takes port 389 as priority late yeaterday, so therefore the port number was the issue. Have changed it and it's working fine now.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top