Creating a Custom HubTransport Connector on Exchange 2013 Multirole Server Results in:
421 4.3.2 Service not available
Connection to host lost
[floated align=”left”]Exchange 2013 Upgrade[/floated]In [tip label=”Part 1” style=”1″ href=”https://www.netometer.com/video/tutorials/How-to-Upgrade-Exchange-2007-to-Exchange-2013″]Screencast: How to Upgrade Exchange 2007 to 2013 P1 
[/tip] and [tip label=”Part 2” style=”1″ href=”https://www.netometer.com/video/tutorials/How-to-Upgrade-Exchange-2007-to-Exchange-2013-Part2″]Screencast: How to Upgrade Exchange 2007 to 2013 P2 [/tip] of our Exchange 2007 to 2013 upgrade Screencast, we demonstrate step-by-step the whole upgrade process. In a series of short videos, we will cover some of the most common mistakes, warnings and errors that you might get during this upgrade.
In this video we demonstrate one of the common problems that you might hit when creating new (or re-creating existing Exchange 2007) Custom Receive Connectors in Exchange 2013 Multirole Servers. In our example, we are creating a Custom Relay connector which allows relaying for a specific internal host/application. The problem occurs when you choose the “HubTransport role” for the connector type. In this case, the Default Frontend connector, which is the common messaging entry point for the organization, closes connections from remote email servers with “421 4.3.2 Service not available” and effectively rejects accepting inbound e-mails. As you can see, the solution is to delete the Custom HubTransport Receive connector and re-create it again as a FrontendTransport connector.
- “Discovery Search Mailbox has been corrupted” error when upgrading from Exchange 2007 to Exchange 2013
- How to Bulk Create Mailboxes in Exchange 2013
- How to Install Exchange 2013
- How to Install WordPress on Windows Server 2012