Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 199
  • Last Modified:

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?
0
BSModlin
Asked:
BSModlin
  • 8
  • 6
1 Solution
 
Gareth GudgerCommented:
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.
0
 
BSModlinAuthor Commented:
Which receive connector on the 2007 server would it be?  Client, Default, or Internal Relay Connector?
0
 
BSModlinAuthor Commented:
Can you please be a bit more specific?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Gareth GudgerCommented:
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.
0
 
BSModlinAuthor Commented:
The scope is from 10.1.10.1 - 10.1.10.255, which dies include the new exchange server.

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

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

Then create two around it.

10.1.10.1 - 10.1.10.49
and
10.1.10.51 - 10.1.10.255
0
 
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". ##
0
 
Gareth GudgerCommented:
Can you check what the error is in the Retry column on the 2013 side in the Exchange Management Toos >> Queue Viewers
0
 
BSModlinAuthor Commented:
There is nothing in he Queue..... Empty... I just receive an undeliverable with the message above...
0
 
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.
0
 
Gareth GudgerCommented:
Try restarting the Transport Service on the 2007 box.
0
 
BSModlinAuthor Commented:
I did....
0
 
BSModlinAuthor Commented:
I rebooted both servers completely as well... Still nothing.....
0
 
Gareth GudgerCommented:
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.
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 8
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now