Domain Naming FSMO role did not respond
Topic Last Modified: 2005-11-17
The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine the value of the fSMORoleOwner attribute of the domain naming operations master in the Configuration Naming Context. For example, in a domain called contoso.com, fSMORoleOwner for the domain naming operations master is an attribute of CN=Partitions,CN=Configuration,DC=contoso,DC=com. The Exchange Server Analyzer then tries to open a Lightweight Directory Access Protocol (LDAP) connection to TCP port 389 on the domain controller that currently holds this role. If the Exchange Server Analyzer cannot connect to this domain controller, an error is displayed.
The domain naming master is a forest-wide operations master role because it manages the addition and removal of all directory partitions, regardless of domain, in the forest hierarchy. The domain controller that has the domain naming master role is the only domain controller that can do the following:
Add new domains to the forest.
Remove existing domains from the forest.
Add or remove cross-reference objects to external directories.
There can be only one domain naming master in the whole forest.
Verify that the directory server specified in the error is online and accessible by Exchange servers in your organization.
If this directory server has been decommissioned, you must assign the domain naming master role to another domain controller.
For more information about transferring the domain naming operations master role from one domain controller to another domain controller, see the following Microsoft Knowledge Base articles:
For Microsoft Windows Server™ 2003, see 324801, "How To View and Transfer FSMO Roles in Windows Server 2003" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=324801).
For Microsoft Windows® 2000 Server, see 255690, "HOW TO: View and Transfer FSMO Roles in the Graphical User Interface" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=255690).