Test Lab Guide Mini-Module: Second Corpnet Subnet for Windows Server 2012
Article
Windows Server 2012 Base Configuration Test Lab Mini-Module for a Second Corpnet Subnet
This Test Lab Guide Mini-Module describes how to configure Corpnet2 as an optional second subnet to the Contoso intranet. DC1 is configured to route traffic between the Corpnet and Corpnet2 subnets. The following figure shows the resulting test lab configuration (click on it for a larger version):
If you are running the Windows Server 2012 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.
There are four steps to adding the Corpnet2 subnet to the Windows Server 2012 Base Configuration test lab.
Configure DC1.
Configure EDGE1.
Configure APP1.
Verify IPv4 connectivity to the Corpnet2 subnet.
Step 1: Configure DC1
DC1 is a Windows Server 2012 domain controller, DNS server, and DHCP server for the Contoso domain. In this step, we configure DC1 with an additional network adapter, with a DHCP scope for the new Corpnet2 subnet, and as an IPv4 router between the subnets.
To configure DC1 with an additional adapter:
Add another network adapter to DC1 and connect it to the Corpnet2 virtual or physical switch.
In Server Manager, click Local Server in the console tree. Click the link next to Ethernet in the Properties tile.
In Network Connections, right-click the network connection that is connected to the Corpnet subnet, and then click Rename.
Type Corpnet, and then press ENTER.
Right-click the network connection that is connected to the Corpnet2 subnet, and then click Rename.
Type Corpnet2, and then press ENTER.
Right-click Corpnet2, and then click Properties.
Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
Select Use the following IP address. In IP address, type 10.0.2.1. In Subnet mask, type 255.255.255.0.
Click Advanced, and then click the DNS tab.
In DNS suffix for this connection, type corp.contoso.com, click OK three times, and then click Close.
Close the Network Connections window.
Windows PowerShell equivalent commands
The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints. Prior to executing these commands, rename the network connections to Corpnet and Corpnet2 according to their associated subnets.
In the DHCP console tree, expand dc1.corp.contoso.com/IPv4/Scope [10.0.0.0] Corpnet, right-click Scope Options, and then click Configure Options.
In the Available Options list, select 121 Classless Static Routes, and then click Add Route.
In the Add a Static Route dialog box, type 10.0.2.0 in Destination, type 255.255.255.0 in Network Mask, type 10.0.0.1 in Router, and then click OK twice.
In the console tree, right click IPv4, click New Scope, and then click Next.
On the Scope Name page, type Corpnet2 in Name, and then click Next.
On the IP Address Range page, type 10.0.2.100 in Start IP address, type 10.0.2.150 in End IP address, type 24 in Length, and then click Next.
On the Add Exclusions and Delay page, click Next.
On the Lease Duration page, click Next.
On the Configure DHCP Options page, click Next.
On the Router (Default Gateway) page, type 10.0.2.1 in IP address, click Add, and then click Next.
On the Domain Name and DNS Servers page, click 10.0.2.1, and then click Remove.
Type 10.0.0.1 in IP address, click Add, and then click Next.
On the WINS Servers page, click Next.
On the Activate Scope page, click Next.
On the Completing the New Scope Wizard page, click Finish.
Close the DHCP snap-in.
Windows PowerShell equivalent commands
The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.
In this procedure, we configure EDGE1 with a static route so that IPv4 locations on the new Corpnet2 subnet are reachable and enable file sharing, which allows incoming traffic for the Ping.exe tool.
To configure EDGE1:
On EDGE1, from the desktop taskbar, right-click Windows PowerShell, and then click Run as administrator.
In the Windows PowerShell window, type the following command, and then press ENTER.
In the Windows PowerShell window, type ping 10.0.2.1, and then press ENTER. There should be four successful replies.
Leave the Windows PowerShell window open.
Step 4:Verify IPv4 connectivity to the Corpnet2 subnet
In this procedure, we verify that CLIENT1 can communicate with IPv4 locations on the Corpnet2 subnet and, while on the Corpnet2 subnet, can resolve names and communicate with locations on the Corpnet subnet.
** To test access to both subnets from CLIENT1**
Connect CLIENT1 to the Corpnet subnet.
From the Start screen, type PowerShell, then right-click Windows PowerShell, and click Run as administrator.
In the Windows PowerShell window, type ping 10.0.2.1, and then press ENTER. There should be four successful replies.
Connect CLIENT1 to the Corpnet2 subnet.
In the Windows PowerShell window, type ipconfig /all, and then press ENTER. CLIENT1 should have an IPv4 address in the range 10.0.2.100 to 10.0.2.150 with a default gateway of 10.0.2.1 and the DNS server address of 10.0.0.1
In the Windows PowerShell window, type ping 10.0.0.2, and then press ENTER. There should be four successful replies.
In the Command Prompt window, type ping 10.0.0.3, and then press ENTER. There should be four successful replies.
In the Command Prompt window, type ping EDGE1, and then press ENTER. There should be a successful name resolution to the IPv4 address 10.0.0.2 and four successful replies.
In the Command Prompt window, type ping APP1, and then press ENTER. There should be a successful name resolution to the IPv4 address 10.0.0.3 and four successful replies.
Snapshot the Configuration
This completes the Base Configuration test lab mini-module for the Corpnet2 subnet. To save this configuration for additional test labs, do the following:
On all physical computers or virtual machines in the test lab, close all windows and then perform a graceful shutdown.
If your lab is based on virtual machines, save a snapshot of each virtual machine and name the snapshots Windows Server 2012 Base Configuration with Corpnet2 subnet. If your lab uses physical computers, create disk images to save the Base Configuration.
