If you would like to read the other parts in this article series please go to:
- Configuring Edge Transport Server Without Edge Synchronization (Part 1)
- Configuring Edge Transport Server Without Edge Synchronization (Part 3)
- Configuring Edge Transport Server Without Edge Synchronization (Part 4)
This is the second part of a four-part article series on configuring Internet email flow through a Hub Transport and Edge Transport configuration that is not using the Edge Synchronization feature. In part one I described the basic lab environment that I am using and went on to commence the configuration of the Send Connector required to send outbound Internet email messages towards the Edge Transport server. Without further ado, let us continue the configuration of this connector, picking up from where we left off. We had just completed the opening page of the New SMTP Send Connector wizard and clicked Next.
Hub Transport Send Connector (Continued)
1. The Address space page of the wizard will now be displayed. This will allow you to configure the destination domain names of messages that will be processed by this connector. Since we require this connector to process all messages to the Internet, the typical address space entered is simply the star character (*). It is possible to specify specific domain names here, such as contoso.com. In this case, this Send Connector would only process messages addressed to users at contoso.com, such as [email protected]. To complete the configuration of the Address space page, follow these steps:
a. Click the Add button which will bring up the SMTP Address Space window.
b. In the Address field, type *.
c. Leave the Include all subdomains check box clear. Since we are interested in processing messages addressed to all Internet domains, this check box is of no interest to us. However, going back to the previous example of a Send Connector processing messages just for the contoso.com domain, we could enable the Include all subdomains check box if we want this Send Connector to process messages for subdomains of the contoso.com domain (such as sales.contoso.com or europe.contoso.com for example).
d. Leave the Cost field set to the default value of 1. The Cost field can be used to control which Send Connector is used in case there are multiple paths existing for messages. In those cases, the connector with the least cost would be used first. As we are only interested in a single Send Connector processing all messages destined for Internet-based recipients, we can safely leave this field at the default value of 1.
e. The SMTP Address Space window should now look like the example shown in Figure 3. Once you are happy with the configuration, click OK.
Figure 3: Configuring the SMTP Address Space
2. Back at the Address Space page of the wizard, the desired address space should now be displayed. Leave the Scoped Send Connector check box cleared. This configuration allows this Send Connector to be used by all Hub Transport servers within the Exchange 2007 organization. Selecting this check box means that only the Hub Transport servers within the same Active Directory site as each other can be used by the connector. When you are happy with the configuration of the Address space page of the wizard, click Next.
3. The next page of the wizard displayed is the Network settings page. Here is how to complete the configuration of this page.
a. Since we are interested in routing all Internet messages through the Edge Transport server, ensure that the option Route mail through the following smart hosts is chosen.
b. Click the Add button. This will bring up the Add smart host window. Here you can either enter the IP address or the Fully Qualified Domain Name (FQDN) of the Edge Transport server. As you can see from Figure 4 below, I have chosen to use the FQDN of the Edge Transport server which obviously assumes that the Hub Transport servers will be able to resolve the Edge Transport server’s name. To allow this, I simply added a DNS A record for the Edge Transport server into the internal DNS server configuration. Do not forget though that in my example, the configuration of the Edge Transport server has two network interface cards configured, so it is important to ensure that the DNS A record points to the internal network card’s IP address. Once you are happy with the configuration, click OK.
Figure 4: Configuring the Smart Host
c. Back at the Network settings page of the wizard, the desired smart host configuration should now be displayed. Leave the Use the External DNS Lookup settings on the transport server check box cleared. Having this check box selected assumes that you have external DNS server information configured on the Hub Transport servers which is not what we want in this case.
d. When you are happy with the configuration of the Network settings page, click Next.
4. The Configure smart host authentication settings page of the wizard will now be displayed. Here, we will make use of the local user account created earlier on the Edge Transport server so that the Hub Transport server can be authenticated by the Edge Transport server when using this Send Connector. To complete the configuration of this page of the wizard:
a. Select the Basic Authentication radio button
b. Select the Basic Authentication over TLS check box
c. In the User name field, enter the user name of the local user account that you created on the Edge Transport server. In this case, this user account is called SMTPAUTH
d. In the Password field, enter the password of the local user account that you created on the Edge Transport server
e. The completed page should look like the example shown in Figure 5
Figure 5: Configuring the Smart Host Authentication Settings
f. When you are happy with the configuration of this page, click Next.
5. The Source Server page of the wizard is now displayed. In my example, configuration of this new Send Connector is already associated with the server SRV1 which is running the Hub Transport server. If you want to add additional Hub Transport servers to be allowed to send messages through this new Send Connector, follow these steps:
a. Click the Add… button which brings up a window titled Select Hub Transport and subscribed Edge Transport servers.
b. From the list of Hub Transport servers presented, highlight the Hub Transport server that you wish to add and then click the OK button.
c. Back at the Source Server page of the wizard, confirm that you have the correct Hub Transport servers now listed and then click Next.
6. The penultimate page of the New Send Connector wizard now displayed is the New Connector page. Here you will see a summary of your chosen configuration. Review the configuration and if you are happy to proceed click the New button. Of course, if you have noticed a mistake along the way you can simply use the Back button to rectify the problem.
7. The final page of the wizard presented is the Completion page as you can see from Figure 6. Note the Exchange Management Shell cmdlet that can be used to create this connector. Click the Finish button to complete the creation of this new Send Connector.
Figure 6: Completing the Configuration of the New Send Connector
The New Send Connector wizard should now disappear and you should find yourself back in the Exchange Management Console with the Send Connectors tab displayed showing your newly created Send Connector with a status of Enabled. This completes the creation of the Send Connector responsible for processing messages from your internal Exchange 2007 organization and sending them onwards to the Edge Transport server.
That completes part two of this four-part article series. I have taken time to explain the full process required in order to configure the first Send Connector. Additional Send Connectors are required on the Edge Transport server, and so, we will be able to skip the vast majority of this part of the configuration process as some of it has already been explained. In the third part of this article series, we will be looking at the configuration of the Hub Transport Receive Connector as well as the Edge Transport server’s internal Receive Connector.
If you would like to read the other parts in this article series please go to: