• 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 VM and Private IPs

B

Blade1

n00b
Joined
Jan 10, 2013
Messages
3
Hi,

I need to assign a private IP to a VM in Hyper-V 2012. However, this never results in internet connectivity. The Hyper-V server has 2 NICs, one private and one public.


With this server setup, how can I get a private IP working in a VM?

Apologies if this is a naive question!


Do I need to assign 2 NICs to the VM for the private and public IP?
Should the vswitch type be external?



Apologies, I am a bit lost!

Thanks
 
Yes you need to use external if the VM is communicating with something other than the host, or other hosted VMs on that physical server.

Also, make sure connectivity works on one of your virtual NICs first before configuring the other. When you have dual NICs on different subnets you have to configure your default gateway on the one that will be accessing other networks.

If both adapters need to move to different subnets you can configured a gateway on each, but depending on the VM app that will be running it can be a problem.
 
what are you using to connect to the internet? is your server also serving as the router (ala pfsense, untangle) or are you using a hardware router (netgear, linskys, etc)?

according to what you've described...you don't have anything connected to the WAN side (public)

1 nic should be assisgned to a vswitch where all your "internal" vm's connect to.

1 nic is assigned to the WAN side which your "router" should be connected to. the "router" should also be connected to the "internal" vswitch.

again, not enough info on your setup to really tell you what's wrong.
 
You must log in or register to reply here.
Back
Top