Forum Discussion
Hyper-V Default switch IP address range change. Ver 1809 Build 17763.1
In that same article:
"the end result is that (to begin with) that virtual machines on the internal virtual switch can talk to the host, but they cannot talk to the network that the host is connected to."
That's totally useless for me.
I want my Virtual machine to be able to talk to the host network and be accessible from the Internet or in case of a server, it host websites on ISS, provide VPN server connections to outside clients over the Internet.
my host is already behind a phyiscal router, putting my VMs on yet another NAT with different subnets makes things worse and impossible.
with External Virtual Swtich in Hyper-V, i can give an IP address (v6 or v4) to my VM and then put that VM's IP address in my physical router's DMZ so it can be accessible from the Internet.
that's how servers operate. Hyper-V does a great job by letting VMs directly be involved with the real network.
HotCakeX The VM can connect to the network using an internal switch if it's set up with a virtual NAT firewall. My local server VM can connect to Microsoft Update (and the rest of the local network + internet). However, only the host (my laptop) can initiate connections to the VM...which is perfect for a development testing scenario. There are other servers (vSphere VMs) that the code is pushed to when it's time to make it available to other people for testing and production.
- It's not.
- Yeah as you said it's off topic so i have no interest in discussing containers.
but as i said, using double NATs won't let servers be accessible from the Internet. specially if it's a nested virtualization that I use mostly. HotCakeX I'm not intending to argue with you and what I'm about to say is not directly related to the original topic of this thread, but you might be surprised at what's being done in "real-life" networking scenarios these days. The reason I switched from VMware to Hyper-V on my dev machine is because I need to work with Window Containers and Docker Desktop, which requires Hyper-V. Currently Hyper-V and VMware cannot coexist, but that is about to change. In the container world, VM's are just hosts for containers and usually many containers. For example IIS would not run directly on a server VM, but in a container. In larger scale systems like I work with, everything is redundant and disposable. For example, the web application I work on has many instances in production all sitting behind a reverse proxy (which itself is in a container). If one instance dies for some reason, no big deal, another is spun up to replace it. The containers are all behind a Hyper-V internal switch with NAT. Anyway, it you want to learn more about containers in the Windows world, here's a good place to start: About Windows containers
- Exactly what i said. the External Virtual Network switch is used for Real-Life scenarios. i wasn't talking about test purposes.
test purposes can have whatever strange settings they want.
Servers such ca CA, VPN, IIS, VDI etc are needed to connect to the outside world in order to do their job and serve. the Internet network would be already behind a NAT which belongs to the physical router.
there is no point in putting it behind yet another NAT.
the external IP address is 1 and when users from Internet want to connect to the Virtual Servers, they have limited possibilities, the best one would be to use VPN and then access the local network of the Servers/Clients but that also does Not need double NATs.
