I'm looking to setup RRAS on a 2008 R2 box with two physical NICs and one "virtual" NIC for Hyper-V
One NIC ("WAN Connection") is connected to the WAN and assigned a static public IP. The other NIC ("LAN Connection") is simply connected to a switch. The Hyper-V connection ("Virtual Connection") needs to be able to obtain public IPs for a handful of VMs on the server.
Ideally, the following is how the setup should be configured: WAN connection is connected to the WAN and gets a public static for use on the server host OS. Then, LAN Connection acts as a router to assign private IPs to any devices that are connected to the physical 5 port switch. Virtual Connection needs to be able to get public IPs for the VMs, most of which are DHCP entries but one or two need static public IPs.
I am completely new to RRAS and know nothing about it so I was overwhelmed after looking at it. As a temporary solution, I setup WAN connection as a virtual switch from the Hyper-V networking options so that Virtual Connection could use it to get public IPs for the host OS and the VMs. I then enabled ICS on Virtual Connection so that it was shared with LAN Connection, which let LAN Connection assign private IPs to anything connected to the switch. The problem I found is that it's extremely unreliable and it seems that I need to almost daily disconnect and reconnect all three interfaces to get it working again.
Since RRAS is much more robust than ICS, (and ICS is frowned upon in a business setting anyhow) could someone advise me on how to accomplish the same setup through RRAS?