Emails being Explicitly Discarded in Exchange 2013 DAG (HADISCARD)

30-09-2015-6-17-33-PM.jpg
Hi,
I am seeing messages Discarded after being delivered to 1 DAG member, and then transferred to the other (The one containing the active mailbox)

I have a NLB doing round robin. Here's the scenario:
UserA is on DBA which is active on EXA
The email comes in and gets delivered to EXB via the NLB
EXB then forwards/transmits/replicates the message to EXA
For whatever reason EXA discards the message

Any ideas why this is happening? This is what I'm assuming is happening. Please correct me if I'm wrong.
LVL 1
tzadminAsked:
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.

Aurel VacalieCommented:
Hello,

Do you use custom receive connector ar the default ones?
If custom, check the limit for number of messages for one source.
0
tzadminAuthor Commented:
I set it to 100 which seems to be the max. What is the default receive connector set to? I assume it's also 20 which means I would have had the same issue.
What happens if I'm using a security appliance? All connections would be coming from one place. This limitation doesn't make sense to me.
0
tzadminAuthor Commented:
I believe that the Exchange servers use the "Default <Servername>" connector to intra-org transmissions which is set to Unlimited Connections from a single source by default.

The HADISCARD messages I've been seeing appear to be from the Shadow Redundancy process.

HADISCARD: A shadow message was discarded after the primary copy was delivered to the next hop.

I don't see anything in event viewer about messages being rejected from MSExchangeTransport so I don't believe there's an issue with my connectors.
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
tzadminAuthor Commented:
Not a receive connector issue although the information is still valuable.
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
Exchange

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.