Frame Type Entries for NWLink Must Appear in Uppercase

Last reviewed: September 9, 1996
Article ID: Q123314
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5
  • Microsoft Windows for Workgroups version 3.11

SUMMARY

Due to compatibility issues with some versions of NetWare 3.x, the NWLink protocol code was developed in such a way that frame type entries appear in uppercase only in both the PROTOCOL.INI and NET.CFG files. This article lists the frame type entries for the NWLink protocol.

MORE INFORMATION

To correctly modify network configurations, use the Network Setup program in Windows for Workgroups version 3.11. However, the two files can also be modified manually. When you do this, the modification of the frame type must conform to the uppercase specification made in the NWLink code. This means that both the frame variable and frame type values must appear in uppercase only.

Valid Frame Type entries for Ethernet are:

   ETHERNET_802.2
   ETHERNET_802.3
   ETHERNET_II
   ETHERNET_SNAP

Valid Frame Type entries for Token Ring are:

   TOKEN_RING
   TOKEN_RING_SNAP

An example of a valid entry in PROTOCOL.INI and NET.CFG is:

   FRAME=ETHERNET_802.2

NetWare is manufactured by Novell, Inc., a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.


Additional reference words: prodnt 3.50 3.11 wfwg
KBCategory: kbnetwork
KBSubcategory: ntinterop



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: September 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.