XCON: MTA Fails to Pick Up DN of Servers with Similar Site Names

Last reviewed: July 15, 1997
Article ID: Q164856
The information in this article applies to:
  • Microsoft Exchange Server, versions 4.0 and 5.0

SYMPTOMS

When you calculate the routing on a server, the Distinguished Name (DN) for servers in other sites may be missing.

CAUSE

The site names are very similar. For example, suppose you set up three servers in a manner similar to the following:

   Server1: organization name to Microsoft, site name to test40
   Server2: organization name to Microsoft, site name to test40F
   Server3: organization name to Microsoft, site name to test40G

Connect Server 1 to Server 2 by means of the site connector, and replicate the directory. Connect Server 2 to Server 3 by means of the IMC connector, and replicate the directory.

If you calculate the routing on Server 1, you will notice that the DN is missing for Server 3. The downstream sites are compared to the local site and there is a match, so the downstream sites are discarded.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server versions 4.0 and 5.0. This problem was corrected in the latest Microsoft Exchange Server 4.0 and 5.0 U.S. Service Packs. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K
 

	
	


Keywords : kbbug4.00 kbbug5.00 kbfix4.00.sp4 kbfix5.00.sp1 kbusage XCON buglist
Version : 4.0 5.0
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.