Do Not Use MAC Address as NetBIOS Name with RAS

Last reviewed: May 14, 1997
Article ID: Q112548
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1

SUMMARY

Do not use your physical node address as a NetBIOS name with Remote Access Service (RAS). Use the workstation name instead.

MORE INFORMATION

The Remote Access server is a NetBIOS-level gateway. It maintains two or more NetBIOS stacks (network transport protocols). It communicates with the Remote Access client through an asynchronous stack over the telephone line and it communicates with Local Area Network (LAN) servers through the other NetBIOS stacks. To connect the remote client with the LAN, the RAS server acts as the remote client to the LAN and acts as a LAN server to the remote client.

To do this, the RAS server must replicate (that is, add) the NetBIOS names used by the remote client to its LAN stack(s) and add the NetBIOS names used by a LAN server to its asynchronous stack.

If either the remote client or the LAN server has a NetBIOS application that uses its physical node address as its NetBIOS name, the RAS server cannot add that NetBIOS name to the other stack because the NetBIOS add name query (command) returns with a duplicate name on the network and does not allow it.

Use the workstation name instead.


Additional query words: prodnt
Keywords : kbnetwork ntras NTSrvWkst
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 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.