IPv6 Test Lab for Windows Server 2008 R2 and Windows 7

IPv6 Test Lab for Windows Server 2008 R2 and Windows 7

The IPv6 test lab for Windows Server 2008 R2 and Windows 7 is a test environment that you configure with 5 physical or virtual computers to demonstrate IPv6 connectivity and functionality that is included in Windows Server 2008 R2 and Windows 7.

The following figure shows the setup of the IPv6 test lab.

  

No new computers have been added to the Base Configuration test lab. However, an additional subnet, Corpnet2, has been added to test inter-subnet functionality.

To configure the IPv6 test lab, see the 
Test Lab Guide: Demonstrate IPv6.

The IPv6 test lab requires the Base Configuration test lab.

For information about how to set up this test lab environment on a Windows Server 2012-based Hyper-V server, see Hosting the IPv6 test lab with Windows Server 2012 Hyper-V.

IPv6 Test Lab Extensions

Test lab extensions contain procedures to demonstrate additional functionality in a working IPv6 test lab. The following IPv6 test lab extensions are available:

Additionally, the Adding IPv6 Connectivity test lab extension describes how to add IPv6 connectivity to the VPN remote access lab.

IPv6 Test Lab Guide Mini-modules

Test Lab mini-modules contain procedures to more quickly get a test lab to a new state, essentially skipping the demonstration steps. The following IPv6 test lab guide mini-module is available:

Here is the current IPv6 test lab stack:



For more information, see Microsoft Test Lab Guides.
 

Sort by: Published Date | Most Recent | Most Useful
Comments
  • i like

  • Me too

  • Cool

  • Can we get an updated lab out of Microsoft with pure IPV6 complete with DNSSEC? IPV6 can be a little confusing at first, but overall its easier then IPV4 once you have a IPV6 only environment setup.

  • I have configured the base lab and the IPv6 demonstration in an isolated VM environment.  When I get to the 6to4 demonstration, I have no 6to4 adapters.  I found several articles that says if you are using private addressing, you won't get a 6to4 adapter.  Is the fact that I do not have actual internet access also preventing the adapters from showing up?  EDGE1 has two interfaces: 10.0.0.2 and 131.107.0.2

    Thanks

  • Jon, please verify that the CLIENT1 computer on the actual Internet has a public IPv4 address. If not, 6to4 is effectively disabled. If CLIENT1 has a public IPv4 address, take a look at the steps in technet.microsoft.com/.../ee844172(WS.10).aspx to verify whether the 6to4 service has been disabled in some way.

  • Joe - thanks for responding

    I believe 131.107.x.x is in a public address range (this is the IP specified in the Base lab).  I do not have the DisabledComponents reg entry defined.  Do I have to have actual internet access?  I'm running my lab in isolation and while there is a virtual switch for the 131.107 segment, I do not have actual internet access.

  • Jon, the 131.107.y.z address space for the Internet subnet was chosen because it is in the public address range. By default CLIENT1 should create a 6to4 adapter with an address that starts with 2002: unless something is preventing it. Can you post this as a question on social.technet.microsoft.com/.../threads and include a copy of the display of the ipconfig command on CLIENT1 when it is connected to the Internet subnet? Thanks

  • FYI: I have updated the "Test Lab Guide: Demonstrate IPv6" document and associated extensions and mini-modules to change the IPv6 prefix on the Corpnet subnet to 2001:db8::/64 and to add a command to manually enable 6to4 on EDGE1 in the "Step 6: Demonstrate 6to4-based connectivity" section.

  • Corpnet instead of Contoso ?

Page 1 of 2 (11 items) 12