programming4us
programming4us
SECURITY

Microsoft Exchange Server 2007 : Edge Transport Server Connectors (part 1) - Configuring Send Connectors on the Edge Transport Server

- How To Install Windows Server 2012 On VirtualBox
- How To Bypass Torrent Connection Blocking By Your ISP
- How To Install Actual Facebook App On Kindle Fire
After the installation of the Microsoft Exchange Server 2007 Edge Transport server role, you must configure the appropriate Send and Receive Connectors. Until this has been accomplished, the server will be unable to send SMTP messages to, or receive them from, the Internet and your internal Hub Transport servers.

As discussed in the previous section, to complete the configuration of the Send Connector on an Edge Transport server, you subscribe the server to the organization using EdgeSync, which then replicates the appropriate connectors to the Edge Transport server. If you do not use EdgeSync, you must manually create and configure the connector.

This section covers additional information about Edge Transport server connectors that was not touched on in the previous section.

An Edge Transport server must have at least four required connectors to function properly. The first two, both Send Connectors, are created and configured for you automatically during the EdgeSync process:

  • A Send Connector must exist that is configured to send messages to the Internet. Typically, the address space for this connector is set to * (all Internet domains). DNS routing is used to resolve destinations. The usage type for this connection is set to “Internet.” This connector is created automatically when you use EdgeSync to subscribe the server to an Active Directory site.

  • A Send Connector must exist that is configured to send messages to the Hub Transport servers in the Exchange organization. The address space for this connector can either be *, or you can manually list each of the domains for which you are processing mail. The smart hosts for the connector should be configured as your Hub Transport servers, and the usage type set to “Internal.” This connector is also created automatically during the subscription process.

The next two required connectors are Receive Connectors:

  • A Receive Connector must exist that is configured to accept messages from the Internet. Usually, this connector is configured to accept connections from any IP address range. Furthermore, it is normally configured to allow anonymous access. When configuring the local network bindings for this connection, they should be set to the external-facing IP address of the Edge Transport server, and the usage type should be set to “Internet.”

  • A second Receive Connector must exist that is configured to accept messages from Hub Transport servers in your organization. For security purposes, you can configure this connector to accept connections only from your Hub Transport servers by listing their IP address ranges. The local network bindings for this connector should be configured as the internal-facing IP address of the Edge Transport server, and the usage type should be set to “Internal.”

Configuring Receive Connectors on the Edge Transport Server

When you install the Edge Transport server, one Receive Connector is automatically created. This connector is configured by default to accept SMTP traffic from all IP address ranges, and it is bound to all IP addresses associated with the local server. The usage type is set to “Internet,” and the connection will accept anonymous connections. It is recommended that you modify the settings of this Receive Connector and create a second one for internal usage. To perform this procedure, follow these steps:

1.
Start the Exchange Management Console on the Edge Transport server.

2.
In the console tree, select Edge Transport.

3.
In the results pane, select the appropriate Edge Transport server and then, on the bottom half of the pane, click the Receive Connectors tab.

4.
Select the default connector and, in the action pane, click Properties.

5.
Click the Network tab, and edit the existing Local IP Addresses (by default, set to All Available). Configure this address to be the IP address of the Internet-facing network adapter of the Edge Transport server. Save your changes and exit, as no other changes are needed on this connector.

6.
Next, in the action pane, click New Receive Connector. On the Introduction page, enter a name for this connector, and select a usage type as Internal. Click Next to continue.

7.
On the Remote Network Settings page, modify the Remote IP Addresses and configure them to accept mail from the IP addresses assigned to your Hub Transport servers. Save the settings and click New to create the connector.

8.
After the connector has been created, you must make one more modification. Select the connector in the results pane and select Properties in the action pane. Click the Network tab, and double-click the Local IP Address(es) entry, currently set to (All Available). Click the Specify an IP Address option button, and enter the IP address of the internal-facing network adapter of the Edge Transport server. Save all settings and exit, as no other changes are needed on this connector.

Configuring Send Connectors on the Edge Transport Server

As discussed in the section on Hub Transport servers, the Send Connectors needed on your Edge Transport server are automatically generated by the EdgeSync service. If you elect to not create an Edge subscription, you must manually configure the Send Connectors.

Manual Completion of Send Connectors

To manually complete the configuration of the first Send Connector, do the following:

1.
Start the Exchange Management Console on the Edge Transport server.

2.
In the console tree, select Edge Transport.

3.
In the results pane, select the appropriate Edge Transport server and then, on the bottom half of the pane, click the Send Connectors tab.

4.
In the action pane, click New Send Connector.

5.
On the Introduction page, type a name for the connector, and set the usage to Internet. Click Next to continue.

6.
On the Address Space page, click Add. Set the Domain to * and ensure the Include All Subdomains option is selected. Click Next to continue.

7.
On the Network Settings page, select Use Domain Name System (DNS) “MX” Records to Route Mail Automatically. Click Next to continue. Save all settings and exit, as no further configuration is needed on this connector.

To manually complete the configuration of the second Send Connector, do the following:

1.
Start the Exchange Management Console on the Edge Transport server.

2.
In the console tree, select Edge Transport.

3.
In the results pane, select the appropriate Edge Transport server and then, on the bottom half of the pane, click the Send Connectors tab.

4.
In the action pane, click New Send Connector.

5.
On the Introduction page, type a name for the connector, and set the usage to Internal. Click Next to continue.

6.
On the Address Space page, click Add. Set the domain to the domain(s) for which you accept mail. If you have more than one accepted domain, configure additional entries. Ensure the Include All Subdomains option is selected. Click Next to continue.

7.
On the Network Settings page, select Route All Mail Through the Following Smart Hosts, and click Add.

8.
Enter the IP address or FQDN of one of your Hub Transport servers as the smart host. Click OK to continue. To add additional Hub Transport servers, click Add again. When you are ready, click Next to continue.

9.
On the Smart Host Security Settings page, ensure the None option button is selected, and click Next.

10.
Review all entries and, after all entries are correct, click New to create the connector.
Other  
  •  Microsoft Exchange Server 2007 : Server and Transport-Level Security - Exchange Server 2007 SMTP Connectors (part 2) - Hub Transport Server Connectors
  •  Microsoft Exchange Server 2007 : Server and Transport-Level Security - Exchange Server 2007 SMTP Connectors (part 1) - Connector Topology
  •  Microsoft Exchange Server 2007 : Server and Transport-Level Security - Transport-Level Security Defined
  •  Microsoft Exchange Server 2007 : Exchange Server-Level Security Features (part 2) - Protecting Exchange Server 2007 from Viruses
  •  Microsoft Exchange Server 2007 : Exchange Server-Level Security Features (part 1) - Exchange Server 2007 Antispam Measures
  •  Microsoft Exchange Server 2007 : Components of a Secure Messaging Environment (part 5) - Using Email Disclaimers
  •  Microsoft Exchange Server 2007 : Components of a Secure Messaging Environment (part 4) - Establishing a Corporate Email Policy, Securing Groups
  •  Microsoft Exchange Server 2007 : Components of a Secure Messaging Environment (part 3) - Hardening Windows Server 2003 - Running SCW
  •  Microsoft Exchange Server 2007 : Components of a Secure Messaging Environment (part 2) - Hardening Windows Server 2003 - Using the Microsoft Baseline Security Analyzer
  •  Microsoft Exchange Server 2007 : Components of a Secure Messaging Environment (part 1) - Hardening Windows Server 2003 - Auditing Policies
  •  
    Top 10
    - Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
    - Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
    - Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
    - Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
    - Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
    - Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
    - Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
    - Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
    - Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
    - Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
    REVIEW
    - First look: Apple Watch

    - 3 Tips for Maintaining Your Cell Phone Battery (part 1)

    - 3 Tips for Maintaining Your Cell Phone Battery (part 2)
    programming4us programming4us
    Celebrity Style, Fashion Trends, Beauty and Makeup Tips.
    programming4us
     
     
    programming4us