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

Migrating to Exchange 2010, mail not working

I am in the process of migrating from Windows 2003 Small Business Server to Windows 2008 R2/Exchange2010.

I installed the new Exchange 2010 server using the typical install. After the install, I created a new send connector so I can send email directly from the 2010 server. I also edited the security settings on the receive connector to allow anonymous connections.

I migrated over one mailbox and tested sending and receiving email. I can send email to the internet but not internally. I also cannot receive any email either internally or externally. All email from the Exchange 2003 server still works fine.

Am I missing a connector or do I need to modify an existing connector?  
  • 4
1 Solution
Glen KnightCommented:
Check the default virtual SMTP connector on the SBS 2003 server, as per my article here: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_3044.html

Also check you have redirected port 25 for SMTP to the Exchange 2010 server fro m your router/firewall.

You may also find my migration guide here useful: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881.html
AceITAuthor Commented:
I read through the migration guide and everything looks correct. I also checked the items you suggested but they are all correct also.

One thing I am noticing is that on the default SmallBusiness SMTP Connector, in the Source Server tab, the Hub Transport Server list is empty. If I click on add, the local hub transport server shows up, but when I select it and click apply, I get the error message: "Source server (server name) isn't in the connectors source routing group."

What server should be in that list? Why do I get that error?
AceITAuthor Commented:
I am also getting this error in the application event log:

Event ID: 5015

Microsoft Exchange cannot find a route to the source transport server or home MTA server CN=SDAIHCSVR,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=SDAIHC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=sdaihc,DC=local for connector CN=SmallBusiness SMTP connector,CN=Connections,CN=first routing group,CN=Routing Groups,CN=first administrative group,CN=Administrative Groups,CN=SDAIHC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=sdaihc,DC=local in routing tables with timestamp 8/30/2010 7:00:49 PM. Microsoft Exchange is ignoring the source transport server.
AceITAuthor Commented:
I figured out what the problem was. When I did the Exchange 2010 install, it never created the routing groups between the 2010 and 2003 servers. I created them manually and the mail flows fine now.

AceITAuthor 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

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!

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