Share via

Configuring a Hyper-V network with a network bridge

Пахомов Кирилл Евгеньевич 0 Reputation points
2024-12-29T19:15:44.1566667+00:00

Good health! Please tell me, help pliz:

Given:

The Domain Controller (hereinafter referred to as DC) for Windows Server 2022

the Hyper-V role is installed on the server to create a virtual machine (hereinafter referred to as VM) for the Microsoft Exchange Server mail server, so as not to install it on the DC.

in order to connect client PCs to the domain, a network bridge has been created (shared access to the adapter via the Control Panel)

that is, my IP settings in the VM were like this:

IP: 192.168.3.124

Subnet mask: 255.255.255.0

Main gateway: 192.168.3.1 (router's IP address because the domain controller is connected to the router)

DNS server: 192.168.3.3 (IP of the domain controller)/192.168.137.1 (IP of the network bridge)

I have created an External virtual switch (for receiving emails from the Internet and web access outside the server (from a smartphone, tablet))

Problem: The Hyper-V VM stops detecting the domain controller after each reboot - the domain itself (that is, instead of the domain: chuc228.ru , it shows the Network) and accordingly, the Exchange and Active Directory services on the VM stop working. Only a current reset of the network helps, but not for a long time.

Question: What do I need to do so that at the same time: the VM sees the domain controller and does not lose contact with it, the client PCs are connected to the domain controller via a network bridge and have web access from other devices to Exchange Server resources?

I tried to recreate the virtual switch. Bottom line: it's useless, it doesn't help. Anyway, after a few minutes, hours, the connection with the DC disappears.

I don't know what to do.

I am attaching a screenshot from the Network and Sharing Center.

image

Application: Screenshot of the Network and Sharing Center on the domain controller

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,494 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,777 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ian Xue 38,746 Reputation points Microsoft Vendor
    2024-12-31T01:53:42.3266667+00:00

    Hi Пахомов Кирилл Евгеньеви,

    Thanks for your post. From your description, it seems that there is some network connectivity issue in the bridge network. Before moving on, please help clarify that you have configured the right virtual switch with the following steps:

    1. Open Hyper-V Manager. A quick way to do this is to select the Windows button or key then type "Hyper-V Manager". If search doesn't find Hyper-V Manager, Hyper-V or the Hyper-V management tools are not enabled. See the instructions to enable Hyper-V.
    2. Select the server in the left pane, or select "Connect to Server..." in the right pane.
    3. In Hyper-V Manager, select Virtual Switch Manager... from the 'Actions' menu on the right.
    4. Under the 'Virtual Switches' section, select New virtual network switch.
    5. Under 'What type of virtual switch do you want to create?', select External.
    6. Select the Create Virtual Switch button.
    7. Under ‘Virtual Switch Properties’, give the new switch a name such as External VM Switch.
    8. Under ‘Connection Type’, ensure that External Network has been selected.
    9. Select the physical network card to be paired with the new virtual switch. This is the network card that is physically connected to the network.
    10. Select Apply to create the virtual switch. At this point you'll most likely see the following message. Select Yes to continue.
    11. Select OK to close the Virtual Switch Manager Window.

    Reference: Create a Virtual Network | Microsoft Learn

    Also, we have encountered similar issues that is associated with a driver issue. For whatever reason, the version of NIC driver in-use is incompatible with the Hyper-V Extensible Virtual Switch protocol that gets bound to the physical adapter when you associate it with an external vSwitch.

    Best Regards,

    Ian Xue

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.