12.From the Network Connections folder on CLIENT2, disable and then enable the Local Area Connection. This renews CLIENT2’s configuration.

13.On CLIENT2, type the netsh interface ipv6 show address command to view the new addresses that are based on the global prefix of 2001:DB8:0:3::/64.

14.On CLIENT2, type the netsh interface ipv6 show route command to view new routes for 2001:DB8:0:2::/64, 2001:DB8:0:3::/64, and ::/0.

15.On CLIENT1, type the following command to ping CLIENT2’s public address: ping CLIENT2PublicAddress

On CLIENT1, type the following command to trace the route between CLIENT1 and CLIENT2:

tracert -d CLIENT2PublicAddress

In the Tracert.exe tool display, you should see the link-local address of the Subnet 1 Connection of ROUTER1 and the link-local address of the Subnet 2 Connection of ROUTER2.

16.On ROUTER1, type the netsh interface ipv6 show neighbors command to view the entries in the ROUTER1 neighbor cache for CLIENT1 and ROUTER2. Type the netsh interface ipv6 show destinationcache command to view the entries in the ROUTER1 destination cache for CLIENT1 and CLIENT2.

Using Name Resolution

To test the use of DNS and the local Hosts file to resolve names to IPv6 addresses, complete the following steps:

1.On DNS1, use the DNS snap-in to view the A and AAAA records in the testlab.microsoft.com forward lookup zone that were dynamically registered by the computers in the test lab. Verify that an AAAA record for CLIENT2 exists.

2.If an AAAA record for CLIENT2 does not exist, create a host resource record for CLIENT2 with the DNS name client2.testlab.microsoft.com for its public IPv6 address.

For example, if CLIENT2’s public address is 2001:db8::3:3cec:bf16:505:eae6, create an AAAA resource record in the testlab.microsoft.com forward lookup zone for the following:

Name: client2

IP address: 2001:db8::3:3cec:bf16:505:eae6

3.On CLIENT1, type the following command: ping client2.testlab.microsoft.com

The name client2.testlab.microsoft.com is resolved to its public address by sending a DNS query to DNS1.

452 Understanding IPv6, Second Edition

4.On CLIENT2, create the following entry in the Hosts file (located in the %SystemRoot%\System32\Drivers\Etc folder):

Client1PublicAddress c1

For example, if CLIENT1’s public address is 2001:db8::1:dd48:ab34:d07c:3914, the entry in the Hosts file is

2001:db8::1:dd48:ab34:d07c:3914 c1

5.On CLIENT2, type the following command: ping c1

The name c1 is resolved to CLIENT1’s public address by using the local Hosts file.

Configuring an IPv6-Only Routing Infrastructure

To configure a routing infrastructure so that all test lab nodes are reachable only by using IPv6 traffic, complete the following steps:

1.On DNS1, type the netsh interface ipv4 uninstall command. Restart DNS1.

2.On CLIENT1, type the netsh interface ipv4 uninstall command. Restart CLIENT1.

3.On ROUTER1, type the netsh interface ipv4 uninstall command. Restart ROUTER1.

4.On ROUTER2, type the netsh interface ipv4 uninstall command. Restart ROUTER2.

5.On CLIENT2, type the netsh interface ipv4 uninstall command. Restart CLIENT2.

At this point in the test lab configuration, there is only an IPv6 routing infrastructure throughout the test lab network. IPv4-based connectivity is not supported. You can now begin testing IPv6-only connectivity and functionality for Windows-based services and for your applications that have been modified to support both IPv4 and IPv6.

Note To reinstall IPv4 support, use the netsh interface ipv4 install command and restart the computer.

Some examples of tasks that you can do to continue your testing and evaluation of IPv6 connectivity for Windows-based services are the following:

■Make DNS1 an Active Directory domain controller for the testlab.microsoft.com domain.

■Join CLIENT1 and CLIENT2 to the testlab.microsoft.com domain, and test Active Directory domain operations.

■Make DNS1 a Web server, and test HTTP traffic over IPv6 from CLIENT1 and CLIENT2.