The information in this article applies to:
SYMPTOMSIn certain circumstances, the Microsoft Client for NetWare Networks may send an NCP over the network with the Task ID field of the NCP header improperly set as zero. This can cause the client computer to stop responding (hang) and the NetWare server to abend. CAUSEThis problem can occur if the Novell NetWare Server expects a task ID not equal to zero. In certain circumstances, it receives a client request with the task ID set to zero and abends as a result. The client stops responding waiting for a reply from the server. RESOLUTIONA supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later:
NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee. For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base: Q154871 Determining If You Are Eligible for No-Charge Technical Support STATUSMicrosoft has confirmed this to be a problem in the Microsoft Client for NetWare Networks. Additional query words:
Keywords : |
Last Reviewed: December 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |