XCON: Troubleshooting MSExchangeMU Event 1031 (286786)
The information in this article applies to:
- Microsoft Exchange 2000 Server
This article was previously published under Q286786 SYMPTOMS
You may receive the following error message in your Application event log.
Event Type: Warning
Event Source: MSExchangeMU
Event Category: General
Event ID: 1031
Description:
A conflict was detected between an authoritative SMTP address in a recipient policy and a SMTP connector. The domain 'microsoft.com' for this address will be treated as a local, authoritative domain. To resolve the conflict, remove 'microsoft.com' from the address space of the connector 'CN=smtp microsoft load balance,CN=Connections,CN=Charlotte,CN=Routing Groups,CN=Charlotte,CN=Administrative Groups,CN=Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=microsoft,DC=2k'.
CAUSE
You may have multiple SMTP connectors defined with the same bridgehead and address space. This configuration is commonly used to load balance between to remote hosts.
RESOLUTION
Instead of creating two SMTP connectors with the same address space and bridgehead (but different smart host), try creating a single connector with multiple smart hosts. You can do this by either of two ways. You can use Domain Name System (DNS) in a round-robin configuration. Or, you can enter the smart hosts' names separated by commas in the Forward all mail through this connector to the following smart hosts option on the General tab of the SMTP Connector Properties page. You can use the NetBIOS name, a fully-qualified domain name (FQDN), IP address, or any combination thereof. Some examples include:
Example A: By NetBIOS Name
Example B: By FQDN
host1.domain.com,host2.domain,com,host3.domain.com
Example C: By IP Address
[192.168.0.1],[192.168.0.2],[192.168.0.3]
When sending to smart hosts separated with commas, if those smart hosts are represented by IP addresses contained in square brackets (which is done to bypass name resolution), as in Example C, instead of the DNS name, you may experience problems if you are running an Exchange 2000 Server version that is earlier than Exchange 2000 Server Service Pack 1 (SP1) with the round robin load balancing. Instead, what will happen is that the connector will only use the first server in the list. To work around that issue you can enter the smart host in the round robin by either host name or by FQDN.
| Modification Type: | Minor | Last Reviewed: | 4/25/2005 |
|---|
| Keywords: | kberrmsg kbprb KB286786 |
|---|
|