Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

Odd Message Tracking Error: Message transerred to computer through SMTP

Posted on 2004-08-25
Last Modified: 2010-08-05
I've got an Exchange 2003 server sitting on a W2K3 Server behind a Hotbrick firewall on SBC DSL.

A user reported that her e-mail messages where not being recieved at an outside destination. I checked on the problem e-mail messages in the Message Tracking Center and found the final line:
  Message transerred to computer through SMTP

A message that got through had the final line:
  Message transerred to mta.snet.net through SMTP

I'm checking the event logs and see the System Event
Source: DCOM
Event ID: 10009
DCOM was unable to communicate with the computer computer using any of the configured protocols.

I also see
Source: DCOM
Event ID: 10009
DCOM was unable to communicate with the computer mta5.snet.net using any of the configured protocols.

I've Googled and didn't find any relevent articles, or articles that apearded relevent. But I've been wrong before. :-)

Is something setup incorrectly on my Exchange Server or is this an outside DNS issue?
Question by:TerrellITC
LVL 104

Expert Comment

ID: 11902002
What is snet.net? Is that your domain, the sender or recipient of the email messages?

If it is external to you, then it looks like it could be a dns issue.


Author Comment

ID: 11907313

Sorry, I thought is was obvious...

A MX lookup shows "snet.net" is the mail domain for the receiver.

And "computer" is...?

I too assume its a DNS issue, but I'm unclear whether its internal or external.
LVL 104

Expert Comment

ID: 11908109
In this game you cannot presume anything.

Does your firewall inspect or do anything with SMTP traffic at all? I am wondering if it or something else is interfering. Cisco PIX are notorious for doing it with certain combinations.

Quickest solution? Setup and SMTP connector for this one domain to send email via your ISP.

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud


Author Comment

ID: 11915085
I don't believe that the Hotbrick firewall is doing anything on the SMTP traffic. I've seen some non-SMTP related funkiness, but I'm trying to determine if it's a problem with our ISP.

I'm learning about Exchange 2003 as I go. Can you give more detail to your solution? I've got the book Exchange Server Unleashed and it has the steps on making a SMTP connector. But I'm unclear on why I need to setup one here...

LVL 104

Accepted Solution

Sembee earned 250 total points
ID: 11915218
An SMTP Connector will send all email to your ISPs email server rather than trying to deliver it directly. Like giving a package to a courier rather than taking it across town yourself. The ISPs server then has to worry about delivering it.
If you setup a connector for this one domain then all the other mail will continue to be delivered normally (direct) while email for this one domain is sent via the ISP.
I am having to use SMTP connectors more often as clients use DSL lines which some ISPs block delivery from (AOL for example).


Author Comment

ID: 11915389
Okay, that makes sense. It sounds like I'll have to check on the relay policies of my ISPs. (I've got two "business-class" DSL connections.)

The only thing I don't like about that is that I would losing the ability to tell my users "I see that the Exchange Server delivered the message to the recepient's e-mail server. So it's their problem, not mine." With a connector to the ISP, I would have to go figure out what my ISP is up too... :-)

Expert Comment

ID: 12656360

First comment so bear with me.
Just installed Exch 2k (Enterprise) on W2k.
I see the DCOM 10009 errors when tracking a message that was delivered externally. I've tried the fix suggested in MS KB 245197 - I only have Connection orientated TCP/IP in the default protocols tab now - no effect.
In this case the 10009 error appears after the message is tracked - the messages are delivered OK.
Is the error a result of Message Tracking attempting to interrogate a server outside of our domain??
Anyone any more ideas?

Simon (another one ;-))

Expert Comment

ID: 14135474
simply make the test.

track a message an have a look on system log. when you get a dcom error after you tracked a message, the external mailserver, may not support tracking and quits the connection.


Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question