exchange 2003 mailbox move, unable to connect to mailbox once moved.

I have moved a user from server2 to server1. Server 1 and server2 are at different locations. I initiated the move on server 2.
Looking at the ESM (exchange system manager) and expanding the server, storage group and looking at mailboxes i can see the mailbox now exists on server1 and not server2.
When using 'active directory users and computers' on server 1and looking at the exchange properties of the user the mailstore is apparantly on server2. Doing this on server2 says that the mailbox is on server1.

The client is unable to connect to exchange even if I re-create the profile locally on the pc or use webmail to connect.
The client can talk to the machine ok and resolve FQDN ping etc.

I have also done an update on GAL and offline address book.

I also tried to do a move for the mailbox back and this failed (initiated from either server)

I cannot restart the mailstore as there are too many people on at the moment and this is scheduled for tonight just in case.
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.

I think a remount of your database will do the trick. You also can try to disconnenct the mailbox and reconnect it for that particular user...
After the disconnection of the mailbox, don't forget to run the Clean-MailboxDatabase command. Or else it will take a while before you can reconnect the mailbox.
I think it's wise to first export/backup the mailbox before doing this (because of the strange behaviour right now)


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
q2qAuthor Commented:
I backed up the mailbox. deleted it created on the correct server and re-imported from backup. Job worked in 3 mins!
Good to hear it worked. But did you reconnect the existing mailbox, of create a new one.
If you created a new one, it's wise to set the Legacy Exchange DN as an X500 address on the mailbox....
The Legacy Exchange DN can be found in the disconnected mailbox, or in someone's Outlook Cache file....
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

q2qAuthor Commented:
I recreated a new one. What is the legacy excchange dn used for? At the moment emais are flowing OK.
The legacy Exchange DN is used by Outlook clients to send mail (when using cache) and when replying to old mail, it also uses the Legacy EDN. Users outside the company don't notice it when changed.
If the users select the user from the address book all is fine and the new Legacy EDN is cached in the NK2 file.
Here is an explenation:
If you look at an NK2 file of a user that mailed to the old mailbox, you see something like:
If you add this (custom) address as an X500 address, all mail will be delivered to the mailbox...
q2qAuthor Commented:

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.