Exchange 07 to 2013 Mail Flow Issue

I am in the middle of a migration from Exchange 07 to 2013.  I have installed 2013 and just moved my first TEST user.  I do not have my SSL certificate yet, so I am testing via 2013 OWA.

From the 2013 Test Account I can successfully send mail outside the organization & receive the reply, BUT I cannot send mail internally to ANY of the users residing on the Exchange 07 server.

If I send mail from an existing user on the 2007 server to the TEST account residing on the 2013 server it is successful.

What am I missing? Why can I not send mail internally from 2013 to 2007?
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 GudgerSolution ArchitectCommented:
Normally this is a result of something on the 2007 Receive Connectors.

More often that not the IP of the 2013 server is not permitted to relay through the 2007 connectors.

The other possibility is that the IP of the 2013 server is included as part of a network range on a Receive Connector with the wrong permissions. For example, you configured an anonymous relay for application and device relay on the 2007 server and it includes the IP of the 2013 server. When the 2013 server tries to use this connector it fails.

The telltale sign of these is to check the Queue Viewer in Exchange 2013 and see what the Last Retry column says. If it makes any reference to authentication problems then it is the above.
BSModlinAuthor Commented:
Which receive connector on the 2007 server would it be?  Client, Default, or Internal Relay Connector?
BSModlinAuthor Commented:
Can you please be a bit more specific?
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Gareth GudgerSolution ArchitectCommented:
Client and Default are the out of the box receive connectors. I would start with the Internal Relay Connector. This would have been created after the install.

Check the Scope tab of that connector and see if it includes the IP of the Exchange 2013 server. It could be included as either an IP or even as part of a network range.

We need to make sure the Exchange 2013 server's IP is not in that scope for that connector.
BSModlinAuthor Commented:
The scope is from -, which dies include the new exchange server.

So what should I do? Howndo I edit it... Delete the entire entry? Leave it blank??
Gareth GudgerSolution ArchitectCommented:
You could create two network ranges instead of one.

So, if your Exchange server is for example, delete the current range.

Then create two around it. -
and -

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
BSModlinAuthor Commented:
After making that change I receive an Undeliverable when emailing from the test mailbox on the 2013 exchnge server to a mailbox on the exchage 2007 server.  Here is the error message in the Undeliverable:

#550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionNamedPropsQuotaExceeded:16.18969:47010000, 17.27161:00000000AC000000000000000000000000000000, 255.23226:3C110000, 255.27962:7A000000, 255.27962:56000000, 255.17082:00090480, 0.16993:80030400, 4.21921:00090480, 255.27962:FA000000, 255.1494:00000000, 255.26426:56000000, 4.6363:0F010480, 2.31229:00000000, 4.6363:0F010480, 2.22787:00000000, 2.22787:00000000, 2.22787:00000000, 4.5415:00090480, 4.7867:00090480, 4.4475:00090480, 4.4603:00090480, 4.5323:00090480, 255.1750:00090480, 0.26849:00090480, 255.21817:00090480, 0.24529:00090480, 4.18385:00090480". ##
Gareth GudgerSolution ArchitectCommented:
Can you check what the error is in the Retry column on the 2013 side in the Exchange Management Toos >> Queue Viewers
BSModlinAuthor Commented:
There is nothing in he Queue..... Empty... I just receive an undeliverable with the message above...
BSModlinAuthor Commented:
Any additional help?  I am in the middle of migration and stuck.... I am getting the message above when sending from 2013 to 2007.
Gareth GudgerSolution ArchitectCommented:
Try restarting the Transport Service on the 2007 box.
BSModlinAuthor Commented:
I did....
BSModlinAuthor Commented:
I rebooted both servers completely as well... Still nothing.....
Gareth GudgerSolution ArchitectCommented:
Can you temporarily disable the Internal Receive Connector for testing and see what happens? Then try to resend. Let me know what error you see in the Queue Viewer in the Retry Error column.
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

From novice to tech pro — start learning today.