This article was previously published under Q186873
This article has been archived. It is offered "as is" and will no longer be updated.
On a network running NetBIOS over TCP/IP, you may notice that, if aclient's connection to a Windows NT server fails or experiences a loss ofsession, this causes delays in sending or receiving data from other clientsto and from the server.
During a failed or disconnected client session to the server, you maynotice, using Network Monitor, that you can see the server is receivingpackets from the other clients; however, NetBIOS is not passing packetsback up to the clients. This will also show that all the send buffers havebeen consumed and they are waiting for the server to respond (this is witha low level NetBIOS ACK, not a NetBIOS packet). The Network Monitor traceshows that TCP/IP has already ACK'd these packets but the NetBIOS layer hasnot.
It will appear that the NetBIOS layer is blocked, waiting for somethingjust after the lower level protocol has notified it of a session failure.
NOTE: The problem does not occur until TCP/IP sees that there is a timeout.
When in this state, the NetBIOS interface will not process any command.Even simple commands like Adapter Status will be blocked. You may pass anyNO_WAIT commands to NetBIOS; however, these will not be processed until itrecovers.
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 theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
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.