Navigation section

multihomed server issue

About this tag
The multihomed server issue tag covers problems arising when a Windows server has multiple network interfaces or IP addresses, leading to NetBIOS name registration conflicts. In a recent thread about an in-place upgrade from Server 2016 to Server 2025, users reported 4321 NetBT errors where a server's name could not be registered on a specific IP because another device claimed it. This often involves misidentified IPs belonging to application servers rather than domain controllers. Troubleshooting includes verifying DNS configuration, checking for duplicate IP assignments, and reviewing NetBIOS settings. The tag is relevant for IT administrators managing file servers, domain controllers, or any multihomed Windows Server deployments.
  1. P

    4321 NetBT errors after in place upgrade from Server 2016 to Server 2025

    I recently ran an in-place upgrade of 2 file servers from 2016 to 2025, upon completion both servers are reporting "The name "(Local Domain Name):1d" could not be registered on the interface with IP address 10.16.1.70. The computer with the IP address 10.16.1.38 did not allow the name to be...
    • perskine77
    • Thread
    • in place upgrade issues multihomed server issue name registration conflict netbios over tcp/ip
    • Replies: 4
    • Forum: Windows Server Forums
Back
Top