The Best Damn Exchange, SQL and IIS Book Period

We assume that most organizations will create an edge subscription for the Edge Transport servers they choose to deploy in their perimeter network (DMZ or screened subnet). Since the EdgeSync service will automatically create the connector necessary to get a mail flow established to and from the Internet and to and from the Hub Transport server in the Exchange organization, no additional post-tasks are necessary regarding connectors; they will be replicated from the Hub Transport server to the Edge Transport server. But if for some reason you choose not to use an EdgeSync subscription, you ll need to create these connectors manually. The Edge Transport server will need four connectors: two receive connectors (one is created during the installation of the Edge Transport server) and two send connectors.
Since the Edge Transport server is located in the perimeter network (the DMZ or screened subnet), we assume that you have installed two network adapters in the server so that you can bind one receive connector and one send connector to the internally configured network adapter and one receive connector and one send connector to the externally configured network adapter.
To create and configure the required connectors, follow these steps:
Create a Send connector that is configured to send messages to the Internet. To do so, log on to the Edge Transport server, open the EMC, and click Edge Transport in the navigation tree.
Now select the Edge Transport server in...