This article was previously published under Q178538
This article has been archived. It is offered "as is" and will no longer be updated.
Per RFC 1597: Section 3: Private Address Space, The Internet AssignedNumbers Authority (IANA) has reserved the following three blocks of the IPaddress space for private networks: 10.0.0.0 - 10.255.255.255 , 172.16.0.0- 172.31.255.255, and 192.168.0.0 - 192.168.255.254.
These network IDs and the associated IP addresses may be used freely inany internal network scheme and will not affect interoperability with theInternet as a whole. In particular, the class C range is the preferredrange to use when configuring the async connectors of Microsoft ExchangeServer.
Each async interface on a Windows NT Server computer requires two (2) ipaddress; one for the server and one for the client of the particularsession. The network ID of the async interface should be such that theasync interface is on a different subnet than the network interface of theserver; as such the unit is multihomed. Using a subnet mask of 255 in thethird octet of the class C address allows 255 networks with 254 hosts oneach network; this facilitates ease of planning and configuration.
For example, connect 3 Exchange sites through the Dynamic Remote AccessService (RAS) connector. Each Exchange Server computer has a single modem.
In the RAS configuration, select a static pool of addresses.
Configure the pools on each server as follows.
Server_1 192.168.1.1 and 188.8.131.52; Server_2 192.168.2.1 and 192.168.2.2 Server_3 192.168.3.1 and 192.168.3.2.
Thus the RAS server session on each server will get the .1 address and theclient session will be assigned the .2 address.