What is event id 4321?
Event ID 4321 — NBT Naming. Updated: April 17, 2008. NBT (NetBIOS (network basic input/output system)) over TCP/IP (Transmission Control Protocol/Internet Protocol) naming provides mapping between NetBIOS names and IP addresses. Product: Windows Operating System.
Did not allow the name to be claimed by this machine?
The machine with the IP address %4 did not allow the name to be claimed by this machine. Your computer cannot access the network because it could not contact the Windows Internet Name Service (WINS) server to register its name . This could be caused by loss of network connectivity.
What does NetBIOS over Tcpip enabled mean?
NetBIOS over TCP/IP provides the NetBIOS programming interface over the TCP/IP protocol. It extends the reach of NetBIOS client and server programs to the wide area network (WAN). It also provides interoperability with various other operating systems.
Should I disable NetBIOS over TCP IP?
A. Yes. To improve performance, it’s recommended that you disable NetBIOS over TCP/IP on your cluster network NIC and other dedicated-purpose NICs, such as for iSCSI and Live Migration. NetBIOS isn’t used in Server 2008 R2 clusters.
Do I need NetBIOS enabled?
NetBIOS is legacy and you only need it if you are using old applications or old versions of Windows that require it or use WINS. If your running applications or OS’s that require it still, NetBIOS is probably not the real problem here.
How to fix error 4321 (fix NetBT)?
Error Event ID 4321 (Fix NetBT) Hi, Your computer has failed to register itself in WINS server. NetBT is responsible for registering your computer in WINS server. Check your WINS server settings by : 1. Go to Network Connections. 2. Choose your network and view its properties.
Why can’t my NetBT see more than one Nic?
So now you just have to disable NETBIOS over TCP/IP on one of them so then your NETBT can only see one NICs means just one IP address.
Is NetBT responsible for this problem?
And yes NETBT is responsible for this problem. The main problem you are facing is that you are using two NICSs in the DC knowingly or not knowingly so what happening is your DC presently have two NICs which means you are using two different IP addresses. That’s why you are having this problem.