RPC binding does not match DNS resolved name
[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: 2007-03-21
The Microsoft® Exchange Server Analyzer Tool tries a Domain Name System (DNS) query against the configured DNS servers for each Exchange Server computer. This connection is made with a custom object processor that performs a name resolution request and analyzes the results. The Exchange Server Analyzer also queries the Active Directory® directory service to determine whether the server ncacn_ip_tcp value on the networkAddress attribute and the fully qualified domain name (FQDN) returned after DNS resolution are different. The networkAddress attribute is an attribute on each Exchange Server object in Active Directory. If the Exchange Server Analyzer finds that the server ncacn_ip_tcp value in Active Directory does not match the FQDN after DNS resolution, the Exchange Server Analyzer displays a warning.
This situation occurs if the FQDN of the server is changed after Exchange has been installed. Both Exchange Server and Active Directory require correctly configured and healthy DNS to operate correctly. Domain Naming Services registration and resolution issues can significantly affect the Exchange Server computer's ability to send, receive, and deliver messages. You can prevent problems if you make the two addresses match by manually editing the networkAddress attribute on the Exchange Server object in Active Directory.
You must update the ncacn_ip_tcp value on the server object in Active Directory to make sure that the ncacn_ip_tcp value matches the DNS FQDN of the server. The Exchange Server Analyzer output provides the name of the affected server.
If you incorrectly modify the attributes of Active Directory objects when you use Active Directory Service Interfaces (ADSI) Edit, the LDP (ldp.exe) tool, or another Lightweight Directory Access Protocol (LDAP) version 3 client, you may cause serious problems. These problems may require that you reinstall Microsoft Windows Server™ 2003, Exchange Server 2003 or Exchange Server 2007, or both. Modify Active Directory object attributes at your own risk.
To update the ncacn_ip_tcp value on the networkAddress attribute
Start the ADSI Edit tool from Windows® 2000 Support Tools or from Windows Server 2003 Support Tools.
Expand the following nodes:
Right-click Exchange_Server_Name, and then click Properties.
Click networkaddress in the Attributes list, and then click Edit.
Add a new value for ncacn_ip_tcp. Use the FQDN of the server instead of the current value.
The syntax for this value is ncacn_ip_tcp:FQDN. For example, if your Exchange server has a host name of EXCHANGE1 and the FQDN is EXCHANGE1.contoso.com, use the following value for ncacn_ip_tcp: ncacn_ip_tcp:EXCHANGE1.contoso.com.
Remove the original ncacn_ip_tcp value that contains the incorrect name of the server by selecting the original value and clicking Remove. Click OK two times to apply the change.
Restart all Exchange Server services on the server.
For more information about how to use DNS with Active Directory, see Microsoft Knowledge Base article 323418, "How To Integrate DNS with an Existing DNS Infrastructure If Active Directory Is Enabled in Windows Server 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=323418).