SP4 RAS server hangs up when RAS client tries to connect as Windows NT 3.1 dial-up server

Article translations Article translations
Article ID: 219380 - View products that this article applies to.
This article was previously published under Q219380
Expand all | Collapse all

Symptoms

When a Microsoft Windows NT 4.0 RAS client tries to connect to a RAS server computer running Windows NT Server 4.0 Service Pack 4, the RAS server unexpectedly hangs up the connection.

Cause

This problem occurs because the Ndiswan.sys driver for the RAS server in this particular hardware configuration becomes deadlocked. The deadlock occurs in the code that causes the NdisWanSend() API call to quit without contacting the RAS client. The RAS server then hangs up.

Resolution

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:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

Status

Microsoft has confirmed that this is a problem in Windows NT Server 4.0 and Windows NT Server 4.0 Service Pack 4. This problem was first corrected in Windows NT Server 4.0 Service Pack 5.

Properties

Article ID: 219380 - Last Review: August 2, 2012 - Revision: 3.0
Applies to
  • Microsoft Windows NT Server 4.0 Standard Edition
Keywords: 
kbhotfixserver kbqfe kbbug kbfix KB219380

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