Cannot email domain now it has moved from one instance of microsoft exchange 2013 to another server running microsoft exchange 2013

Posted on 2016-11-14
Medium Priority
Last Modified: 2016-11-19
Hello Experts,

I have an issue where users cannot email mailboxes that used to be on the same exchange 2013 server now that they have been moved to a different exchange 2013 server

So domain A and Domain B were on the same server and could email each other without an issue, Domain B has now moved to a different server and is working correctly however when users of Domain A try to email users of Domain B they get a bounce back stating that the database for domain B is offline '432 4.3.2 STOREDRV; mailbox database is offline;

I have asked users of domain A to delete their autocomplete files and rewrite the addresses of users at domain B but they seem to still be getting the same message

I have removed domain B as an accepted domain in the ECP on the Exchange server that domain A is still on but this has made no difference.

We don't want to delete the database for Domain B until we are sure it is definitely not required and that all historic emails are completely moved over to the new server.

Can you advise what we need to do so that when users of Domain A send an email to Domain B the message does not stay local and goes outside of the exchange server rather than staying internal.

Question by:purpleoak
  • 2

Expert Comment

ID: 41886744
Under Organization configuration. Do you have Domain B set up as a Remote Domain and Accepted Domain in Hub Transport? Also are your connector IP's correct under Server Config - Hub Transport?

Accepted Solution

purpleoak earned 0 total points
ID: 41887574

I believe I have found the solution in that the original mailboxes still had for Domain B still had some aliases configured that related to domain B, After removing these and sending test emails again I can see the mail is going from Domain A over to Domain B on the new server correctly.

Author Closing Comment

ID: 41894079
After further investigation my side I found that the mailboxes still had some data connected to them from the original setup of domain B therefor I have managed to solve the problem myself.

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

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

After a recent Outlook migration from a 2007 to 2010 environment, some issues with Distribution List owners were realized. In this article, I explain how that was rectified.
Disk errors can be the source of sundry problems for the Exchange server, the most common one being that the database fails to mount.
Many of my clients call in with monstrous Gmail overloading issues with Outlook. A quick tip is to turn off the All Mail and Important folders from synching. Here is a quick video I made to show you how to turn off these and other folders in Gmail s…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…

586 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question