Jump to content
RESET Forums (homeservershow.com)
canuckcam

Windows Server 2019 Hyper-V NIC assignment

Recommended Posts

canuckcam
Posted (edited)

I upgraded a DL360 Gen8 lab server to Window Server 2019, and noticed that unlike 2016, I can no longer use just two ports for WAN, host LAN access and Hyper-V LAN access. I'm running Sophos UTM Home as a Hyper-V VM on both so I need two NICs in Hyper-V. I notice that when I try to put the Hyper-V Virtual Switch on eth2, it gives me an error that it's already bound to the Virtual Switch protocol. But in properties, it's unchecked!

 

I'm wondering if I'm missing something, or this will happen to my Microserver as well. And since the Microserver effectively only has two NICs for OS access, this won't work? Hope I've explained it clear enough?

 

Server 2016 on Microserver Gen8 and previously DL360 Gen8

eth1: WAN (not shared to hypervisor)

eth2: LAN (access to hypervisor and Hyper-V VMs)

 

Server 2019 on DL360 Gen8

eth1: WAN (not shared to hypervisor)

eth2: LAN (WS 2019 host/hypervisor)

eth3: LAN (Hyper-V virtual switch)

 

*and yes, the physical port assignments are correct. Not sure why but Windows identifies physical ethernet port 2 as #1 and port 1 as #2 yet ports 3 and 4 are correct!

 

Screen Shot 2019-05-22 at 12.10.18 AM.png

Edited by canuckcam

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...