XADM: "DSGetDCName" Gets Secondary Servers, Which Causes Needless Traffic to Remote Sites

This article was previously published under Q316990
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
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).
CAUSE
This problem may occur because of changes in Exchange 2000 Server Service Pack 2 (SP2).
RESOLUTION
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 theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: DSAccess

File nameVersion
Dsaccess.dll6.0.5770.38

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:
250570 XADM: Directory Service Server Detection and DSAccess Usage
After you configure these settings, the DSAccess component on the Exchange server does not perform discovery of secondary servers (servers that are outside the site).
STATUS
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.
out-of-site out of site
Properties

Article ID: 316990 - Last Review: 10/24/2013 09:35:25 - Revision: 4.1

  • Microsoft Exchange 2000 Server Service Pack 2
  • kbnosurvey kbarchive kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB316990
Feedback