STOP 0x0A in Redirector with Invalid Server Responses (224428)



The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition
  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Workstation 4.0
  • Microsoft Windows NT Server, Enterprise Edition 4.0

This article was previously published under Q224428

SYMPTOMS

When you scan directories, query file information, or do named pipes transactions against a server, the client may experience a STOP 0x0A in Rdr.sys.

This error may happen when there is an intermediate network device between the client and the server or when the network adapter of one of the nodes corrupts the data in the frames. You may see this in a network trace while the problem happened, or the corruption can be seen in the memory dump written on the client.

CAUSE

The redirector checks for invalid SMB responses. It performs these checks only when the return code returned by the server is ERROR_SUCCESS. Especially with transactions (on named pipes), it may happen that the server returns errors like ERROR_BUFFER_TOO_SMALL or ERROR_MORE_DATA.

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for 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 the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.

Modification Type:MinorLast Reviewed:9/23/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE KB224428