RAS Server Does Not Support the Full NetBIOS 3.0 Specification

Last reviewed: April 11, 1996
Article ID: Q149685

The information in this article applies to:

Microsoft Windows NT Advanced Server versions 3.5, 3.51, 4.0
Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
Microsoft Win32 Software Development Kit versions 3.5, 3.51, 4.0

SUMMARY

Windows NT Remote Access Server (RAS) supports most NetBIOS 3.0 commands with a few exceptions. Three features are not supported:

Sessions can only be established with a unique name, not a group name.
The NCBFINDNAME command is unsupported.
The first byte of a NetBIOS name must be a non-zero value.

MORE INFORMATION

The NetBIOS support in RAS was designed to support Windows NT redirector over NetBIOS, not to be fully compliant with the NetBIOS specification. A secondary goal was to support the majority of existing NetBIOS applications (like Lotus Notes).

All widely used NetBIOS commands are supported, and the few that are not supported are both uncommon and complex to implement in a RAS context.

REFERENCES

IBM NetBIOS 3.0 Specification

Additional reference words: 3.50 3.51 4.00 netbios group unique findname
ras rasapi win32
KBCategory: kbprg kbtshoot
KBSubcategory:

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