IPX May Not Work When Packet Size Is Larger Than Receive Buffer

This article was previously published under Q187939
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
IPX may not work, or data corruption may occur, with a receive-packetdriver when a token ring packet spans multiple receive buffers. Datacorruption is likely when the Receive buffer size on the client Windows NTcomputer is smaller that that of the Maximum transmit size of the WindowsNT server computer.

NOTE: The data transfers may seem to work but the data is corrupted if theNDIS packets are large enough to be split among receive buffers.

The IPX protocol allows packets to span multiple receive buffers, but onlytoken ring packets are large enough to do so. NDIS 4 token ring drivers,such as Ibmtrp.sys, that support the ReceivePacket function may encounterthis problem.
RESOLUTION
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

You can work around this problem by setting the maximum transmit size onserver computers to equal to or smaller than the receive buffer sizes ofclient computers.
STATUS
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.
Olicom ISA 16/4 (oc-3118) TR PCI MAU
Properties

Article ID: 187939 - Last Review: 10/09/2013 17:35:39 - Revision: 1.3

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB187939
Feedback