Hybrid Configuration

%3CLINGO-SUB%20id%3D%22lingo-sub-875253%22%20slang%3D%22en-US%22%3EHybrid%20Configuration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-875253%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20a%20new%20configuration%2C%20we%20have%202016%20CU11%20on-prem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHaving%20issues%20with%20the%20O365%20Hybrid%20Config.%3CBR%20%2F%3Ewe%20are%20able%20to%20send%20from%20our%20migrated%20test%20account%20that%20is%20in%20the%20cloud%20to%20both%20to%20internal%20users%20(on%20prem)%20and%20external%20users%20(google)%2C%26nbsp%3Bhowever%2C%20we%20are%20not%20able%20to%20receiving%20from%20any%20source%20into%20our%20migrated%20test%20account%20in%20the%20cloud.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20Full%20Hybrid%20configuration%20with%20the%20Classic%20topology%20in%20place%20and%20are%20not%20using%20centralized%20mail.%20We%20also%20have%20a%20valid%203rd%20party%20SSL%20cert%20loaded.%3CBR%20%2F%3EI%20have%20added%20network%20range%20for%20our%20WAN%20edge%20to%20both%20the%20Protection--%26gt%3BConnection%20filter%20and%20the%20O365%20inbound%20connector%3CBR%20%2F%3ECurrently%20we%20have%20the%20O365%20connector%20set%20to%20verify%20connection%20by%20certificate%20(3rd%20party%20from%20above)%2C%20but%20have%20also%20tried%20adding%20network%20range%20to%20inbound%20connector%20as%20well.%3C%2FP%3E%3CP%3EI%20turned%20on%20the%20on-prem%20servers%20send%20connector%E2%80%99s%20logging%20to%20verbose%20and%20this%20is%20what%20is%20being%26nbsp%3B%20logged%20no%20matter%20the%20changes%20I%20make.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2019-09-25T18%3A23%3A09.282Z%2COutbound%20to%20Office%20365%2C08D741D487D8E263%2C0%2C%2C104.47.66.10%3A25%2C*%2CSendRoutingHeaders%2CSet%20Session%20Permissions%3CBR%20%2F%3E2019-09-25T18%3A23%3A09.282Z%2COutbound%20to%20Office%20365%2C08D741D487D8E263%2C1%2C%2C104.47.66.10%3A25%2C*%2C%2Cattempting%20to%20connect%3CBR%20%2F%3E2019-09-25T18%3A23%3A10.284Z%2COutbound%20to%20Office%20365%2C08D741D487D8E263%2C2%2C%2C104.47.66.10%3A25%2C*%2C%2C%22Failed%20to%20connect.%20Winsock%20error%20code%3A%2010061%2C%20Win32%20error%20code%3A%2010061%2C%20Destination%20domain%3A%20*tenantname*.mail.onmicrosoft.com%2C%20Error%20Message%3A%20No%20connection%20could%20be%20made%20because%20the%20target%20machine%20actively%20refused%20it%20104.47.66.10%3A25.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20suggestions%20would%20be%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-875253%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%20Network%20Connectivity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn-Premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
New Contributor

This is a new configuration, we have 2016 CU11 on-prem.

 

Having issues with the O365 Hybrid Config.
we are able to send from our migrated test account that is in the cloud to both to internal users (on prem) and external users (google), however, we are not able to receiving from any source into our migrated test account in the cloud.

 

I have a Full Hybrid configuration with the Classic topology in place and are not using centralized mail. We also have a valid 3rd party SSL cert loaded.
I have added network range for our WAN edge to both the Protection-->Connection filter and the O365 inbound connector
Currently we have the O365 connector set to verify connection by certificate (3rd party from above), but have also tried adding network range to inbound connector as well.

I turned on the on-prem servers send connector’s logging to verbose and this is what is being  logged no matter the changes I make.

 

2019-09-25T18:23:09.282Z,Outbound to Office 365,08D741D487D8E263,0,,104.47.66.10:25,*,SendRoutingHeaders,Set Session Permissions
2019-09-25T18:23:09.282Z,Outbound to Office 365,08D741D487D8E263,1,,104.47.66.10:25,*,,attempting to connect
2019-09-25T18:23:10.284Z,Outbound to Office 365,08D741D487D8E263,2,,104.47.66.10:25,*,,"Failed to connect. Winsock error code: 10061, Win32 error code: 10061, Destination domain: *tenantname*.mail.onmicrosoft.com, Error Message: No connection could be made because the target machine actively refused it 104.47.66.10:25."

 

Any suggestions would be appreciated.

0 Replies