Microsoft KB Archive/184832

From BetaArchive Wiki
Knowledge Base


Article ID: 184832

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition



This article was previously published under Q184832

SYMPTOMS

Your multihomed Windows NT computers may experience name conflicts intermittently and Event Viewer may log the following event:

   Event ID   : 4320
   Source     : NetBT
   Description: Another machine has sent a name release message to this
                machine probably because a duplicate name has been
                detected on the TCP network. The IP address of the node
                that sent the message is in the data. Use nbtstat -n in a
                command window to see which name is in the Conflict state.
                

CAUSE

The server service on your multihomed Windows NT computers is not releasing its registered NetBIOS name from your Windows Internet Name Service (WINS) server properly. Only the primary network interface card (NIC) is being released while the other NICs are maintaining the registration of the server service.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack




STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Microsoft has confirmed this to be a problem in Windows NT version 3.51. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next service pack that contains this fix. Contact Microsoft Technical Support for more information.


Keywords: kbhotfixserver kbqfe kbbug kbfix KB184832