asked on

How to configure 2nd NIC on Hyper-V server?

I have a Hyper-V server with two VMs.
The physical machine has two NICs and I have configured one for a virtual switch using IP 192.168.1.254
The second NIC has just been connected to the physical switch so now I have two active ethernet connections on my Hyper-V.
What should I do with the second NIC?

Tom Cieslik

NIC #1 is configured as Virtual Switch so there is no IP address on this card anymore because its passing network traffic to VM. This NIC should be connected to your LAN.
NIC#2 is a physical NIC , has Internal IP and should be connected to your LAN as well

ClintonK

ASKER

NIC#2 is a physical NIC , has Internal IP and should be connected to your LAN as well

So I shouldn't create another virtual switch using NIC2? Without a virtual switch the VMs can't see the outside world.
I'm at a slight loss as to what the benefit is of having a second NIC - apart from having a spare one should NIC1 fail.

ASKER CERTIFIED SOLUTION

Philip Elder

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Tom Cieslik

Virtual switch is for sharing ONE server NIC to all VM without disturbing server connection
If you do have a Virtual Switch already you should be able connect VM to internet since your NIC that you've used for switch is connected to your network.

If you did created different subnet for VM, for example,, your LAN IP is 10.0.0.x and your VM network is 192.168.1.x then you must connect your Virtual Switch NIC to router with same subnet or you must create a route on your VM network to be able connect to Internet.

OR

You can assign same subnet for VM as you have in your network (LAN) then all VM will be able to connect to Internet and will be discoverable by your LAN devices.

ClintonK

ASKER

I have teamed the two NICs and used the team to configure a virtual switch.
The use of two NICs now makes sense. Thanks