Setting up the infrastructure
The infrastructure for the IPv6 test lab network consists of five computers performing the following services:
| • | A computer running Whistler that is used as a Domain Name System (DNS) server. This computer is named DNS1. |
| • | A computer running Windows that is used as a client. This computer is named CLIENT1. |
| • | A computer running Windows that is used as a router. This computer is named ROUTER1. |
| • | A computer running Windows that is used as a router. This computer is named ROUTER2. |
| • | A computer running Windows that is used as a client. This computer is named CLIENT2. |
The following illustration shows the configuration of the IPv6 test lab.
There are three network segments:
| • | A network segment known as Subnet 1 that uses the private IP network ID of 10.0.1.0/24 and site-local subnet of FEC0:0:0:1::/64. |
| • | A network segment known as Subnet 2 that uses the private IP network ID of 10.0.2.0/24 and site-local subnet of FEC0:0:0:2::/64. |
| • | A network segment known as Subnet 3 that uses the private IP network ID of 10.0.3.0/24 and site-local subnet of FEC0:0:0:3::/64. |
All computers on each subnet are connected to a separate common hub or Layer 2 switch. The two router computers, ROUTER1 and ROUTER2, have two network adapters installed.
For the IPv4 configuration, each computer is manually configured with the appropriate IP address, subnet mask, default gateway, and DNS server IP address. Dynamic Host Configuration Protocol (DHCP) and Windows Internet Name Service (WINS) servers are not used. For the IPv6 configuration, link-local addresses are used initially.
The following sections describe how each of the computers in the test lab are configured. To reconstruct this test lab, please configure the computers in the order presented.
Note
| • | The following instructions are for configuring a test lab using a minimum number of computers. Individual computers are needed to separate the services provided on the network and to clearly show the desired functionality. This configuration is neither designed to reflect best practices nor is it designed to reflect a desired or recommended configuration for a production network. The configuration, including IP addresses and all other configuration parameters, is designed only to work on a separate test lab network. |
DNS1
DNS1 is a computer running Whistler . It is providing DNS Server services for the testlab.microsoft.com DNS domain. To configure DNS1 for this service, perform the following steps:
1. | Install Whistler as a stand-alone server. Set the Administrator password. |
2. | After restarting, log on as Administrator. |
3. | Install the IPv6 protocol. For more information, see To install IPv6 |
4. | Install the Domain Name System (DNS) Server service. |
5. | Configure the TCP/IP protocol with the IP address of 10.0.1.2, the subnet mask of 255.255.255.0, and the default gateway of 10.0.1.1. For more information, see To configure TCP/IP for static addressing |
CLIENT1
CLIENT1 is a computer running Windows that is being used as a client. To configure CLIENT1 as a client computer, perform the following steps:
1. | On CLIENT1, install Windows as a workgroup computer. Set the Administrator password. |
2. | After restarting, log on as Administrator. |
3. | Install the IPv6 protocol. For more information, see To install IPv6 |
4. | Configure the TCP/IP protocol with the IP address of 10.0.1.3, the subnet mask of 255.255.255.0, a default gateway of 10.0.1.1, and the DNS server IP address of 10.0.1.2. For more information, see To configure TCP/IP for static addressing and To configure TCP/IP to use DNS |
ROUTER1
ROUTER1 is a computer running Windows that is being used as a router between Subnet 1 and Subnet 2. To configure ROUTER1 as a router, perform the following steps:
1. | On ROUTER1, install Windows as a workgroup computer. Set the Administrator password. |
2. | After restarting, log on as Administrator. |
3. | Install the IPv6 protocol. For more information, see To install IPv6 |
4. | For the interface on Subnet 1, configure the TCP/IP protocol with the IP address of 10.0.1.1, the subnet mask of 255.255.255.0, and the DNS server IP address of 10.0.1.2. For more information, see To configure TCP/IP for static addressing and To configure TCP/IP to use DNS |
5. | For the interface on Subnet 2, configure the TCP/IP protocol with the IP address of 10.0.2.1, the subnet mask of 255.255.255.0, and a default gateway of 10.0.2.2. For more information, see To configure TCP/IP for static addressing |
6. | Enable IP forwarding. For more information, see To enable IP forwarding |
ROUTER2
ROUTER2 is a computer running Windows that is being used as a router between Subnet 2 and Subnet 3. To configure ROUTER2 as a router, perform the following steps:
1. | On ROUTER2, install Windows as a workgroup computer. Set the Administrator password. |
2. | After restarting, log on as Administrator. |
3. | Install the IPv6 protocol. For more information, see To install IPv6 |
4. | For the interface on Subnet 2, configure the TCP/IP protocol with the IP address of 10.0.2.2, the subnet mask of 255.255.255.0, and a default gateway of 10.0.2.1. For more information, see To configure TCP/IP for static addressing |
5. | For the interface on Subnet 3, configure the TCP/IP protocol with the IP address of 10.0.3.1, and the subnet mask of 255.255.255.0. For more information, see To configure TCP/IP for static addressing |
6. | Enable IP forwarding. For more information, see To enable IP forwarding |
CLIENT2
CLIENT2 is a computer running Windows that is being used as a client. To configure CLIENT2 as a client computer, perform the following steps:
1. | On CLIENT2, install Windows as a workgroup computer. Set the Administrator password. |
2. | After restarting, log on as Administrator. |
3. | Install the IPv6 protocol. For more information, see To install IPv6 |
4. | Configure the TCP/IP protocol with the IP address of 10.0.3.2, the subnet mask of 255.255.255.0, and a default gateway of 10.0.3.1. For more information, see To configure TCP/IP for static addressing |
5. | Verify the integrity of the IPv4 routing infrastructure by pinging 10.0.1.3 from the CLIENT2 computer. |