This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 34%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hey guys, I was hoping I could get some help with this. I am using my desktop as a standalone hyper v host and I can't seem to get my VMs any internet access. My current setup is below:
Att gateway(external routing, DHCP, and NAT for my regular home network): 192.168.1.0/24
My desktop and where my lab resides on hyper v: 192.168.1.126
VM RRAS for routing in my homelab. Three interfaces: 192.168.10.1 for client network. 172.16.1.1 for DC subnet. 192.168.1.15 in my home network which allows my rras VM access to the gateway out to the internet and which I am trying to route through for my other VMs
VM Domain controller 1 and 2: 172.16.1.10 && 172.16.1.11
Client windows 10: 192.168.10.100
Every VM can ping every other VM across networks and within networks. The only one that can reach the internet and the home network is RRAS VM due to having an interface on the home network. Does anyone have any ideas as to why my VMs aside from RRAS can't route to the internet?
I was hoping to provide Internet access to my VMs without having to use an external switch on every host. Right now my RRAS host is the only one that can access the internet because of that external switch. Is this possible to accomplish while remaining on only internal switches and using RRAS for routing out to the home and public network?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I'd check the domain controller and problem member both have the static address of DC listed for DNS and no others such as router or public DNS. All should use the RRAS router Lan address for default gateway.
RRAS router should only have two active interfaces.
https://www.dell.com/support/kbdoc/en-us/000118763/configuring-windows-server-2012-r2-as-a-router
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just to clarify, I can't use a third interface? My lab environment has two separate subnets in it. Those can route between each other with RRAS but neither can get outside of the Hyper V host whether I have configured NAT or not on RRAS. All hosts use the DCs for DNS already. The third interface on RRAS is what allows it on my home network and and out to the internet. Only the RRAS machine can actually access the internet as of now
Apologies for the double comment:
It seems I spoke too soon. It took a while but after enabling NAT on RRAS between my DC subnet and out to my home network, it finally began working. I was trying to get the client subnet going too but it seems I can only NAT one subnet, but that's ok, as I don't absolutely need the client having internet.
Edit: figured out how to NAT the client network as well. This is completely solved now.
Thank you!
Sounds good, you're welcome.
Hello @EdwardSargeant-6222
Thanks for sharing your concern here.
Have you thought about Port-forwarding or Dynamic DNS?
BR,
Thank you! It turns out it was a NAT issue
