Export (0) Print
Expand All
Expand Minimize

DSAccess reports that this Active Directory server is not functional

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2005-11-18

The Microsoft® Exchange Server Analyzer Tool queries the Exchange_DSAccessDC Microsoft Windows® Management Instrumentation (WMI) class in the ROOT\MicrosoftExchangeV2 namespace to determine the value for the IsUp key. If the IsUp key is set to False, an error is displayed.

If the IsUp key is set to True, it indicates that the domain controller responded the last time the Exchange server tried to establish a connection. If IsUp is set to False, it indicates that the domain controller did not respond to connection attempts.

The lack of response does not always mean that the domain controller or global catalog is down or malfunctioning. Sometimes, there may network connectivity issues between the Exchange server and the domain controller that could cause this failure. Such a failure could also be the result of a firewall between the Exchange server and the domain controller on which the appropriate ports have not been opened.

  1. Check that the domain controller is running by trying to ping to it.

  2. If there is a firewall, make sure that the firewall has the correct ports open. Be aware that firewalls can be configured to drop PING packets also. Check your firewall documentation for details about how to open or close specific ports.

  3. Make sure that there are no other network related issues, such as malfunctioning switches, routers, and cables.

For more information about DSAccess and directory services detection, see the Microsoft Knowledge Base article 250570, "Directory Service Server Detection and DSAccess Usage" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=250570).

For more information about troubleshooting network connectivity issues, see the Knowledge Base article 325487, "How to troubleshoot network connectivity problems" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=325487).

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft