I could not fully grasp your question. However, when you migrate an Exchange 5.5 server to Exchange 2000 In-place, the Exchange 5.5 site becomes a mixed mode site. In mixed mode you have SRS (site replication sevice) which replicates information from Exchange DS to AD. This SRS listens on LDAP port 379. Once you migrate to Exchange 2000, your two way connection agreemnets automaticaly change/reconfigure to port 379. Regards, Raj -----Original Message----- From: Frank Wakelin [mailto:fwakelin@xxxxxxxxxxxxxx] Sent: March 11, 2002 12:22 PM To: [ExchangeList] Subject: [exchangelist] UPGRADE HELP: Exchange 5.5 LDAP Port for in place upgrade 5.5 - 2 000. Importance: High http://www.MSExchange.org/ I am going to be performing an in-place upgrade of our Exchange 5.5 server. The process is pretty clear with the exception of the reconfiguring of the LDAP port. The course, as well as the MS KB article (Q255256: XADM: Upgrade Fails When Exchange Server 5.5 LDAP Port Has Been Reconfigured): "Generally, the LDAP port is changed so that a domain controller, Microsoft Exchange Server 5.5, and Active Directory Connector (ADC) can all be run on the same computer. When an upgrade is performed, however, it expects that the Exchange Server 5.5 directory is listening on the default port (389)." This is exactly the situation with our Exchange 5.5 server. The LDAP port on the Exchange server is currently 390. The ADC is already installed in our case and is configured to use port 390 for exchange LDAP. I take it from this article that the setup program itself also access the Exchange 5.5 server (in addition to the ADC access it) via LDAP to obtain site information. To work around this problem the article states: 1. Set the ADC to Replicate Never. 2. Change the LDAP port on the Exchange Server 5.5 computer back to 389. 3. Re-run Setup. 4. After this, the ADC won't be needed for this particular server, and you can remove it or point it to another Exchange Server 5.5 computer. Even if the ADC is not replicating, port 389 will still be taken by the AD LDAP service, will it not? If so, then it will still not be able to connect with the exchange 5.5 ldap service as it will not work due to the fact that the port is already taken. The article does state that this solution is for the scenario when Exchange 5.5 is installed on a Windows 2000 DC however, so I am a bit confused as to how this will work... Can you help me understand the process here? Do I have to allow the setup to fail first with the port as is, then reconfigure it to 389? _____ <http://www.cga-canada.org/eng/images/email-logo.gif> <mailto:fwakelin@xxxxxxxxxxxxxx> Frank Wakelin- Network/Systems Engineer <http://www.cga-canada.org/> Certified General Accountants Association of Canada 700 - 1188 West Georgia Street Vancouver, British Columbia - Canada Phone: (604) 605-5064 (direct) - FAX: (604) 689-5845 ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: psraj@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')