A few errors I'm receiving after adding one CAS and one multirole HT/MBX physical server in a single 2003 server environment for which I'm having problems finding the exact resolution. Their E2003 environment (ahp-exch01.domain.local) is all on one physcial host behind a firewall. Their public URL is webmail.domain.com. 1. BPA's only critical issue: The computer account for Exchange server ahp-exch01.domain.local does not appear to contain the fully-qualified domain name of Exchange SMTP virtual server 'Default SMTP Virtual Server'. This may cause Kerberos authentication to fail when sending messages between servers. The tool expected to find 'SMTPSVC/Webmail.domain.com' in the 'servicePrincipalName'. The article says to use this syntax: setspn.exe -a SMTPSVC/mail.yourdomain.com YOURSERVERNAME I want to confirm that the first field is the public URL (webmail.domain.com) and the second field is what? The E2010 CAS server name? The E2003 server name? The internal webmail alias (webmail.domain.local)? Something else? 2. After installing E2010, it imported two SMTP address spaces from E2003 which are configured for fax routing on the old E2003 server. The E2003 server has a fax application installed on the same server, as well as a Brooktrout TR1034 board. The fax software routes the faxes via SMTP to the localhost IP. They are using DNS instead of a smarthost for SMTP routing. The two error messages are: --- Non-SMTP address space 'SMS:*;1' was detected on the DNS SMTP connector 'FaxMaker SMTP Connector' in routing tables with timestamp 2/8/2012 7:38:20 PM. The address space is ignored on the connector because a non-delivery report (NDR) will be sent for the message or because the message will go to another connector. Exchange Server 2007 or Exchange 2010 tasks block this configuration. However, the connector may have been set up by Exchange Server 2003. --- Non-SMTP address space 'FAX:*;1' was detected on the DNS SMTP connector 'FaxMaker SMTP Connector' in routing tables with timestamp 2/8/2012 7:38:20 PM. The address space is ignored on the connector because a non-delivery report (NDR) will be sent for the message or because the message will go to another connector. Exchange Server 2007 or Exchange 2010 tasks block this configuration. However, the connector may have been set up by Exchange Server 2003. --- I found this link but it's unclear to me what specific steps I need to perform to resolve the errors: http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=5025&EvtSrc=MSExchangeTransport&LCID=1033 3. I'm getting these errors randomly on the HTMBX server even when the CAS server is online: --- DCOM was unable to communicate with the computer AHP-EXCAS01.domain.local using any of the configured protocols. --- Jim Thanks for any guidance you can offer.

For the SMTPSVC SPN, I found this ancient link which did the best job IMO of covering internal/external references with setspn: http://www.tech-archive.net/Archive/Exchange/microsoft.public.exchange.connectivity/2006-11/msg00103.html I checked the virtual server in ESM and it already had Webmail.domain.com listed in the FQDN field. I ran following but it didn't list any changes, but ExBPA no longer barks about it. --- C:\Users\username>setspn -L ahp-exch01 Registered ServicePrincipalNames for CN=AHP-EXCH01,OU=Servers,DC=domain,DC=local: exchangeMDB/ahp-exch01.domain.local exchangeMDB/AHP-EXCH01 exchangeRFR/ahp-exch01.domain.local exchangeRFR/AHP-EXCH01 SMTPSVC/AHP-EXCH01 SMTPSVC/ahp-exch01.domain.local HOST/AHP-EXCH01 HOST/ahp-exch01.domain.local C:\Users\username>setspn.exe -a SMTPSVC/webmail.domain.com AHP-EXCH01 Registering ServicePrincipalNames for CN=AHP-EXCH01,OU=Servers,DC=domain,DC=local SMTPSVC/webmail.domain.com Updated object C:\Users\username>setspn -L ahp-exch01 Registered ServicePrincipalNames for CN=AHP-EXCH01,OU=Servers,DC=domain,DC=local: SMTPSVC/webmail.domain.com exchangeMDB/ahp-exch01.domain.local exchangeMDB/AHP-EXCH01 exchangeRFR/ahp-exch01.domain.local exchangeRFR/AHP-EXCH01 SMTPSVC/AHP-EXCH01 SMTPSVC/ahp-exch01.domain.local HOST/AHP-EXCH01 HOST/ahp-exch01.domain.local C:\Users\username> ---

For the SMTPSVC SPN, I found this ancient link which did the best job IMO of covering internal/external references with setspn: http://www.tech-archive.net/Archive/Exchange/microsoft.public.exchange.connectivity/2006-11/msg00103.html I checked the virtual server in ESM and it already had Webmail.domain.com listed in the FQDN field. I ran following but it didn't list any changes, but ExBPA no longer barks about it. --- C:\Users\username>setspn -L ahp-exch01 Registered ServicePrincipalNames for CN=AHP-EXCH01,OU=Servers,DC=domain,DC=local: exchangeMDB/ahp-exch01.domain.local exchangeMDB/AHP-EXCH01 exchangeRFR/ahp-exch01.domain.local exchangeRFR/AHP-EXCH01 SMTPSVC/AHP-EXCH01 SMTPSVC/ahp-exch01.domain.local HOST/AHP-EXCH01 HOST/ahp-exch01.domain.local C:\Users\username>setspn.exe -a SMTPSVC/webmail.domain.com AHP-EXCH01 Registering ServicePrincipalNames for CN=AHP-EXCH01,OU=Servers,DC=domain,DC=local SMTPSVC/webmail.domain.com Updated object C:\Users\username>setspn -L ahp-exch01 Registered ServicePrincipalNames for CN=AHP-EXCH01,OU=Servers,DC=domain,DC=local: SMTPSVC/webmail.domain.com exchangeMDB/ahp-exch01.domain.local exchangeMDB/AHP-EXCH01 exchangeRFR/ahp-exch01.domain.local exchangeRFR/AHP-EXCH01 SMTPSVC/AHP-EXCH01 SMTPSVC/ahp-exch01.domain.local HOST/AHP-EXCH01 HOST/ahp-exch01.domain.local C:\Users\username> ---

For the SMTPSVC SPN, I found this ancient link which did the best job IMO of covering internal/external references with setspn: http://www.tech-archive.net/Archive/Exchange/microsoft.public.exchange.connectivity/2006-11/msg00103.html I checked the virtual server in ESM and it already had Webmail.domain.com listed in the FQDN field. I ran following but it didn't list any changes, but ExBPA no longer barks about it. --- C:\Users\username>setspn -L ahp-exch01 Registered ServicePrincipalNames for CN=AHP-EXCH01,OU=Servers,DC=domain,DC=local: exchangeMDB/ahp-exch01.domain.local exchangeMDB/AHP-EXCH01 exchangeRFR/ahp-exch01.domain.local exchangeRFR/AHP-EXCH01 SMTPSVC/AHP-EXCH01 SMTPSVC/ahp-exch01.domain.local HOST/AHP-EXCH01 HOST/ahp-exch01.domain.local C:\Users\username>setspn.exe -a SMTPSVC/webmail.domain.com AHP-EXCH01 Registering ServicePrincipalNames for CN=AHP-EXCH01,OU=Servers,DC=domain,DC=local SMTPSVC/webmail.domain.com Updated object C:\Users\username>setspn -L ahp-exch01 Registered ServicePrincipalNames for CN=AHP-EXCH01,OU=Servers,DC=domain,DC=local: SMTPSVC/webmail.domain.com exchangeMDB/ahp-exch01.domain.local exchangeMDB/AHP-EXCH01 exchangeRFR/ahp-exch01.domain.local exchangeRFR/AHP-EXCH01 SMTPSVC/AHP-EXCH01 SMTPSVC/ahp-exch01.domain.local HOST/AHP-EXCH01 HOST/ahp-exch01.domain.local C:\Users\username> ---

Hello, The command should be: setspn.exe -a SMTPSVC/webmail.domain.com Intenert facing server In additon, please check the application log and find if there are any related error reports. Thanks, Simon

Hello, The command should be: setspn.exe -a SMTPSVC/webmail.domain.com Intenert facing server In additon, please check the application log and find if there are any related error reports. Thanks, Simon

Hello, The command should be: setspn.exe -a SMTPSVC/webmail.domain.com Intenert facing server In additon, please check the application log and find if there are any related error reports. Thanks, Simon

So you're saying it should be "setspn.exe -a SMTPSVC/webmail.domain.com webmail.domain.com"? Application log on the CAS?

So you're saying it should be "setspn.exe -a SMTPSVC/webmail.domain.com webmail.domain.com"? Application log on the CAS?

For the DCOM error, I found this link. I will try it and report back in a few days. http://www.expta.com/2011/07/fix-for-dcom-10009-errors-in-exchange.html

For the DCOM error, I found this link. I will try it and report back in a few days. http://www.expta.com/2011/07/fix-for-dcom-10009-errors-in-exchange.html

Hello, Is there any update on this thread? Thanks, Simon

Hello, Is there any update on this thread? Thanks, Simon

Hello, Is there any update on this thread? Thanks, Simon

The last DCOM error was on the 13th, so I think that is resolved. I'm not seeing any error messages in the Application log related to SPN, but I'm still confused on whether I got it right based on your previous post. For the non-SMTP address spaces, I'm inferring that they were imported from Exchange 2003, and even though they are listed they won't be recognized by E2010? E2003 and the routing group are still in the environment, and the fax software/hardware is still on the E2003 server. It will likely be a week or so before we move these items to the new server. So I guess if the faxes are working now, and those 2 address spaces are not in use, then it's safe to remove them? When I install the fax software on the hub transport, will the fax software be able to deliver mail to 127.0.0.1 successfully, or will I need to allow that somewhere?

The last DCOM error was on the 13th, so I think that is resolved. I'm not seeing any error messages in the Application log related to SPN, but I'm still confused on whether I got it right based on your previous post. For the non-SMTP address spaces, I'm inferring that they were imported from Exchange 2003, and even though they are listed they won't be recognized by E2010? E2003 and the routing group are still in the environment, and the fax software/hardware is still on the E2003 server. It will likely be a week or so before we move these items to the new server. So I guess if the faxes are working now, and those 2 address spaces are not in use, then it's safe to remove them? When I install the fax software on the hub transport, will the fax software be able to deliver mail to 127.0.0.1 successfully, or will I need to allow that somewhere?

The last DCOM error was on the 13th, so I think that is resolved. I'm not seeing any error messages in the Application log related to SPN, but I'm still confused on whether I got it right based on your previous post. For the non-SMTP address spaces, I'm inferring that they were imported from Exchange 2003, and even though they are listed they won't be recognized by E2010? E2003 and the routing group are still in the environment, and the fax software/hardware is still on the E2003 server. It will likely be a week or so before we move these items to the new server. So I guess if the faxes are working now, and those 2 address spaces are not in use, then it's safe to remove them? When I install the fax software on the hub transport, will the fax software be able to deliver mail to 127.0.0.1 successfully, or will I need to allow that somewhere?

I don't understand why a previous message dated 9 days ago was marked as an answer 6 hours ago, when my last post 2 days ago indicated the DCOM errors still existed.

I don't understand why a previous message dated 9 days ago was marked as an answer 6 hours ago, when my last post 2 days ago indicated the DCOM errors still existed.

I don't understand why a previous message dated 9 days ago was marked as an answer 6 hours ago, when my last post 2 days ago indicated the DCOM errors still existed.

I don't understand why a previous message dated 9 days ago was marked as an answer 6 hours ago, when my last post 2 days ago indicated the DCOM errors still existed.