Configuring Hyper-V for multiple subnets with only one NIC (Server 2012 R2 Edition)

Configuring Hyper-V for multiple subnets with only one NIC (Server 2012 R2 Edition)

Check with support before doing this in a production environment. I use this configuration in my lab and that’s my intention for guidance.

Assuming you have Hyper-V loaded already, lets get started!

Open Hyper-V Manager and click on Virtual Switch Manager on the Actions pane.

Click New virtual network switch on the left and click Create Virtual Switch on the right

On the New Virtual Switch Network window, fill in the following fields.

• Name: vNet Internal 10.10.10.0/24 (you can name these whatever you want; I like to keep mine named after the respective subnet)
  
• Notes: (optional)
• Connection type: Internal network
• Click Apply

On the New Virtual Switch Network window, fill in the following fields.

• Name: vNet Internal 10.10.20.0/24
• Notes: (optional)
• Connection type: Internal only
• Click OK

On the New Virtual Switch Network window, fill in the following fields.

• Name: vNet External
• Notes: (optional)
• Connection type: External network (select your network adapter in the drop down)
  
• Click OK

You can add as many as you want/need by repeating the above steps.

Open Server Manager, select Local Server and click Manage > Add Roles and Features from the upper right corner

On the Before You Begin page, select the check box to Skip this page by default and click Next

On the Installation Type page, select Role Based or feature-based installation and click Next

On the Server Selection page, select your Local Server and click Next

On the Server Roles page, select Remote Access and click Next

On the Features page select RAS Connection Manager Administration Kit (CMAK) and under Remote Server Administration Tools > Remote Administration Tools select Remote Access Management Tools and click Next.

On the Role Services page, select DirectAccess and VPN (RAS) and Routing. If prompted by the Add Roles and Features Wizard, select Add Features and click Next.

Review the Web Server Role (IIS) page and click Next

On the Role Services page, click Next

On the Confirmation page, [you may need to specify a path to your Server 2012 R2 Installation files]

[whoops! highlighted the wrong selection, click the one under the highlighted one]

Click the link to Specify an alternate source path

Enter the location of your SxS folder on the installation media when prompted and click OK

Click Install to begin the installation

Ok, now that the installation is complete, click Close to complete the wizard.

Now that we have the bits installed, it’s time to configure them.

Pop over to your Start menu and look for this icon

If you don’t see it, simply start typing (while on the Start menu) “Rou” and you should see the icon:

Go ahead and right click that and Pin it to the Start menu, then click it to open the RRAS Configuration Wizard

From here, it’s time to configure. It’s pretty much the same steps required from Server 2008 R2, so we’ll go ahead and work through them quickly.

Right click on Server Status and click Add Server

When the Add Server menu opens, select This computer if it’s not already selected, and click OK

Right click your server and select Configure and Enable Routing and Remote Access

Click Next at the setup wizard

Select Custom configuration and click Next

Select NAT and LAN routing

Selecting NAT will allow your virtual machines to access the internet. If this isn’t your intentions, do NOT select this setting

Review your selections and click Finish

Click Start Service when prompted

You’ll need to configure your network adapters in the VMs to the proper configurations and you also need to assign your NICs to the appropriate network in the VM settings! You can refer back to my 2008R2 guide to see how I had them configured…I used the same configurations with the 2012 setup.