• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1553
  • Last Modified:

The description for Event ID ( 4006 ) in Source ( smtpsvc ) cannot be found

The description for Event ID ( 4006 ) in Source ( smtpsvc ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 61.187.98.7, 0733.com, The remote server did not respond to a connection attempt.
.
0
agiliopereira
Asked:
agiliopereira
  • 4
  • 4
1 Solution
 
SembeeCommented:
Nice error.
And your question is?

Cos my crystal ball is playing up at the moment.

Simon.
0
 
agiliopereiraAuthor Commented:
How about solving this error.
0
 
SembeeCommented:
Crystal ball is still on the blink...

You have left out all of the key information...

Exchange version and service pack?
Windows version and service pack?
What else is installed on this machine?

Are there messages stuck in the queue?
Is this a one off error, or reoccurring regularly?
Any patterns?

We can only work with what you have given us, and at the moment that is nothing whatsoever to go on.

Simon.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
agiliopereiraAuthor Commented:
Ok Simon. Exchange server 2003 with service pack 2 on windows server 2000. It has only exchange installed. This started just a month back. The queue shows 10 messages stick and retrying to send to a domain mboxx04.com.  Seems to be a chinese website. Do not know how to track the machine casuing this problem.
Thanks

Agilio
0
 
SembeeCommented:
It looks like a straight connection error.
Chinese stuff is always suspicious.

It could be a form of relaying - either authenticated, NDR or straight open relay. You will need to check for all three.
If you are relaying messages they normally show up in the queues.

As you are on Windows 2000 I can't really recommend enabling recipient filtering as it opens you to a dictionary attack.

Turn on Message tracking and see if the messages are coming from inside or outside.

Simon.
0
 
agiliopereiraAuthor Commented:
Sorry Simon, little raw with a couple of new issues. Where do I find the message tracking option and what happens if I find something there, or will I find something there?

Agilio
0
 
SembeeCommented:
Message Tracking only shows you what is happening, so you will not actually be able to do anything from there.
http://www.amset.info/exchange/message-tracking.asp

What it does is show what Exchange is doing with the message. It is evidence gathering stage, not problem fix. Without the evidence you will not know what the source of the problem is.

Simon.
0
 
agiliopereiraAuthor Commented:
Hi Sembee,

Whole place closed for Easter. Cannot test anything till Tuesday. Is it possible to keep this open?

Thanks again
Agilio
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now