IPX Doesn't Function Correctly over Token Ring Source Routing

 Last reviewed: May 19, 1997
Article ID: Q161714
The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0

SYMPTOMS

When you try to log on to a File and Print Services for NetWare (FPNW) server running on Windows NT 4.0 in a Token Ring environment where the client is separated from the server by multiple source routing bridges, the following error is returned: 

   Shell-332-76: Network Error on Server "servername":
   Error Receiving from Network;
   Abort, Retry, ?
The above error is what you would get on a Novell-only client. A VLM client gives a similar error.

CAUSE

Not enough buffer space is allocated to accommodate the Routing Information Field on the FPNW server.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

Additional query words: prodnt
Keywords : kbfix4.00.sp3 kbnetwork ntnetserv NTSrvWkst kbbuglist kbfixlist
Version : 4.0
Platform : WinNT
Issue type : kbbug
Resolution Type : kbservicepack

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 19, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.