The information in this article applies to:
SYMPTOMSCopying 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.
RESOLUTIONTo 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, please see the following article in the
Microsoft Knowledge Base: Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack To resolve this problem, obtain the following fix for Windows NT 3.51:
NOTE: Service Pack 5 must be applied to Windows NT 3.51 prior to applying this fix. STATUSMicrosoft has confirmed this to be 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.
Keywords : kbnetwork NT4SP4Fix kbbug4.00 ntnetserv kbfix4.00.sp4 kbbug3.51 kbfix3.51 NTSrvWkst |
Last Reviewed: April 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |