Exchange Server domain name changes -- don't forget about IIS

Because of their co-dependent relationship, changes to Exchange Server can influence Internet Information Server (IIS) behavior and vice versa. One particular interaction between Exchange Server and IIS that can sometimes cause problems involves domain name changes.

When you change the domain name of an Exchange server, that domain name change is also replicated to the IIS metabase so that it can be used by the SMTP service (SmtpSvc).

Each domain that the SmtpSvc sends on behalf of is listed there in LM -> SmtpSvc -> 1 -> Domain -> <domain_name>. The <domain_name> entry may be a fully qualified domain name (FQDN) like yourcompany.com, or it might be an internal .local DNS entry.

If domain name changes are not propagated to the IIS metabase, email to the SMTP service will generate a non-delivery report (NDR) with the error:

Error 5.1.1: The e-mail account does not exist at the organization this message was sent to. Check the email address, or contact the recipient directly to find out the correct address.

This sounds confusing, especially since it seems like you're getting an error from the target organization. It's so misleading that you

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Exchange Server Administration Tips Using Mobile Device Manager 2008 server roles in Exchange 2007 An introduction to the DSAccess service in Exchange Server 2007 Exchange Performance Monitor tracks domain controller communication Exchange Server 2007 SP2 reinstates built-in backup capabilities Three Performance Monitors counters to use in Exchange Server 2007 Scheduling multiple Performance Monitor alerts in Exchange Server 2007 Which ActiveSync authentication method is best for your mobile device? Configure Performance Monitor alerts for Exchange Server 2007 Disable ActiveSync in bulk with Exchange Management Shell commands Configuring ActiveSync authentication in Exchange Server 2007 Internet Information Services (IIS) and Exchange Server Interoperability Analyzing Exchange ActiveSync data from .CSV report files Automated redirects to OWA directories may fail when SSL is enforced Monitoring Outlook Web Access usage via IIS log files Exchange Server and Microsoft Internet Information Services (IIS) IIS 6 file corruption flaw impairs OWA Symantec Mail Security for Microsoft Exchange crashes IIS Outlook Web Access only displays parent directories Recreating IIS virtual directories for OWA, OMA and Exchange ActiveSync Forms-based authentication errors with OMA and ActiveSync Disappearing OWA and Exchange virtual directory settings Internet Information Services (IIS) and Exchange Server Interoperability Research

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

might be tempted to go on a wild goose chase to debug a nonexistent problem with a remote server -- but the problem really lies with your own Exchange Server/IIS setup.

To confirm that this is truly the issue, use MetaEdit to open the IIS metabase and look at the abovementioned entry. If you see an entry for a domain name other than your currently configured one (under Domain), delete it. (You may want to back up the IIS metabase before doing this, just in case.)

About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter.

Do you have comments on this tip? Let us know.

Related information from SearchExchange.com: