Article ID: 316990 - View products that this article applies to.
This article was previously published under Q316990
This article has been archived. It is offered "as is" and will no longer be updated.
If you use the graphical user interface (GUI) to configure the domain controller and global catalog, the Exchange 2000 DSAccess component may contact secondary servers (servers that are outside the site).
This problem may occur because of changes in Exchange 2000 Server Service Pack 2 (SP2).
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378The English version of this fix should have the following file attributes or later:
(http://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Collapse this tableExpand this table
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2. After you apply this fix to upgrade the DSAccess component, you must set the domain controller and global catalog in the registry on the Exchange 2000 server. For additional information about these settings, click the article number below to view the article in the Microsoft Knowledge Base:
250570After you configure these settings, the DSAccess component on the Exchange server does not perform discovery of secondary servers (servers that are outside the site).
(http://support.microsoft.com/kb/250570/EN-US/ )XADM: Directory Service Server Detection and DSAccess Usage
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.
Contact us for more help
Connect with Answer Desk for expert help.