Exchange routing problem.

I have a customer with an Exchange 2003 server.  They had two domain names in the box (domain-1.com and domain-2.com).  The company spun off the domain-2 division which is now at a different location and has their own seperate server.  

I have rebuilt the address books and ensured that all references in exchange to domain-2.com have been removed.

If domain-2.com sends an email to a user at domain-1 it gets there no problem.   If a user at domain-1.com emails to a user at domain-2.com it failed with a mail account does not exist at the organization.
LVL 8
SanDiegoComputerAsked:
Who is Participating?
 
Computer101Connect With a Mentor Commented:
PAQed with points refunded (500)

Computer101
EE Admin
0
 
Hypercat (Deb)Commented:
Have you checked all recipient policies to make sure that domain-2.com is not still being applied to any accounts and is not referenced in any way?  Even if it's not checked in the policy, you should delete all references to it, otherwise the server may still see itself as responsible for the domain-2.com email.
0
 
SanDiegoComputerAuthor Commented:
I did verify that it is not in the recipient policy.  Also, we went through all local email addresses to ensure that the accounts on domain-1.com don't have any references any more to domain-2.com
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Hypercat (Deb)Commented:
How about DNS?  Could there be any references to domain-2.com left on your DNS servers?  Also, try clearing the DNS cache by typing "ipconfig /flushdns" and then "ipconfig /registerdns" at the command prompt on the Exchange server and see if that helps.
0
 
SanDiegoComputerAuthor Commented:
no.  DNS points properly.  Also, this change was made months ago so the cache has certainly cleared by now.

0
 
Hypercat (Deb)Commented:
Aha, I was thinking it was something that happened recently.  So, does this happen with all of the domain-2.com addresses? And are you sure the error is being generated by your server and not the server at domain-2.com?
0
 
SanDiegoComputerAuthor Commented:
The response that we get is from the server at domain-1.com.  It does happen with any email sent from any email address at domain-1.com to any at domain-2.com

0
 
Hypercat (Deb)Commented:
You could try tracking this through increasing the level of diagnostic logging on your server temporarily and then sending a test email to one of these addresses.  I would recommend going into the registry and changing the diagnostic settings for all of the Exchange services temporarily to "7" and then send a test email.  This is the "field engineering" level of diagnostics (highest you can go) and can only be set through editing the registry.  Here's an explanation of how to do this:

http://support.microsoft.com/kb/555232/en-us

Hopefully this will give you a good trace of what exactly is happening to the message.
0
 
SanDiegoComputerAuthor Commented:
It looks like it's never getting to the smtp service.  My guess is there is something somewhere in the server that is still pointing to domain-2.com.  I just can't figure out where that might be.
0
 
Hypercat (Deb)Commented:
I think you're right, but it sounds like you've checked everything pretty thoroughly.  How about any Mailbox Management policies?
0
 
SanDiegoComputerAuthor Commented:
Problem wound up being invalid entries pointing to the old domain still in the IIS metabase.
0
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.

All Courses

From novice to tech pro — start learning today.