The Receive Connector already exists by default when
the Edge Transport role is installed.
Figure 9-11
Chapter 9: Confi guring the Edge Transport Server Role
253
See Figure 9 - 15 in the next section for connectors created on the Hub Transport server after edge
subscription is imported. Keep in mind that an implicit Send Connector from the Hub Transport servers
that are in the same forest as the Edge Transport server is also created so all the Hub servers know how
to route outbound Internet mail to the Edge Transport server.
Preparing the Hub Transport Server
The actual steps required to prepare the Hub Transport server vary depending on whether edge
subscription and EdgeSync will be performed. It is highly recommended that you use edge subscription
and EdgeSync to subscribe the Edge Transport server to an Active Directory site in the Exchange
organization because this automates and simplifies the configuration on both the Edge and Hub
Transport servers.
First consider the scenario where edge subscription and EdgeSync will not be performed. In this case,
to prepare the Hub Transport server, you should perform the following tasks:
1. Ports: Verify that the perimeter network firewall that separates the Edge Transport server
from the Exchange organization is configured to enable SMTP communications on port 25.
Pages:
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365