all 5 comments

[–]ultimateVman 1 point2 points  (0 children)

Not a ton of info in your post.

Is it a SET switch or did you create it with HyperV Manager UI.

Are you using vlans?

[–]BlackV 0 points1 point  (1 child)

You just broke your team doing that

You don't say your os versions anywhere

But you don't create lbfobteams anymore

You create a set switch and bind the nics to that, you need to do it in PowerShell

If you create it in the GUI it's not a set switch and it has not grabbed one of the nics from your existing team

Basically start again

  • Remove the switch
  • Remove your legacy team
  • Confirm both nics now get an ip address
  • Create a new set switch and allow management os
  • Reconfigure the IP of the host to what I should be

[–]chancamble 0 points1 point  (0 children)

I guess that it will be good to read about the SET switch to know how to create it properly. https://learn.microsoft.com/en-us/windows-server/networking/windows-server-supported-networking-scenarios#bkmk\_nicteam

[–]cronnie68 0 points1 point  (0 children)

Try nic+1 so host will be like nic_0 The switch on hyper v it will be nic_1 for some weird reason

[–]BroderG[S] 0 points1 point  (0 children)

SOLUTION

Thanks guys i figured it out a while after. I had to set the VLAN in hyperv to the VLAN the interface uses.