?
Solved

Exchange 2010 -> 2016 Migration:  internal Mailfow

Posted on 2016-11-20
3
Medium Priority
?
100 Views
Last Modified: 2016-11-20
Hi,

I know this has been talked about a million times and more, but I can't find my error in this one:

Exchange 2010 SP3 on Server 2008 (R1) hosting roughly 450 mailboxes alone.  New VM 2012 R2 running Exchange 2016 CU3 just installed into the domain.  All seems well.

I can mail from 2010 to 2016, but not the other way.  The messages stall in the queue on the 2016 box with this message:

[{LRT=20.11.2016 12:50:01},{LED=451 4.4.0 Target host responded with: "451 5.7.3 Cannot achieve Exchange Server authentication." Last endpoint attempted was 192.168.5.104:25};{FWDN=internal.domain.local};{192.168.5.104}]

The IP is the one of the old box.  I checked the receive connectors and disabled Exchange Server authentication on every one.  I also checked the send connectors on the 2016 box and disabled it there.

Where else can I look?
0
Comment
Question by:Ralph Scharping
  • 2
3 Comments
 
LVL 3

Accepted Solution

by:
Pune Tech earned 2000 total points
ID: 41894749
Please refer following article to fix this issue

http://www.petenetlive.com/KB/Article/0000791
0
 
LVL 2

Author Closing Comment

by:Ralph Scharping
ID: 41894784
Looks like what I missed was a restart of the transport service...
0
 
LVL 3

Expert Comment

by:Pune Tech
ID: 41894871
Thanks for the update and points.
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Question has a verified solution.

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

In this article, I will demonstrate that how to do a PST migration from Exchange Server to Office 365. This method allows importing one single PST, or multiple PST's at once.
In my humble opinion (IMHO), TouchDown from Symantec is the best in class for this type of application, but Symantec has end-of-lifed it and although one can keep using it, it will no longer be supported or upgraded.  Time to look for alternatives t…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
In this video I will demonstrate how to set up Nine, which I now consider the best alternative email app to Touchdown.

588 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