Exchange 2010 not sending outbound email

Customer has SBS 2003 with Exchange 2003, and in this domain an Exchange 2010 server has been installed. All mailboxes and public folders have been migrated.

Exchange 2010 has a send connector on the hub transport to send all outbound email through a smarthost (EPA/FuseMail). Everything to now has been working

Windows updates were run on both servers last night, and since doing so, Exchange 2010 isn't sending emails out of the organisation. There are no bouncebacks (yet).

I can send mail into the organisation and to other internal users.

This is my only exposure to Exchange 2010, so I don't know what to check.
LVL 17
Chris MillardAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Check the exchange queue if the emails are sitting in queue. Also check all the exchange services are running.
Chris MillardAuthor Commented:
I'm seeing an error in the event log which reads:-

The Microsoft Exchange Mail Submission service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.
That might be the cause of the issue. Please restart the exchange services and check again.
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Chris MillardAuthor Commented:
I've restarted the Exchange 2010 server, and checking the Mail Queue, it shows 72 queued messages, and the Next Routing Hop shows as:-

cn=first routing group,cn=routing groups,cn=first administrative group,cn=administrative groups,cn=first organisation,cn=Microsoft exchange,cn=services,cn=configuration,dc=mydcname,dc=local

This appears to be therefore routing through the old Exchange 2003 server rather than straight out through the smarthost?
Simon Butler (Sembee)ConsultantCommented:
Exchange 2003 on SBS 2003 will create an SMTP Connector.
This is seen by Exchange 2010 as a read-only Send Connector.
Furthermore, Exchange 2003 will see the Send Connector on Exchange 2010 as a SMTP connector.

You probably have two issues.

1. The presence of the SMTP connector. If you want email to go out through Exchange 2010 then you need to delete that SMTP Connector.
2. Not withstanding point 1, email should still flow out through the Exchange 2003 server if that is what Exchange wants to do.
Therefore you need to check the SMTP virtual server on the Exchange 2003 server. Ensure there are no restrictions are on the VS that would stop Exchange from sending email.
The most common problem though will be with the routing group connectors. Very common for those to stop working. You need to use EMS on Exchange 2010 to resolve that problem, not Exchange 2003 ESM.
Remove them using remove-routinggroupconnector and then recreate them with new-routinggroupconnector

Although is this is your first exposure to Exchange 2010, then you should really have a consultant involved. Exchange 2003 and 2010 are very different - chalk and cheese in installation, admin and support.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Chris MillardAuthor Commented:
Simon - the old Exchange 2003 server is acting up (disk errors) following last nights reboot after Windows Updates.

What I have done is create a new send connector on Exchange 2010 and set the source server as the Exchange 2010 server. I have then stopped and restarted the Microsoft Exchange Transport service on Exchange 2010 and all email is now going out.

I am going to get rid of Exchange 2003 as soon as the customer allows it!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.