All Active Directory servers in the domain are not responding


Topic Last Modified: 2007-11-16

The Microsoft Exchange Server 2007 Management Pack for Microsoft Operations Manager (MOM) monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.

To learn more about this event, do one or more of the following:

  • Review the description of the event that includes the variables specific to your environment. From the MOM Operator Console, select this alert, and then click the Properties tab.

  • Review all events that have been logged that meet the criteria of this MOM alert. From the MOM Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description.


Product Name


Product Version

8.0 (Exchange Server 2007)

Event ID


Event Source

MSExchange ADAccess

Alert Type


MOM Rule Path

Microsoft Exchange Server/Exchange 2007/Common Components/Active Directory Access

MOM Rule Name

All Active Directory servers in the domain are not responding. Make sure that there is a domain controller that is located in the same domain as the Exchange server is up and running.


This Error event indicates that the Exchange server was unable to contact a domain controller in the local domain. DSAccess needs a local domain controller to perform topology discovery.

This event may occur when the Exchange server starts. For example, if no domain controllers respond when the Exchange server starts, the Microsoft® Exchange System Attendant (MSExchangeSA) and all its dependent services will not start.

This event may also occur when the Exchange server and all required services are running. For example, if all domain controllers and global catalog servers become unreachable during ordinary operation, the MSExchangeSA and all its dependent services will stop.


When all domain controllers and global catalog servers go down, a new topology discovery becomes necessary.

This event can occur if the domain controllers in local or all domains become unreachable because of network problems.

User Action

To resolve this error, verify that at least one domain controller in the local domain, the domain local to Exchange server, is running and reachable from the Exchange server. Do one or more of the following:

  • Use the Ping or PathPing command-line tools to test basic connectivity. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems.

  • Run the Dcdiag command line tool to test domain controller health. To do this, run dcdiag /s:<Domain Controller Name> at a command prompt on the Exchange Server. Use the output of Dcdiag to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag Overview at the Microsoft Windows Server TechCenter.

For More Information

To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.

To review Exchange 2007 event message articles that may not be represented by Exchange 2007 MOM alerts, see the Events and Errors Message Center.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.