Export (0) Print
Expand All

How to Configure Network Connections for a Single Copy Cluster

 

Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007

Topic Last Modified: 2007-10-10

This topic explains how to configure the network connections for a Microsoft Exchange Server 2007 clustered mailbox server in a single copy cluster (SCC) environment. Proper configuration of the network connections is necessary to make sure that client connections to the cluster server are possible and happen in a timely fashion. There are three procedures that must be performed prior to forming the clusters:

  • Configure the network connection order

  • Configure the public network connections

  • Configure the private network connections

    importantImportant:
    If you have a network adapter that can be manually configured to specify speed and duplex mode, and you are using a crossover cable, you should manually specify a speed and duplex mode. With network adapters that can manually specify a speed and duplex mode, make sure that you hard set them with the same configuration on all nodes and according to the manufacturers' specifications. For network adapters that do not support manual settings, follow the card manufacturer's specifications. The amount of information that is traveling across the private network is small, but latency is critical for communication. If you have the same speed and duplex settings, this helps to support reliable communication. If you are not sure of the supported speed of your card and connecting devices, or your manufacturer's recommended settings, we recommend that you set all the devices on that path to 10 megabytes (MB) per second and half duplex. This configuration provides sufficient bandwidth and reliable communication. For more information about the effects of using the Autodetect setting on network interface cards in cluster deployments, see Microsoft Knowledge Base article 174812, The effects of using Autodetect setting on cluster network interface card.

To perform the following procedures, the account you use must be delegated the following:

  • Membership in the local Administrators group

For more information about permissions, delegating roles, and the rights that are required to administer Exchange Server 2007, see Permission Considerations.

  1. In Control Panel, double-click Network Connections.

  2. On the Advanced menu, click Advanced Settings.

  3. In Advanced Settings, on the Adapters and Bindings tab, under Connections, make sure that your connections appear in the following order:

    • <Public network name> (where Public network name is the name of your public network connection)

    • <Private network name> (where Private network name is the name of your private network connection)

    • Remote access connections

  4. Click OK to save the changes.

noteNote:
If your clustered mailbox server has more than two networks, it is important to make sure that all public networks are at the top of the connection order list and all private networks are at the bottom of the connection order list. If your cluster includes a network interface for iSCSI-based storage, the iSCSI network interface should be listed in between the <Private network name> and remote access connections.

  1. In Control Panel, double-click Network Connections.

  2. In Network Connections, right-click <Network connection name> (where <Network connection name> is the name of your public network connection), and then click Rename.

  3. In the Name field, enter a meaningful name, such as Public.

  4. In Network Connections, right-click <Network connection name> (where <Network connection name> is the name of your public network connection), and then click Properties.

  5. In <Network connection name> Properties, on the General tab, under This connection uses the following items, make sure that the Client for Microsoft Networks, File and Printer Sharing for Microsoft Networks, and Internet Protocol (TCP/IP) check boxes are selected.

  6. Select Internet Protocol (TCP/IP), and then click Properties.

  7. In Internet Protocol (TCP/IP) Properties, click Advanced.

  8. In Advanced TCP/IP Settings, on the DNS tab, verify the following information:

    • Under DNS server addresses, in order of use, ensure that all of the required addresses are listed.

    • In the For resolution of unqualified names area, ensure that the Domain Name System (DNS) suffix behavior for resolution of host names is configured correctly for your environment.

  9. On the WINS tab, make sure that Disable NetBIOS over TCP/IP is not selected.

  10. Click OK twice to save the changes, and then click Close to exit Properties.

  1. In Control Panel, double-click Network Connections.

  2. In Network Connections, right-click <Network connection name> (where <Network connection name> is the name of your private network connection), and then click Rename.

  3. In the Name field, enter a meaningful name, such as Private.

  4. In Network Connections, right-click <Network connection name> (where <Network connection name> is the name of your private network connection), and then click Properties.

  5. On the General tab of the private network connection, select Internet Protocol (TCP/IP).

  6. Select Internet Protocol (TCP/IP), and then click Properties.

  7. On the Internet Protocol (TCP/IP) Properties page, on the General tab, select Use the following IP address, and then configure a static IP address and subnet mask for the connection. Also select Use the following DNS server addresses, and leave blank the IP address fields for Preferred DNS server and Alternate DNS server, and then click Advanced.

    noteNote:
    The default gateway and DNS entries are left blank. It is not necessary to configure the default gateway or DNS settings because private cluster networks are used only for internal cluster communications.
  8. In Advanced TCP/IP Settings, on the DNS tab, verify the following information:

    • Under DNS server addresses, in order of use, make sure that no addresses are listed.

    • Make sure that the Register this connection's addresses in DNS check box is cleared.

  9. On the WINS tab, make sure that Disable NetBIOS over TCP/IP is selected.

  10. Click OK twice to save the changes, and then click Close to exit Properties.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2015 Microsoft