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
Solved
no outgoing or incoming mail
Posted on 2010-11-30
I tested the mx record and this is what I got:
smtp:69.199.57.100 smtp
220 sis.onyxarchitects.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.4675 ready at Tue, 30 Nov 2010 04:57:13 -0800
Not an open relay.
0 seconds - Good on Connection time
5.507 seconds - Warning on Transaction time
OK - 69.199.57.100 resolves to mail.onyxarchitects.com
OK - Reverse DNS matches SMTP Banner
Session Transcript:
HELO please-read-policy.mxtoolb
250 sis.onyxarchitects.com Hello [64.20.227.133] [47 ms]
MAIL FROM: <supertool@mxtoolbox.com>
250 2.1.0 supertool@mxtoolbox.com...
RCPT TO: <test@example.com>
550 5.7.1 Unable to relay for test@example.com [5054 ms]
QUIT
221 2.0.0 sis.onyxarchitects.com Service closing transmission channel [47 ms]
I tested from several locations and they all say it is working but it is not working. Mail is sitting in the queue. The exchange troubleshooting assistant is telling me there is an error of Delivery status notification code 4.3.1 I have not been able to fix it. Any help would be appreciated. 2k3 server sp2 running on win 2k3 enterp. server sp2. Was working fine until the network card went bad and I changed it.
smtp:69.199.57.100 smtp
220 sis.onyxarchitects.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.4675 ready at Tue, 30 Nov 2010 04:57:13 -0800
Not an open relay.
0 seconds - Good on Connection time
5.507 seconds - Warning on Transaction time
OK - 69.199.57.100 resolves to mail.onyxarchitects.com
OK - Reverse DNS matches SMTP Banner
Session Transcript:
HELO please-read-policy.mxtoolb
250 sis.onyxarchitects.com Hello [64.20.227.133] [47 ms]
MAIL FROM: <supertool@mxtoolbox.com>
250 2.1.0 supertool@mxtoolbox.com...
RCPT TO: <test@example.com>
550 5.7.1 Unable to relay for test@example.com [5054 ms]
QUIT
221 2.0.0 sis.onyxarchitects.com Service closing transmission channel [47 ms]
I tested from several locations and they all say it is working but it is not working. Mail is sitting in the queue. The exchange troubleshooting assistant is telling me there is an error of Delivery status notification code 4.3.1 I have not been able to fix it. Any help would be appreciated. 2k3 server sp2 running on win 2k3 enterp. server sp2. Was working fine until the network card went bad and I changed it.
[X]
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
-
16
14
30 Comments
I think you may have to recreate the SMTP virtual server under the exchange adminintrator.
Exchange administrator -> Server -> server name -> protocols -> smtp. Document the existing settings, delete the virtual server, create a new one.
This often resolves this type of problem when a new network card is installed.
Hope this helps.
msincorp
Exchange administrator -> Server -> server name -> protocols -> smtp. Document the existing settings, delete the virtual server, create a new one.
This often resolves this type of problem when a new network card is installed.
Hope this helps.
msincorp
Wow.. missed that one.
Exchange administrator -> Servers ->connectors -> smtp connector. Document the existing settings, delete the smtp connector, create a new one.
One more thing.. Exchange administrator -> Server -> server name -> protocols -> smtp -> smtp virtual server -> advanced -> make sure you have the FQDN set properly (mail.domain.com) and that check dns comes back with a valid domain name.
sorry for the confusion.
msincorp
Exchange administrator -> Servers ->connectors -> smtp connector. Document the existing settings, delete the smtp connector, create a new one.
One more thing.. Exchange administrator -> Server -> server name -> protocols -> smtp -> smtp virtual server -> advanced -> make sure you have the FQDN set properly (mail.domain.com) and that check dns comes back with a valid domain name.
sorry for the confusion.
msincorp
There are two smtp virtual servers. One is under Protocols - smtp - default smtp virtual server and the other is under Connectors - new smtp virtual server. Which one to delete and replace?
The one under connectors should do it.
Also, make sure you check for valid FQDN under the protocols -> advanced tab.
msincorp
Also, make sure you check for valid FQDN under the protocols -> advanced tab.
msincorp
I deleted the virtual server under connectors and filled in the data but one are won't let me finish. It says "You must specify a smart host" for the name. I put default smtp virtual server but it won't take it. What is it looking for?
ok.. there are 3 required elements in the smtp connector:
1) A name for the connector (can be anythig, so make it meaningful to you)
2) The address space to "serve" usually set to SMTP and an "*" to indicate all domains
3) A local bridgehead server (usually set to your server)
If you are using a smarthost (one of your ISP's mail servers, or a 3rd party mail server) to send your mail, you will have to select that option in the "forward all mail through this connector to the following smart hosts". This is only necessary if your mail server is NOT sending the mail directly.
Almost there.
msincorp
1) A name for the connector (can be anythig, so make it meaningful to you)
2) The address space to "serve" usually set to SMTP and an "*" to indicate all domains
3) A local bridgehead server (usually set to your server)
If you are using a smarthost (one of your ISP's mail servers, or a 3rd party mail server) to send your mail, you will have to select that option in the "forward all mail through this connector to the following smart hosts". This is only necessary if your mail server is NOT sending the mail directly.
Almost there.
msincorp
I restarted information store and still no emails. The queues are growing. Should I do anything to the other virtual server?
ok.. right click on the largest queue, and select "force connection". see what the message is and post it here.
did you verify the FQDN settings under the smtp server -> advanced tab? starting to sound like a DNS issue.
did you verify the FQDN settings under the smtp server -> advanced tab? starting to sound like a DNS issue.
fqdn is set at mail.onyxarchitects.com and all messages (54) are under pending submission. Nothing happens when I force a connection. How do I check for dns problem? Thanks for staying with me.
ok.. silly question, but here goes... when you replaced the network card did you set the IP address to a static IP? was it the same as the old network card? also, pay particular attention to the default gateway setting, is it set to your router / firewall? can you get on the internet from this system? can you "ping" other devices on the network?
don't worry... we'll get it sorted out.
msincorp
don't worry... we'll get it sorted out.
msincorp
Please confirm also that the following services are installed and running:
Microsoft Exchange Information Store
Microsoft Exchange Management
Microsoft Exchange MTA Stacks
Microsoft Exchange Routing Engine
Simple Mail Transfer Protocol (SMTP)
let me know.
msincorp
Microsoft Exchange Information Store
Microsoft Exchange Management
Microsoft Exchange MTA Stacks
Microsoft Exchange Routing Engine
Simple Mail Transfer Protocol (SMTP)
let me know.
msincorp
Hows your disk space on this volume? is it formatted as FAT or NTFS?
I found a microsoft article (http://support.microsoft.com/kb/284204) that describes the error code but it might not be related because it talks about disk space. Here's the short version:
Numeric Code: 4.3.1
Possible Cause: This code may be caused by resource problem such as a disk full condition. This code may also occur if your Simple Mail Transfer Protocol (SMTP) queue is on a File Allocation Table (FAT) partition and the service has reached a Windows-imposed limit on the number of concurrent file handles that can be opened by the SMTP Service. In this case, instead of receiving a disk full error, you might be receiving an out of memory error.
Troubleshooting: Make sure you have sufficient disk storage, and try to operate your Exchange Transport queues on an NTFS partition.
Take a look at the artice and let me know what you think.
msincorp
I found a microsoft article (http://support.microsoft.com/kb/284204) that describes the error code but it might not be related because it talks about disk space. Here's the short version:
Numeric Code: 4.3.1
Possible Cause: This code may be caused by resource problem such as a disk full condition. This code may also occur if your Simple Mail Transfer Protocol (SMTP) queue is on a File Allocation Table (FAT) partition and the service has reached a Windows-imposed limit on the number of concurrent file handles that can be opened by the SMTP Service. In this case, instead of receiving a disk full error, you might be receiving an out of memory error.
Troubleshooting: Make sure you have sufficient disk storage, and try to operate your Exchange Transport queues on an NTFS partition.
Take a look at the artice and let me know what you think.
msincorp
Ok, all the mentioned services are up and running. The ip is static and I can ping the entire network and have internet access. The volume is ntfs and has plenty of room. I saw that article already and it does not apply to me. The only thing I noticed is from a certain site, Network -tools.com, if I do email verification it comes with an error "No domain specified" this could be a clue.
Exchange administrator -> Server -> server name -> protocols -> smtp -> default smtp virtual server -> access -> relay -> check "only list below" (make sure it is the internal IP address of the mail server) -> check "allow all computers......"
then restart the IIS service (take the restart all services option).
msincorp
then restart the IIS service (take the restart all services option).
msincorp
Now the queue is empty. I tried to send an internal email and it is just sitting in the outbos folder. I clicked on send/receive but that did not help.
I was mistaken about the queue. The smtp service had not started and after starting it the queue is back at 68 and my email went out and joined the rest of them (in the queue).
can you "delete" the messages in the queue?
also, is there any chance of restarting this server after the messages are removed?
msincorp
also, is there any chance of restarting this server after the messages are removed?
msincorp
I have no choice. Have been working on this for 14 hours non stop. I will delete the messages and restart the server. I have to let everone know so they get off the server. It will take about 15 min for the server to restart.
have you tried the exchange best practices analyzer?
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=dbab201f-4bee-4943-ac22-e2ddbd258df3&displaylang=en
this will give us some insight.
msincorp
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=dbab201f-4bee-4943-ac22-e2ddbd258df3&displaylang=en
this will give us some insight.
msincorp
done testing and found not much of any problem. I am attaching screen shots.
analyzer.JPG
best-practice-baseline.JPG
best-practice-health.JPG
analyzer.JPG
best-practice-baseline.JPG
best-practice-health.JPG
looks like it could be your swap file (paging file) causing the error. are you sure about your disk space? do you have two volumes? a system volume and a data volume? could be your system volume is running out of disk space while you have plenty on the data volume.
Let me do some more checking on my lab computer.
msincorp
Let me do some more checking on my lab computer.
msincorp
The Filter folder on the exchange volume had grown too large and was the cause of the the problem. Deleting some of the older files resolved the issue. Thanks for all the help. You get all the points since you did suggest disk space problems could be causing the mail to fail.
Featured Post
Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies. Only from Platform Scholar.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
There are times when we need to generate a report on the inbox rules, where users have set up forwarding externally in their mailbox. In this article, I will be sharing a script I wrote to generate the report in CSV format.
New style of hardware planning for Microsoft Exchange server.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center.
Log into Exchange Admin Center.:
Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses
Course of the Month10 days, 22 hours left to enroll
719 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.