This essentially means that this connector will route mail for any authoritative domain or
internal relay domain configured for the organization. The smart host configured for this Send
Connector will be one or more Hub Transport servers in the Exchange organization. The source
bridgehead as usual will be the Edge Transport server but it is not specified. This is shown in
Figure 9 - 5 .
Figure 9-5
6. Receive Connector from Hub Server(s): Finally, because this scenario does not use edge
subscription and EdgeSync, it is recommended that you create another Receive Connector on
the Edge Transport server other than the default. The default Receive Connector has a usage
Chapter 9: Confi guring the Edge Transport Server Role
249
type of Internet, which means it can accept anonymous connections. If edge subscription was
used, the EdgeSync process would be able to negotiate the authentication seamlessly. However,
because this is a manual configuration, you would need to create a Receive Connector of usage
type internal. It must be bound to the internal network adapter of the Edge Transport server.
This connector is shown in Figure 9 - 6 .
Figure 9-6
The Receive Connector is bound to the internal adapter with an IP address of 172.16.8.55 and allows all
Hub Transport servers in the remote IP range to connect to the Edge Transport server.
Pages:
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360