Troubleshooting NetBT Error 4319

BFos 26 Reputation points
2021-04-14T20:28:13.827+00:00

Hi folks,

I’m trying to troubleshoot NetBT Error 4319. On a hardware server running 2012r2 I’m getting

NetBT Error 4319 : “A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.”

-This server is a domain controller, also running DNS, and DHCP for a relatively small network.
-It has two NICs that are not teamed.
-Each has a static IP assigned, call it 192.168.1.13 and 192.168.1.14, although the second does not have a default gateway assigned.
-IPv4 and IPv6 are checked for both in the NIC properties.

In my research sometimes this comes up with a domain controller that is also running RAS, or Wins server. I don’t use those.

And for what it’s worth, everything has been working fine on the server, as far as I know. Any help is appreciated, thanks!

Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,526 questions
0 comments No comments
{count} votes

Accepted answer
  1. Dave Patrick 426K Reputation points MVP
    2021-04-14T20:53:29.87+00:00

    Multi-homing a domain controller will always cause no end to grief for active directory DNS. Also note
    https://support.microsoft.com/en-us/topic/how-multiple-adapters-on-the-same-network-are-expected-to-behave-e21cb201-2ae1-462a-1f47-1f2307a4d47a

    A work-around for the netbt error
    http://www.jenovarain.com/2015/10/event-id-4319-netbios-over-tcpip-with-dual-nics/

    but multi-homing the domain controller will always present a problem.

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

    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. BFos 26 Reputation points
    2021-04-15T16:53:06.34+00:00

    Thanks DSPatrick. Very helpful! The first article was cut off for me but I read the second one. I see two static A records in DNS for the server in question "SV-005", one for each IP address. This must have been added by my predecessor. I'm not fully up to speed on what Active Directory is adding to DNS. Should I simply disable the 2nd NIC? Maybe I'm over thinking it.

    0 comments No comments

  2. Dave Patrick 426K Reputation points MVP
    2021-04-15T17:24:08.517+00:00

    Should I simply disable the 2nd NIC?

    Yes, I'd think that should solve the netbt problem and any potentials active directory DNS issues.

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

    0 comments No comments

  3. BFos 26 Reputation points
    2021-04-15T18:52:30.597+00:00

    Thanks, very helpful.