Solved

Cannot send email from Exchange 2013 to Exchange 2010 within the same organization

Posted on 2014-10-02
5
2,654 Views
Last Modified: 2014-10-06
Hi guys,
I'm in the middle of migrating my users from exchange 2010 to exchange 2013 and i need help with one issue I'm having with my Exchange 2013 sending. I have successfully installed 2013 (per Microsoft migration guide), I have also followed the migration post installation procedures and I've successfully moved one of the mail boxes to 2013 from the 2010 server.

Problem:
I cannot send internal emails (within the same Exchange organization) from the 2013 mailbox to any of the exchange 2010 mail boxes. But I have no problem sending emails from exchange 2010 mailboxes to  the exchange 2013 mail box. I'm also able to send external emails from the same exchange 2013 mail box to internet email addresses after I've created an smtp send connector.

Here is a sample of the delivery email report I get ==========
==============================================================

"
This message hasn't been delivered yet. Delivery will continue to be attempted.
The server will keep trying to deliver this message for the next 1 days, 19 hours and 51 minutes. You'll be notified if the message can't be delivered by that time.






Diagnostic information for administrators:
Generating server: CG-EXCH2013.mydomain.ca
Receiving server: CG-EXCH2010.mydomain.ca (192.168.1.2)
myemail@mydomain.ca
Remote Server at CG-EXCH2010.mydomain.ca (192.168.1.2) returned '400 4.4.7 Message delayed'
10/2/2014 7:40:18 PM - Remote Server at CG-EXCH2010.mydomain.ca (192.168.1.2) returned '451 4.4.0 Primary target IP address responded with: "451 5.7.3 Cannot achieve Exchange Server authentication." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 192.168.1.2:25'
Original message headers:

Received: from CG-EXCH2013.mydomain.ca (192.168.1.22) by
 CG-EXCH2013.mydomain.ca (192.168.1.22) with Microsoft SMTP Server (TLS) id
 15.0.847.32; Thu, 2 Oct 2014 11:42:11 -0400
Received: from CG-EXCH2013.mydomain.ca ([fe80::5833:4ace:9096:337]) by
 CG-EXCH2013.mydomain.ca ([fe80::5833:4ace:9096:337%12]) with mapi id
 15.00.0847.030; Thu, 2 Oct 2014 11:42:05 -0400
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: u1-ex2010 <sender1@mydomain.ca>
To: Mohammed Ali <myemail@mydomain.ca>
Subject: test90
Thread-Topic: test90
Thread-Index: AQHP3ldqrHq4pepDf0C6VLIoDMJrcw==
Date: Thu, 2 Oct 2014 11:42:05 -0400
Message-ID: <da4e62cb6f6044ceb11449f4a4c0f2b2@CG-EXCH2013.mydomain.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <da4e62cb6f6044ceb11449f4a4c0f2b2@CG-EXCH2013.mydomain.ca>
MIME-Version: 1.0
X-Originating-IP: [192.168.1.151]
Return-Path: sender1@mydomain.ca"
0
Comment
Question by:M Ali
  • 2
  • 2
5 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40358224
Check the receive connector configuration on the Exchange 2010 server.
The default connector is usually used and you need to ensure that Exchange server is enabled as an authentication type. After making changes, restart the Microsoft Exchange transport service to get the change to take.

Simon.
0
 

Author Comment

by:M Ali
ID: 40360058
The Exchange server is enabled as an authentication type on the default receive connector in  my exchange 2010 server,
I'm wondering whether I need to add a separate send connector on the exchange 2013 ?
0
 
LVL 31

Accepted Solution

by:
Gareth Gudger earned 500 total points
ID: 40360886
Simon is correct. This is normally a problem with the 2010 receive connector.

One other thing to check. On the 2010 side, do you have any additional receive connectors that were created for application relay for example?

Exchange 2010 only comes with two default receive connectors. Client and Default. If you have any others check their IP scoping. Make sure they don't include the IP of the 2013 Exchange server. If so, Exchange maybe trying to use a receive connector with an authentication scheme it cant use.

A common cause is that the Exchange servers IP was included as part of a network range in the IP scope.
0
 

Author Comment

by:M Ali
ID: 40363703
Good call!!

This is actually what it was ...I had another  receive connector for SMTP relay, scoped to only accept emails from an IP  range that happened to include the IP address of Exchange 2013.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40363780
Awesome. Yea I have been seeing that a lot recently with 2010 >> 2013 migrations.
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…

837 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question