This article was previously published under Q182444
This article has been archived. It is offered "as is" and will no longer be updated.
In a Token Ring network, NBF clients are disconnected from the server afterreceiving the following message:
Drive x not available
A network trace shows either:
An NBF REJ frame from the client because the server skips an NBF sequence number sending data. The server and the client never recover from this state and the server finally disconnects.
The client sends an SMB read raw and the server no longer answers. the server and client exchange POLL - FINAL frames and finally disconnect.
In a Token Ring source routing network, NBF uses the source routinginformation to calculate the maximum datasize it can use. During the stagesof the NBF connection setup, frames are received through different pathscontaining a different amount of source routing information. Because of thedifferent amount of Token Ring source routing information, the maximumdatasize was calculated incorrectly.
If NBF tries to send the maximum calculated amount of data after setting upthe connection, the network card discards these packets because they aretoo long. NBF retries several times and then disconnects.
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.