NetBT Tears Down TCP Session with Many Concurrent File Transfers

 Last reviewed: February 3, 1998
Article ID: Q161968
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.51 and 4.0
  • Microsoft Windows NT Server versions 3.51 and 4.0

SYMPTOMS

Copying files from one computer running Windows NT to a UNC path on a second computer running Windows NT may fail if the Windows NT machine is under heavy stress. This usually occurs when there are multiple, concurrent, file transfers in progress. If the file transfers are initiated by an application, the application initiating the file transfer may log events with error 59 ("An unexpected network error occurred"). A network sniff of the failure will show a TCP RESET segment being sent by the computer running Windows NT that is doing the writing.

CAUSE

When under a heavy load, Windows NT may send multiple server message blocks (SMBs) in the same network segment. Rdr.sys was incorrectly assuming the response to the Session Setup & X would be the only SMB in the segment and was taking more data than it should.

RESOLUTION

To resolve this problem, obtain the following fix or wait for the next Windows NT service pack.

This fix should have the following time stamp: 

   Windows NT 4.0

   01/21/98  05:32p               264,144  Rdr.sys (Intel)
   01/21/98  05:29p               511,312  Rdr.sys (Alpha)
NOTE: Service Pack 3 must be applied to Windows NT 4.0 prior to applying this fix. 

   Windows NT 3.51

   01/26/98  04:58p               260,384  Rdr.sys (Intel)
   01/26/98  04:55p               471,664  Rdr.sys (Alpha)
NOTE: Service Pack 5 must be applied to Windows NT 3.51 prior to applying this fix.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. 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.

Microsoft has confirmed this to be a problem in Windows NT version 3.51. A supported fix is now available, but is not 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 Product Support Services for more information. 

Keywords          : kbbug3.51 kbbug4.00 kbfix3.51 kbfix4.00 ntnetserv NTSrvWkst kbnetwork
Version           : WinNT:3.51,4.0
Platform          : winnt
Issue type        : kbbug
Solution Type     : kbpatch

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 3, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.