New Exchange 2013 server in org can't receive mail

Hi, I have a 2 node Exchange 2013 DAG running CU5 that is having problems and have built 3 new servers to replace the 2.  We will create a new DAG.  Yesterday I installed Exchange 2013 with CU8 and the install completed successfully with no issues. I have a mailbox on the new server that I can connect to using OWA and send mail with no issues.  When I send mail to the mailbox on the new server, the message hangs on either of the existing servers in the Unreachable Domain queue with the error that "There is currently no route to the mailbox database."

Troubleshooting to this point:

 Restart Transport service on server1 and server2
 Matched configuration for receive connectors between server3 and the other 2.
 Messages sent from server3 to a mailbox on server1 or server2 is delivered fine.
 Replies and messages sent from server1 or server2 to a mailbox on server3 are not delivered.

What am I missing?
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.

Will SzymkowskiSenior Solution ArchitectCommented:
Have you been able to completely reboot the servers or restart all services? When you say server1 server2 are you talking about old or new servers?

Routing should be configured automatically for internal mail and also between Exchange servers. Have you tried re-creating the default receive connectors?


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
aridaenAuthor Commented:
Thanks Will for your reply.  Yes, I am talking about the old servers when I say server1 and server2.  The new server is server3.  I have not been able to completely reboot server1 and server2 yet, but that will happen tomorrow.  In my previous experience, the connectors have always configured themselves and everything just worked.  I was thinking maybe the problems with the old servers are having an effect on mail flow.  If the reboots don't help, I'll recreate the connectors.
aridaenAuthor Commented:
The update is that the customer requested to place the server restarts on hold over the weekend so that didn't happen.  I installed Exchange on my second new server and tested between both new servers.  My server3 could not send mail to server4 which I had just built and restarted.  However, after restarting server3, I was able to send mail in both directions between server3 and server4.  Looks like the restarts will resolve the mail delivery issue.  What a bunch of BS having to restart existing servers when you add a new server to the environment just so they can send mail to the new guy.
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.