NetBIOS CALL to a Group Name Fails with TCP/IP-32

 Last reviewed: September 9, 1996
Article ID: Q125916
The information in this article applies to:
  • Microsoft TCP/IP-32 for Windows for Workgroups, versions 3.11 and 3.11a
  • Microsoft Windows for Workgroups version 3.11

SYMPTOMS

After converting a Windows for Workgroups workstation from TCP/IP-16 to TCP/IP-32 for Windows for Workgroups, some NetBIOS based client-server and peer-to-peer applications may stop working. Error messages indicate that the server or partner can not be found on the network.

CAUSE

NetBIOS applications use names to identify themselves and to address their partners and servers. To establish a connection with a partner, the application makes a NetBIOS CALL request to a particular name, and the protocol resolves the name to a specific machine. When resolving NetBIOS names for CALL requests, VNBT.386 ignores responses from group names.

STATUS

Microsoft has confirmed this to be a problem in TCP/IP-32 for Windows for Workgroups version 3.11. A fix to this problem is in development, but has not been regression-tested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Product Support Services for more information on the availability of this fix.

KBCategory: kbnetwork
KBSubcategory: nttcp ntprotocol
Additional reference words: 3.11 prodtcp32



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.