Hyper-V installation, no network after reboot

Question

Hello everyone

I'll try to be clear about my questions and my problem.

I have a HP Proliant microserver gen10+ (xeon E2224 and 32go Ram) and have installed windows server 2022.

I've been installing and using Hyper-V for years with no problems, so I don't think I'm a beginner, but now I don't understand what's going on.

I have several network interfaces on my server, so I've configured interface 2 as fixed IP (xxx.xxx.xxx.6)

Using this IP address, I connected to the server via RDP to launch the installation (via the graphical user interface) of HyperV.

When it asked for the vswitch to be created, I selected my interface 2 and simply continued with the installation then rebooted the server as requested.

And here's the problem, after the reboot the network card is in limited connectivity (no network) and I can no longer connect to the server via rdp, I can only do so physically in front of the server keyboard.

When I go to the card's properties, I only have "Microsoft LLDP protocol driver" and "hyper-v extensible virtual switch" checked off.

By uninstalling Hyper-V everything returns to normal and I can connect to rdp via the fixed ip.

I tried to reinstall Hyper-V by passing the vswitch request, so not selecting my interface 2, same problem.

So I changed my strategy and connected 2 interfaces (2 and 3). The 2 is still in fixed IP (xxx.xxx.xxx.6) and the 3 in DHCP(xxx.xxx.xxx.206).

I connect via RDP to the server via the fixed IP of interface 2, launch the installation, and this time when I set up the vswitch, I select interface 3 and finish the hyper-V installation and reboot.

After the reboot, the fixed lP doesn't respond anymore, but I connect in RDP via the DHCP IP (xxx.xxx.xxx.206) without any problem and I'm connected via interface 3!

And when I go to see the network card configurations

interface2: only have "Microsoft LLDP protocol driver" and "hyper-v extensible virtual switch" checked off.

interface3: only have "Microsoft LLDP protocol driver" and "hyper-v extensible virtual switch" checked off.

vswitch created on interface 3 and in DHCP

The fixed IP configuration of my interface 2 has completely disappeared.....

Questions:

• Do you have an explanation for this crazy behavior?
• Why did it work with 2 interaces and not just one?
• Now that HyperV is installed and the vswitch has been created on interface 3, can I reconfigure interface 2 to a fixed IP without messing up the whole configuration now in place?

Thank you in advance

Answer 1

Hello Frederic,

Thank you for your question and for reaching out with your question today.

It seems like you're experiencing some unexpected behavior with Hyper-V and network configuration on your HP Proliant microserver gen10+. While I can't provide a definitive solution without access to your specific setup, I can offer some insights and suggestions that might help you troubleshoot the issue.

1. Explanation for the behavior:
   • The behavior you described could be due to a conflict between the Hyper-V virtual switch and the network configuration of the physical interfaces.
   • During the Hyper-V installation, when you selected interface 2 for the virtual switch, it might have disrupted the network configuration on that interface, causing the limited connectivity issue.
   • By selecting interface 3 during the installation and using it for the virtual switch, the issue might have been avoided because interface 2 was not directly associated with the virtual switch.
2. Two interfaces vs. one interface:
   • When you used two interfaces (interface 2 and interface 3), the issue might have been bypassed because the virtual switch was created on interface 3, while interface 2 remained unaffected.
   • Using two interfaces allowed you to access the server via RDP using the DHCP IP (xxx.xxx.xxx.206) assigned to interface 3.
3. Reconfiguring interface 2 with a fixed IP:
   • With Hyper-V already installed and the virtual switch created on interface 3, it should be possible to reconfigure interface 2 with a fixed IP without disturbing the existing configuration.
   • You can try reassigning a fixed IP to interface 2 through the network adapter settings in Windows Server 2022.
   • Ensure that the IP address you assign to interface 2 doesn't conflict with any other IP addresses in your network configuration.

Here are some steps you can follow to reconfigure interface 2:

1. Connect to the server physically or via RDP using the DHCP IP (xxx.xxx.xxx.206) assigned to interface 3.
2. Open the Network and Sharing Center in Windows Server 2022.
3. Click on "Change adapter settings" in the left-hand menu.
4. Locate interface 2, right-click on it, and choose "Properties."
5. In the Properties window, double-click on "Internet Protocol Version 4 (TCP/IPv4)" to access its settings.
6. Select the option to use a fixed IP address and provide the desired IP address, subnet mask, default gateway, and DNS server information.
7. Click "OK" to save the changes.
8. After reconfiguring interface 2, test the connectivity and verify if the fixed IP is working as expected.

Remember to take precautionary measures, such as backing up your server and network configurations, before making any significant changes. It's also recommended to consult the official documentation for your server and Hyper-V for any specific guidelines or known issues related to your hardware and software configuration.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Answer 2

So I put interface 2 back in fixed ip mode....but now, after rebooting, it's the "VEthernet virtual" switch card that indicates unidentified network and don't have network IP (check with ipconfig /all command)

in HyperV the virtual switch card is indicated as an "internal network type", so I switched it to "external network" and check the box "authorize the operating system to share this card" and...

the vm I've just installed, which is configured as a fixed ip, has neither network nor internet, it's nowhere to be found

now I don't know what to do

Thank you.

Answer 3

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

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 4

take a look at my previous answer, which I've changed ;)

that's exactly what I did, but my virtual switch card doesn't see my local network at all, it became totally isolated and independent (IP: 169.254.44.185) when I switched my interface 2 to fixed ip, whereas before it was in xxx.xxx.xxx.206 in my network and have internet and network access

Answer 5

Try installing the hyper-v role and create a new external vSwitch using one of the other (yet unused) network interfaces for the VMs also uncheck the box for "allow management to share with adapter" to avoid the additional vEthernets being created for host since this seems to be causing you multi-homing madness.

--please don't forget to upvote and Accept as answer if the reply is helpful--