Event ID 4319, NetBT, Domain Controller with VM

RiverWild 96 Reputation points
2021-09-22T17:10:12.297+00:00

I am getting the error 4319 on my domain controller that has a hyper-v VM on it.
The first nic is for the DC, the second one does not have IPv4 protocol checked (I copied the last server).
Obviously there is a VSwitch also shown for the hyper-v vm which is set to DHCP.

On the VM, the nic is set to static IP and it shows up in the DNS of the DC with this static IP.
However, there are two entries in DNS for the DC. One is the static IP of the first nic and the other is the DHCP address of the VSwitch adapter.

Is this setup correct?
If so, why do I get error 4319?

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,843 questions
Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
1,021 questions
0 comments
Accepted answer
  1. RiverWild 96 Reputation points
    2021-09-23T13:00:49.317+00:00

    While those are good suggestions, they are for much larger organizations.
    I fixed the problem by unchecking the allow host to share button in VirtualSwitch of Hyper-V.
    This "hides" the VEthernet adapter which was showing itself as duplicate in DNS.
    Works fine now.

    Thanks for all your comments.

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 39,351 Reputation points
    2021-09-23T09:17:19.623+00:00

    Hello @RiverWild ,

    This is a logical error and can be ignored as long your services run as expected. The main reason is that Microsoft does not recommend to configure Hyper-V on a Domain Controller precisely for the different interactions that may have over the function of the server.

    In this scenario, you should have 2 NICs in order to assign an interface for DC and another for the VMs to avoid conflict. Even in this case (or if you have only 1 NIC) you are at risk to have what is called a "Multihomed" DC.

    Recommendation is: DC should only have ADDS and DNS, DHCP is even a stretch if you ask me.

    Hope this helps you,

    ------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments
  2. Dave Patrick 426.1K Reputation points MVP
    2021-09-23T12:57:45.693+00:00

    A better option is to install the hyper-v role (as only role) on host, then stand up a dedicated virtual machine for active directory domain services. Then add other virtual machines for other roles or applications.

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

    0 comments