Unexpected Result in NCB Callname After Canceling a Listen

 Last reviewed: November 21, 1997
Article ID: Q162681
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0
  • Microsoft Windows NT Server versions 3.5, 3.51, and 4.0

SYMPTOMS

A Windows NT NetBIOS application's network control block (NCB) may appear corrupted. If Ncb.listen is posted with an asterisk (*) for the called name, the string "nnection context" is returned in the NCB callname structure whenever Ncb.listen is canceled before a client responds to it.

CAUSE

The remote address of the client should be copied to the NCB structure on the completion of the listen. However, because a client did not respond to the listen, the unexpected string is copied to the structure.

STATUS

Microsoft has confirmed this to be a problem in Windows NT versions 3.5x and 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Because the NCB callname is not used when Ncb.listen is canceled, this problem does not negatively affect NetBIOS applications.

Additional query words: prodnt call cancelled
Keywords : kbbug3.50 kbbug3.51 kbbug4.00 ntgeneral NTSrvWkst kbnetwork
Version : WINNT:3.5 3.51 4.0
Platform : winnt

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