MSExchange ADAccess 2107
This article provides an explanation and possible resolutions for a specific Exchange event. If you don't find what you’re looking for here, try searching Exchange 2010 Help.
Details
Product Name |
Exchange |
Product Version |
14.0 |
Event ID |
2107 |
Category |
Topology |
Symbolic Name |
DSC_EVENT_GETHOSTBYNAME_FAILED |
Message Text |
Process %1 (PID=%2). Exchange Active Directory Provider failed to obtain an IP address for DS server %3, error %4 (%5). This host will not be used as a DS server by Exchange Active Directory Provider. |
Explanation
This Error event indicates that the Active Directory Provider did not obtain an IP address for an Active Directory server. This host will not be used as an Active Directory server by DSAccess. This could be caused by network problems. This is a critical error if there are no other domain controllers available.
User Action
To resolve this error, do one or more of the following:
Check the Application log for related events. The detail in other MSExchange ADAccess events and other events may help determine the root cause of this warning. Increase diagnostic logging for the MSExchange ADAccess\Topology category to Lowest or higher. For detailed information about how to increase logging, see Manage Diagnostic Logging Levels.
Use the
Ping
orPathPing
command-line tools to test basic connectivity. UsePing
to isolate network hardware problems and incompatible configurations. UsePathPing
to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, Advanced network adapter troubleshooting for Windows workstations.Run the
Dcdiag
command-line tool to test domain controller health. To do this, rundcdiag /s:[Domain Controller Name]
at a command prompt on the Exchange server. Use the output ofDcdiag
to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag Overview at the Windows Server TechCenter.
For more information about the Get-EventLogLevel and Set-EventLogLevel diagnostic logging cmdlets, see the following topics:
For More Information
If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.