TechNet
Products
IT Resources
Downloads
Training
Support
Products
Windows
Windows Server
System Center
Microsoft Edge
Office
Office 365
Exchange Server
SQL Server
SharePoint Products
Skype for Business
See all products »
Resources
Channel 9 Video
Evaluation Center
Learning Resources
Microsoft Tech Companion App
Microsoft Technical Communities
Microsoft Virtual Academy
Script Center
Server and Tools Blogs
TechNet Blogs
TechNet Flash Newsletter
TechNet Gallery
TechNet Library
TechNet Magazine
TechNet Wiki
Windows Sysinternals
Virtual Labs
Solutions
Networking
Cloud and Datacenter
Security
Virtualization
Updates
Service Packs
Security Bulletins
Windows Update
Trials
Windows Server 2016
System Center 2016
Windows 10 Enterprise
SQL Server 2016
See all trials »
Related Sites
Microsoft Download Center
Microsoft Evaluation Center
Drivers
Windows Sysinternals
TechNet Gallery
Training
Expert-led, virtual classes
Training Catalog
Class Locator
Microsoft Virtual Academy
Free Windows Server 2012 courses
Free Windows 8 courses
SQL Server training
Microsoft Official Courses On-Demand
Certifications
Certification overview
Special offers
MCSE Cloud Platform and Infrastructure
MCSE: Mobility
MCSE: Data Management and Analytics
MCSE Productivity
Other resources
Microsoft Events
Exam Replay
Born To Learn blog
Find technical communities in your area
Azure training
Official Practice Tests
Support options
For business
For developers
For IT professionals
For technical support
Support offerings
More support
Microsoft Premier Online
TechNet Forums
MSDN Forums
Security Bulletins & Advisories
Not an IT pro?
Microsoft Customer Support
Microsoft Community Forums
Sign in
Home
Library
Wiki
Learn
Gallery
Downloads
Support
Forums
Blogs
Resources For IT Professionals
United States (English)
Россия (Pусский)
中国(简体中文)
Brasil (Português)
Skip to locale bar
Post an article
Translate this page
Powered by
Microsoft® Translator
Wikis - Page Details
First published by
Joe Davies
(0Microsof)
When:
9 Nov 2011 3:47 PM
Last revision by
Yagmoth555
(eMicrosoft Community Contributor, Microsoft Partne)
When:
8 Feb 2013 8:36 PM
Revisions:
3
Comments:
1
Options
Subscribe to Article (RSS)
Share this
Can You Improve This Article?
Positively!
Click Sign In to add the tip, solution, correction or comment that will help other users.
Report inappropriate content using
these instructions
.
Wiki
>
TechNet Articles
>
Test Lab Guide Mini-Module: Configuring the Base Configuration Test Lab for IPv6-Only
Test Lab Guide Mini-Module: Configuring the Base Configuration Test Lab for IPv6-Only
Article
History
Test Lab Guide Mini-Module: Configuring the Base Configuration Test Lab for IPv6-Only
This Test Lab Guide Mini-Module describes how to configure Corpnet subnet of the
Base Configuration test lab
for IPv6-only connectivity. You configure DC1 as a DHCPv6 server and as an advertising router for the Corpnet subnet, disable IPv4 on all intranet hosts, and then show that all network, Active Directory, and application connectivity works in the IPv6-only environment.
Note
These instructions are designed to quickly configure the Corpnet subnet of a working base configuration test lab for IPv6 only. To learn about default, ISATAP, and native IPv6 connectivity, see the
Test Lab Guide: Demonstrate IPv6
.
If you are running the base configuration test lab in a virtual environment, you can create snapshots of the virtual machines (VMs) for all of the test lab computers before performing the following procedure.
Configuring an IPv6-only Intranet
To configure DC1 as the IPv6 router and DHCPv6 server:
1.
On EDGE1, in the Command Prompt window, type
ipconfig
, and then press ENTER. Notice the link-local IPv6 address (beginning with “fe80”) that is assigned to the Corpnet interface. Write the address here: __________________________________
2.
On DC1, click
Start
, click
All Programs
, click
Accessories
, right-click
Command Prompt
, and then click
Run as administrator
.
3.
In the Command Prompt window, type the following commands
netsh interface ipv6 add address Corpnet 2001:db8::1111
netsh interface ipv6 add route 2001:db8::/64 interface=Corpnet publish=yes
netsh interface ipv6 add route ::/0 interface=Corpnet nexthop=
link-local address of EDGE1’s Corpnet interface
publish=yes
4.
On DC1, click
Start
, point to
Administrative Tools
, and then click
DHCP
.
5.
In the console tree of the DHCP snap-in, open
dc1.corp.contoso.com
, right-click
IPv6
, and then click
New Scope
.
6.
On the Welcome page, click
Next
.
7.
On the Scope Name page, type
Corpnet
in
Name
, and then click
Next
.
8.
On the Scope Prefix page, type
2001:db8::
in
Prefix
, and then click
Next
.
9.
On the Add Exclusions page, click
Next
.
10.
On the Scope Lease page, click
Next
.
11.
On the Completing page, click
Finish
.
12.
In the console tree of the DHCP snap-in, open
IPv6
, right-click
Server Options
, and then click
Configure Options
.
13.
On the
General
tab, select
0023 DNS Recursive Name Server IPv6 Addresses
, type
2001:db8::1111
in
New IPv6 address
, click
Add
, and then click
OK
.
14.
In the Command Prompt window, type the following command:
netsh interface ipv6 set interface Corpnet advertising=enabled forwarding=enabled otherstateful=enabled advertisedefaultroute=enabled
15.
Connect CLIENT1 to the Corpnet subnet.
16.
In the Command Prompt window, type
ipconfig /all
, and then press ENTER. Notice that there are now IPv6 addresses beginning with "2001:db8::" assigned to the Local Area Connection adapter and that the DNS servers assigned to the Local Area Connection adapter includes 2001:db8::1111.
Note:
CLIENT1 and other computers on the Corpnet configure at least two IPv6 addresses starting with "2001:db8::". One from DC1 acting as an advertising router (stateless) and another from DC1 acting as a DHCPv6 server (stateful). IPv6 hosts do not configure a 2001:db8::/64 route for the Corpnet subnet based on the address received from DC1 acting as a DHCPv6 server. Therefore, DC1 must also advertise the route, resulting in at least two IPv6 addresses with "2001:db8::".
To configure the Contoso intranet for IPv6-only and demonstrate connectivity:
1.
On CLIENT1, right-click the network icon in the notification area, click
Network and Sharing Center
, click
Change adapter settings
, right-click
Local Area Connection
, and then click
Properties
.
2.
In
This connection uses the following items
, clear
Internet Protocol Version 4 (TCP/IPv4)
, and then click
OK
.
3.
In the Command Prompt window, type
ipconfig /all
, and then press ENTER. Notice that all IPv4 address configuration for the Local Area Connection interface has been removed.
4.
On DC1, right-click the network icon in the notification area, click
Network and Sharing Center
, click
Change adapter settings
, right-click
Corpnet
, and then click
Properties
.
5.
In
This connection uses the following items
, clear
Internet Protocol Version 4 (TCP/IPv4)
, and then click
OK
.
6.
Right-click
Corpnet2
, and then click
Properties
.
7.
In
This connection uses the following items
, clear
Internet Protocol Version 4 (TCP/IPv4)
, and then click
OK
.
8.
On APP1, right-click the network icon in the notification area, click
Network and Sharing Center
, click
Change adapter settings
, right-click
Local Area Connection
, and then click
Properties
.
9.
In
This connection uses the following items
, clear
Internet Protocol Version 4 (TCP/IPv4)
, and then click
OK
.
10.
Click
Start
, click
All Programs
, click
Accessories
, right-click
Command Prompt
, and then click
Run as administrator
.
11.
In the Command Prompt window, type
ipconfig /renew6
, and then press ENTER.
12.
In the Command Prompt window, type
ipconfig /all
, and then press ENTER. Verify that APP1 has a DHCPv6-assigned IPv6 address and DNS server (2001:db8::1111).
13.
On EDGE1, right-click the network icon in the notification area, click
Network and Sharing Center
, click
Change adapter settings
, right-click
Corpnet
, and then click
Properties
.
14.
In
This connection uses the following items
, clear
Internet Protocol Version 4 (TCP/IPv4)
, and then click
OK
.
15.
click
Start
, click
All Programs
, click
Accessories
, right-click
Command Prompt
, and then click
Run as administrator
.
16.
In the Command Prompt window, type
ipconfig /renew6
, and then press ENTER.
17.
On CLIENT1, log off and then log on using the CORP\User1 account.
18.
Click
Start
, click
All Programs
, click
Accessories
, right-click
Command Prompt
, and then click
Run as administrator
.
19.
In the Command Prompt window, type
ipconfig
, and then press ENTER. Notice that there is no longer an IPv4 address assigned to the Local Area Connection adapter.
20.
In the Command Prompt window, type
nltest /dsgetdc: /force
, and then press ENTER. Notice that the domain controller found is DC1 via its IPv6 address.
21.
In the Command Prompt window, type
ping edge1
, and then press ENTER. You should see a successful name resolution to EDGE1’s IPv6 address on the Corpnet subnet (starting with “2001:db8::”) and four successful replies.
22.
In the Command Prompt window, type
ping app1.corp.contoso.com
, and then press ENTER. You should see four successful replies.
23.
From the taskbar, click the Internet Explorer icon.
24.
In the Address bar, type
http://app1.corp.contoso.com/
, and then press ENTER. You should see the default IIS 7 web page for APP1.
25.
In the Address bar, type
https://app1.corp.contoso.com/
, and then press ENTER. You should see the default IIS 7 web page for APP1.
26.
Close Internet Explorer.
27.
Click
Start
, type
\\app1\Files
, and then press ENTER.
28.
You should see a folder window with the contents of the Files shared folder.
29.
In the Files shared folder window, double-click the
Example.txt
file. You should see the contents of the Example.txt file.
30.
Close the
example.txt - Notepad
and the
Files
shared folder windows.
With this new configuration, all network, Active Directory, and application traffic uses only IPv6 and works the same as in the Base Configuration test lab, which is IPv4-only.
Note
If you now connect CLIENT1 to the Internet subnet, it will not be able to connect to INET1 or EDGE1 without first enabling the
Internet Protocol Version 4 (TCP/IPv4)
protocol on the Local Area Connection.
If you are running this test lab in a virtual environment, you can create snapshots of the virtual machines (VMs) for all of the test lab computers to save this configuration.
For additional resources for the IPv6 test lab, see
IPv6 Test Lab for Windows Server 2008 R2 and Windows 7
.
en-US
,
IPv6
,
mini-module
,
Test Lab Guide
[Edit tags]
Leave a Comment
Please add 4 and 7 and type the answer here:
Post
Wiki - Revision Comment List(Revision Comment)
Sort by:
Published Date
|
Most Recent
|
Most Useful
Comments
Joe Davies
17 Feb 2012 1:39 PM
Joe Davies edited Original. Comment: Update to use new 2001:db8::/64 prefix on the Corpnet subnet
Edit
Page 1 of 1 (1 items)
Wikis - Comment List
Sort by:
Published Date
|
Most Recent
|
Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
Posted by
Joe Davies
on
17 Feb 2012 1:39 PM
Joe Davies edited Original. Comment: Update to use new 2001:db8::/64 prefix on the Corpnet subnet
Edit
Page 1 of 1 (1 items)