How to simulate external IP addresses on a single server Hyper-V test environment

Question

I just bought a powerful laptop and installed a spare copy of Server 2012 R2 Datacentre on it.
I am in the process of setting up a test LAN with DC, Exchange, TMG firewall web and backup servers.
V host without the use of external physical routing?
I would like to connect a client to the LAN services such as Exchange and VPN in the same way a client device connects to a network over the internet. In other words, I need to test the external IP addresses of my test LAN.
I am considering a setup consisting of two separate LANs with different IP address ranges:
LAN 1: internal network (with all the services mentioned above)
LAN 2: with only one client VM; this would be the external network (simulated internet)
Is this the best way of doing it? Has anyone already done something similar?
Many thanks!

Answer 1

I have something similar.
I don't believe your solution would work alone, as you'd need a VM to act as a router between the two. You could do it like that (but adding a virtual router) or you could just let WAN be your local network (the one your laptop is on)
Some steps (not very detailed, I can provide my documentation I wrote for Hyper-V running on server 2012 R2 (should work exactly the same for you though)
The first vSwitch created should be External type (it should already be created if you installed Hyper-V)
Create a second switch, call it whatever (Internal or LAN doesn't matter), set it's type to Private.
Create a small 512MB Generation 1 VM with a small (1GB should be fine, and it can be dynamic expanding)
Add two LEGACY (key point) network adapters to it, attach the first to the external and the second to the private.
Install pfSense onto it. You'll basically have a router. the first interface is the WAN (if you set the first adapter as external when you added them to the VM) or "the internet" you could say. While the private switch is the second interface or your local
(private) LAN. Now any VM you want to be on this virtual LAN just set it's network adapter to be connected to the Private vSwitch.
I have instructions if you want to do this (specifically for Hyper-V (I wrote them in case I ever had to reinstall it because there are a few gotchas with it being virtualized)