Exchange 2003 mailbox issues

Customer is running exchange 2003, they had a unrecoverable server failure, restored their system from an image backup to a VMware host. I had to clean the public datastore but the private looked clean. I did run a defrag on it anyway. Emails are working for some but not most employees. Initially the issue was they could send but not receive emails from outside the network but now it appears some cannot send internal emails, getting this message..."was rejected due to the current administrative policy by the destination server". I believe exporting the mailbox manually to pst and recreating the mailbox and reimporting the pst resolves the ability to receive outside emails issue. Exmerge and scanpst fail to work in every case, there are over 300 mailboxes.

I'm kinda stuck not sure where the issue lies with internal rejection, is it a spam filter, information store issue, etc...the logs look okay.
BERITMAsked:
Who is Participating?
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.

Gareth GudgerCommented:
Hey Bertim,

So, to not assume. Your private database mounted fine.

What happens if you reboot the server? Does mail previously stuck in the queue get delivered?

What is the error you see in the Queue?

Best regards,

Gareth
0
BERITMAuthor Commented:
I have not rebooted it, the local queue only shows external emails intended for internal recipients, resolved that issue by rebuilding the affected mailboxes.

Internal queue states "message scheduled to retry categorization"

outbound queue:
Unable to bind to the destination server in DNS
and
The remote server did not respond to a connection attempt
0
Gareth GudgerCommented:
Hey Bertim,

Try downloading and running the Exchange Best Practice Analyzer to see if it brings up any issues.
http://www.microsoft.com/en-us/download/details.aspx?id=22485

Sounds like to me that Exchange either can't contact DNS and/or as a result can't contact a Domain Controller/Global Catalog server.

From the Exchange server can you perform NSLOOKUP tests fine?

Can the Exchange server ping a DNS server. Or DC/GC by FQDN?

Check this article from Microsoft. Specifically the section titled "Verify that the global catalog server is available"
http://support.microsoft.com/kb/251746/en-us
0
BERITMAuthor Commented:
It's an issue with the mail server and AD account/mailbox, since new mailboxes work properly. Exporting their mailbox and rebuilding them is only option. I'm able to get ExMerge working so at least I have this tool to make the process somewhat easier.
0

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
BERITMAuthor Commented:
No tools available to repair the server/AD corruption - only option is rebuild the mailboxes and restore the data.
0
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
Email Servers

From novice to tech pro — start learning today.

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.