Exchange 2013. Have 2 domains. One cannot recieve inbound mail.

I have a new Exchange 2013 server.  It's running on Hyper-V with the host and 4 servers.
- Domain controller ABC.com
-Child domain controller DEF.com
-Exchange server
-Remote client

The client has two companies and want's the two domains.  I've added the second email domain as authoritive on the exchange server.  I've added users on both domains with email boxes for each user.  Both domains have their mx records pointed to McAfee's MXLogic servers and then test to the exchange server ok.  The primary domain is receiving email but the second domain is not.  I'm looking on the MXLogix server and that domain's email is being spooled and cannot deliver.  I know the MXLogic server works in this environment because it was working on our old system.

How do I figure out why it's not being delivered?

Thanks!
MOBlewAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

arnoldCommented:
Are both domains reflected withi exchange 2013 as accepted domains, are there users that have email address on each or both?

Check transport rules.

What happens when you connect to the exchange and send an email to the domain (make sure you connect from a source not configured to relay)

Does the second domain on mxlogic configured to send to the new exchange? I.e. It points to the same ip as the one that works?
MOBlewAuthor Commented:
Thanks for you attention Arnold...

Both are accepted domains

Both domains  have users on them

There are no transport rules

Internally you can send emails between domains

Yes it's configured to the same IP that works and it passes the continuity test.

Thanks again for your input...
MOBlewAuthor Commented:
Resolved...

I'm not sure why but after 2 days it just started working...

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
arnoldCommented:
Glad to hear, it might have been that the queue on the mxlogic side was such that it took the changes this long to propagate.
MOBlewAuthor Commented:
It just started working...
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.