• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Hyper V - Networking ?

M

marley1

Supreme [H]ardness
Joined
Jul 18, 2000
Messages
5,447
I installed Hyper-V the other day and messing around with it. Any reason to use any of the Internal Network? Seems like everything would be on External?

Can someone give me a quick run down of when you would use Internal or Private?

I would say I would have a NIC dedicated to the host Hyper-V machine, then do 2 NIC teams for an external for the virtual machines, and then 2 more external if we did shared storage or something?
 
A private network ensures that the virtual machine(s) you are running don't see or interfere with the outside world (both the internet and your own regular intranet). You can test and develop things things like Active Directory without risk of interference to your production systems. This way you don't have to be the guy who installed a copy of Win2003 to do some testing and didn't realize DHCP was enabled by default until after several days of trying to diagnose why people had random problems logging in and had to reboot. It can also be taken a step further, to see how intentionally hostile code (viruses) behave on a network without exposing real resources.
 
Or say in a small, non redundant environment you have a single VM host running an AD, web server, WSUS and a firewall that logs to SQL along with an SQL server that supports the above. Absolutely nothing not on the VM host or even the VM host itself really needs to communicate with the SQL server so why open it up for attack when you could make an internal only network and add a network interface to any VM that needs to talk to the SQL server. Basically any sort of back end server or service that doesn't need to be directly accessed from off the VM host.
 
You must log in or register to reply here.
Back
Top