Forum Discussion
Anton5032
May 29, 2020Copper Contributor
Hybrid Exchange change of SMTP relay connector
Hi All So we have Hybrid Exchange environment, with few 2010 Exchange boxes on-prem, 1x Exchange 2016 on-prem (as the hybrid) and O365 tenant. Until now we were using one of the EX2010 boxes as ...
- Jun 02, 2020
Whenever I setup a connector for this purpose on an Exchange 2016 Server, I always set the security tab options as follows;
I would definitely double and triple check your firewall rules too. Do you definitely have the Exchange Online IP's all allowed for the Exchange 2016 server?
PeterRising
May 29, 2020MVP
Hmm, that's interesting. Are you able to share a screenshot of the receive connector you have created on your Exchange 2016 server please?
Also, could you share the socket error you are seeing too?
Anton5032
Jun 02, 2020Copper Contributor
PeterRisingthanks for the reply
this is the receive connector (screenshot) and under security we have marked ONLY - Anonymous
Scoping is the internal printer network
Looks like the receive connector on the Exchange 2016 is ok, but then if try to open SMTP 25 to Outlook.office.com from the Exchange 2016 all I am getting is blank screen and nothing else. When I try to do the same from the old 2010 Exchange box it all works perfectly. As I said on the FW both boxes have identical rules. Not sure why EXCH2016 -> Outlook.office.com:25 not working
- PeterRisingJun 02, 2020MVP
Whenever I setup a connector for this purpose on an Exchange 2016 Server, I always set the security tab options as follows;
I would definitely double and triple check your firewall rules too. Do you definitely have the Exchange Online IP's all allowed for the Exchange 2016 server?
- Anton5032Jun 02, 2020Copper Contributor
THANK YOU!
That definitely did the trick, although now it looks like whoever created the send connector didnt do the work right - it is only relaying emails to internally and if try to send externally (ie: gmail) - nothing happens.
I can see there is a separate send connector for that 2016 box and another one which serves the on-prem (which obviously works fine at the moment). So, I am not sure how the 2016 send must looking.
Current config:
delivery:
Route via smart hosts (address of our securemx)
Smart host auth: NONE
Scoping:
Address Space - SMTP *
Source server: ADDRESS of the 2016 Exch box
Any help will be greatly appreacited!
- Anton5032Jun 04, 2020Copper Contributor
Found the problem!
FW issue - someone forgot to fix the src ip masq and the requests were going with the default ext ip instead the dedicated one
Thanks for the help!