Lab: Using Windows Server 2008 R2 as a Simple NAT Router

We have a number of lab setups that require the VMs to be on their own Private Network in Hyper-V but still have access to the Internet.

In some cases we need to have access to that private network and the VMs just as we would a product network.

In comes Windows Server 2008 R2 SP1. We set up the VM with two vNICs. One is connected to the Private Network while the other is connected to the Internet via our internal production network (gives us quick access to the lab VMs).

1. We install the OS
2. Install Integration Services.
3. Install the Network Policy and Access Services Role.
4. Run the Configure and Enable Routing and Remote Access.
5. Choose VPN and NAT
• 
6. Set the WAN connection.
7. Allow DHCP to be set automatically.
8. No RADIUS for authentication
• 
9. Click OK to the DHCP Relay warning.

We now have an internal router that will allow the VMs on the Private Network to reach out to the Internet.

Finally, to publish internal services via the WAN connection:

1. Click on NAT under IPv4
• 
2. Right click on the WAN Interface in the centre pane and click Properties.
1. Click on HTTPS (443) and a window pops up.
2. Enter the IP address of the server hosting HTTPS and click OK.
3. Tick the check to the left of HTTPS and then click Apply (if it did not do so).
• 
4. Repeat for the needed published services.
5. Test the connections:
• 
• 

In the end, it should take no more than 20 minutes to have the first router configured.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Windows Live Writer