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

Exchnage 2010 to Ex2003 routing problem

Hello all -

We have three sites in a hub and spoke config all with their own Exchange servers.  They were all running Ex2003 and life was good.  Then the two 'remote' sites were upgraded to Exchange 2010 with the 'main' site staying on Ex2003.

Now we have a mail routing problem we can not figure out.  Internal mail works just fine everywhere.  Mail from the internet gets delivered everywhere as well.  However mail destined for the Internet has problems.

If there is no send connector configured in Ex2010, then the 'main' site that is on 2003 can send mail externally without an issue.  The two remote site cannot send external email though.

If we create a send connector not using a smarthost, then all email from all three sites is then sent through the associated Ex2010 remote site.  This is not what we want and does not really work due to MX lookups.

If we create a send connector that uses the Ex2003 sever as a smarthost, then all email just dissapears into la la land.

The Interop RGC connector is there as seen below -
Name                      SourceRoutingGroup                             TargetRoutingGroup
----                      ------------------                             ------------------
Interop RGC               Exchange Routing Group (DWBGZMFD01QNBJR)       First Routing Group
Interop RGC               First Routing Group                            Exchange Routing Group (DWBGZMFD01QNBJR)

So...any thoughts as to what is going on and how to fix it?

To be clear, we want all Internet email to be delivered by the Ex2003 server at the 'main' site.  Ex2010 just does not seem to want to route it there nicely.

Thanks in advance -

  • 5
1 Solution
Try adding the 2003 server as a smart host on your default SMTP connector on the 2010 server.  
dasmail2000Author Commented:
As stated, if I create a Send Connector and choose to use a smart host, then email simply disappears.  We have treid to figure out where it goes without any luck.

What I did for each step of the wizard is as follows:
New Send Connector
Custom type
* for Address space
IP address of 2003 Exchange server
None for authentication
The source server was one of the 2010 servers

Once done, I can see queues empty out but nothing is actually delivered to Inetrnet based hosts.

Any other thoughts?
dasmail2000Author Commented:
Just a note:

I can telnet from the Ex2010 servers to the Ex2003 server and send mail to the Internet just fine.
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

dasmail2000Author Commented:
This actually took MS four days to correct.  Turned out to be a problem with ISA2004 as that is what is used for the site-site VPNs.

Tracking that down was a bear.

dasmail2000Author Commented:
outside solution
dasmail2000Author Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

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

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