<div>
the Best practice tool should have given you a link to some potential help...
</div>


the Best practice tool should have given you a link to some potential help...

<div>
Without knowing anything about the environment this is a difficult thing to offer assistance on. Do you have multiple sites in the domain? If so, are the Site and Subnet assignements correct so that your Exchange servers are not talking across WAN links for global catalog and LDAP data? Is the DC that the Exchange server is talking to overloaded? DNS issues can also cause issues here - are you sure your DNS configuration is correct for the AD components to resolve, and resolve quickly?<br />

</div>


Without knowing anything about the environment this is a difficult thing to offer assistance on. Do you have multiple sites in the domain? If so, are the Site and Subnet assignements correct so that your Exchange servers are not talking across WAN links for global catalog and LDAP data? Is the DC that the Exchange server is talking to overloaded? DNS issues can also cause issues here - are you sure your DNS configuration is correct for the AD components to resolve, and resolve quickly?


<div>
Thank you guys. It seems that the DCs are being swamped. 
</div>


Thank you guys. It seems that the DCs are being swamped.

<div>
The teaming of the NIC did improve the performance of the DCs.
</div>


The teaming of the NIC did improve the performance of the DCs.

<div>
<div class="content wysiwyg-content">
I ran the Best Practice Tool on my Exhange 2000/2003 environment. There is a critical issue, the response time between my Exchange servers and the domain controllers is too high. What can I do to improve the communication between them?
</div>
</div>


I ran the Best Practice Tool on my Exhange 2000/2003 environment. There is a critical issue, the response time between my Exchange servers and the domain controllers is too high. What can I do to improve the communication between them?

How do I improve the response time between my domain controllers and my Exchange servers?

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).