Net2Com and RAS Can Conflict on LANA Number

Last reviewed: May 15, 1997
Article ID: Q114867
The information in this article applies to:
  • Microsoft Windows NT Resource Kit for Windows NT and Windows NT Advanced Server version 3.1

SUMMARY

The Net2Com utility included with the Windows NT Resource Kit uses only LANA 0 as its protocol path to the network. Other protocols such as Remote Access Service (RAS) may use the same LANA number.

MORE INFORMATION

LANA is a number given to a specific path from the application layer through a protocol stack, to a specific network card.

To check what LANA number a protocol is using:

  1. In the Control Panel window, choose the Network icon.

  2. From the Installed Network Software list box, choose NetBIOS Interface, and then choose the Configure button.

  3. The NetBIOS Interface dialog box displays the Network Route and the LANA Number. Please note:

          NBF is NetBEUI
          NBT is NetBIOS over TCP/IP
          NWBLINK is NetBIOS over IPX
          RASHub is a RAS link
    

  4. Make sure that the Network Route for RAS is not set to LANA 0. To ensure connection between the workstation and the server, it is important that LANA 0 on both computers use the same networking protocol (NetBEUI, TCP/IP, IPX, and so on).

The products included here are manufactured by ESDL Incorporated, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.


Additional query words: prodnt reskit
Keywords : kbother ntreskit
Version : 3.1
Platform : WINDOWS


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 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.