Bugcheck When IPX Is Bound to Only Ndiswan Adapter

Article translations Article translations
Article ID: 185682 - View products that this article applies to.
This article was previously published under Q185682
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

A STOP may occur in IPX whenever it is the only protocol installed and bound only to the Ndiswan adapter.

RESOLUTION

To work around this problem, bind IPX to a valid network adapter or add an additional protocol. If a network adapter is not available add the MS Loopback adapter.

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 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 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.

Properties

Article ID: 185682 - Last Review: October 8, 2013 - Revision: 1.2
APPLIES TO
  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB185682

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com