Oct 06 2023 08:48 AM
Dear community,
I've installed two Hyper-V Servers each on five machines. They are all connected to the Internet through their host. Connectivity to their neighbouring hosts is not possible, let alone to their Hyper-V buddies.
This is the installation media used:
I've had some Microsoft experience in the past but that is twenty years ago. I am picking this up as a side occupation for fun. Because it is fun when it works :)
Kind regards,
Bjarne Petersen
Oct 06 2023 01:51 PM
SolutionYou'll want to create an external vSwitch then plug the physical adapters into a common switch. When you create a new external vSwitch the internet protocols are removed from the adapter and the Hyper-V Extensible Switch protocol is added turning that physical port into a multi-port virtual switch. Connect your VMs to this vSwitch and use each VM's vEthernet to configure the addressing in the exact same manner as if it were a physical NIC
Oct 06 2023 08:37 PM
Oct 07 2023 06:14 AM
Do not edit any adapter properties. In Hyper-V Manager in the right-hand pane use Virtual Switch Manager to create a vSwitch
Oct 07 2023 03:40 PM
@Bjarne_Petersen just checking if there's any progress or updates? please don't forget to mark helpful replies.
Oct 10 2023 05:24 AM - edited Oct 10 2023 06:09 AM
The situation as of now is:
The vSwitch works!
Connectivity is good. Hosts systems communicate with eachother. Hosts communicate with vMachines. vMachines communicate with vMachines.
Oct 10 2023 06:20 AM
Glad to hear, thanks for coming back to let us know.
Oct 06 2023 01:51 PM
SolutionYou'll want to create an external vSwitch then plug the physical adapters into a common switch. When you create a new external vSwitch the internet protocols are removed from the adapter and the Hyper-V Extensible Switch protocol is added turning that physical port into a multi-port virtual switch. Connect your VMs to this vSwitch and use each VM's vEthernet to configure the addressing in the exact same manner as if it were a physical NIC