NDRs generated on Master sever in Site-A not recived by user homed on Member server in Site-B

User homed on Member Exchange 2K3 in Site-B sends message to an internet recipient, message goes to Master server in Site-A and is not delivered to recipient, an NDR is generated but it never makes it back to user in Site-Bs mailbox, even though Message Tracking says it did.  All other email between both sites is working fine, and to and from the internet.  Both servers are part of same domain, different sites with domain controllers at both sites AD DNS at both sites running Exchange 2K3 SP1, on Windows 2K3 servers in an 2K3 AD domain.  This is my first post.  Let me know if I need to supply more information.  Thank you.
Ascend-AdminAsked:
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.

gpriceeeCommented:
Hi.  If this is only affecting one user, on the workstation, remove the Outlook profile and recreate a new one.  Then send a message.
Ascend-AdminAuthor Commented:
It affects all users on that server.  We created a test account and can log in and duplicate it from here.  We do have another member server here at Site-A also.  I have not heard any complaints from anyone useing it, neither have I had time to test it from that server.
gpriceeeCommented:
Is the server that's unable to deliver external email included in the bridgehead list in the SMTP connector?

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
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

Ascend-AdminAuthor Commented:
I only fails to deliver to this one domain and since we cant get to the NDR we dont know why.  Trying to send to a non-existant domain results in the same problem, NDR is generated, Message Tracking shows it being sent back to the users mailbox, but it never appears.
Ascend-AdminAuthor Commented:
And yes the Master server is the Local Bridgehead server.
gpriceeeCommented:
Is the Is Member Exchange 2K3 in Site-B a bridgehead for the connector?
Ascend-AdminAuthor Commented:
Only the Site-A Master server is listed as a local bridghead server under the default routing connector.
SembeeCommented:
If message tracking shows that the NDR was delivered to the server then something is eating the NDR.
Antivirus or Antispam would be the first thing to look at.

Simon.
gpriceeeCommented:
Go to your virtual server in Site-A
Messages Tab
In Forward all mail with unresolved recipients to host, enter the FQDN of the server in Site-B
Ascend-AdminAuthor Commented:
Can I put both the SiteB and SiteC servers in there?  Seperated by a ;  ?
gpriceeeCommented:
In site B, put site C.
SembeeCommented:
Just going through some of the old outstanding questions as it is quiet...

Has this problem been resolved?
If you need clarification on any part of the responses above, please post back.

Otherwise you need to close the question by awarding points, or posting in the Support Topic Area (top right corner) with a link to this question asking for the moderators to close the question for you without awarding points.

Simon.
Ascend-AdminAuthor Commented:
I appologize for the delay, we found the problem.  It was a setting in the SMTP connector.  The first 2 servers setup had the connector renamed to our outside domain name, the new one was still default named as our internal domain.  NDRs apparently have to be delivered to a connector of like domain name.  Once all 3 matched the problem went away.  I cant count how many times I looked at these connectors and never noticed they were different.  But everything else was working ok between them, just not NDRs.  I had run the Microsoft Exchange SMTP test utility against it several times from all the servers and it allways reported no problems found, SMTP conneciton and lookup in all forms passed.  The first two servers were setup within a short time from each other but the third was a year later.  Yet another reason to allways document all changes made to systems so it can be refered to later when adding a new like system.  Thank you all for your suggestions.  Is there a way I can split the results among the pople who attempted to help?
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
Exchange

From novice to tech pro — start learning today.