Hyper V lab environment question
I have a hyper V lab environment setup. I originally had it setup to a internal switch but wanted to change it to a external switch so I can get out to the internet.
I can get out to the internet if I set that machines to automatically get a ip address but I need to be able to communicate between the machine in the lab.
At my work place they have it setup so all the machines use the DC for DNS resolution and they set forwarders on the DNS server to get out to the internet. This doesnt seem to work in my lab envir. Is there a way to get the machines to see each other and get out to the internet as well?
I can get out to the internet if I set that machines to automatically get a ip address but I need to be able to communicate between the machine in the lab.
At my work place they have it setup so all the machines use the DC for DNS resolution and they set forwarders on the DNS server to get out to the internet. This doesnt seem to work in my lab envir. Is there a way to get the machines to see each other and get out to the internet as well?
We keep a .ISO of Windows Server 2008 R2 around for this very purpose. Install the OS, configure RRAS for NAT, and publish HTTPS inbound, RDP inbound, and SMTP inbound if there's a lab Exchange server.
Untangle and SOPHOS UTM are two freebies that can be used.
Set the VM up as per the OS of choice with two vNICs:
vNIC 0: 192.168.20.1 on Private vSwitch (Gateway for private subnet so set accordingly)
vNIC 1: DHCP or static on production/Internet External vSwitch
We set things up this way so we can have a DC, Exchange, RDS Farm, SQL, SharePoint, and any other number of workloads on the Private vSwitch with services published.
Untangle and SOPHOS UTM are two freebies that can be used.
Set the VM up as per the OS of choice with two vNICs:
vNIC 0: 192.168.20.1 on Private vSwitch (Gateway for private subnet so set accordingly)
vNIC 1: DHCP or static on production/Internet External vSwitch
We set things up this way so we can have a DC, Exchange, RDS Farm, SQL, SharePoint, and any other number of workloads on the Private vSwitch with services published.
You need a router. This can be Windows RAS, ICS, NAT Router, Linux box etc.
I left my Hyper-V environment a few months ago so I'm not where I can provide the exact setup. I forget which version of Hyper-V introduced the new default switch but that took care of ALL the NAT and sharing setup for you.
If your version doesn't that that switch available, go back to your internal virtual switch and configure the host to use Internet Connection Sharing (ICS):
https://social.technet.microsoft.com/Forums/windowsserver/en-US/d380e4c3-a9c0-483f-8fd9-11962b1f486c/enable-virtual-machine-to-access-internet-with-ics?forum=winserverhyperv
ICS did work for me but is a pain and needed hand-holding once in a while, so I would make the attempt to use the default if it is available. Once I moved to that, I never had a problem.
If your version doesn't that that switch available, go back to your internal virtual switch and configure the host to use Internet Connection Sharing (ICS):
https://social.technet.microsoft.com/Forums/windowsserver/en-US/d380e4c3-a9c0-483f-8fd9-11962b1f486c/enable-virtual-machine-to-access-internet-with-ics?forum=winserverhyperv
ICS did work for me but is a pain and needed hand-holding once in a while, so I would make the attempt to use the default if it is available. Once I moved to that, I never had a problem.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
no idea what the network topology is like outside of an internal and external switch
could be a firewall issue
could be a vlan configuration
could be something else that we don't know about