APPC Problem Handling AP_PGM Security with NULL Password

 Last reviewed: February 1, 1996
Article ID: Q139678
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, versions 2.0, 2.1 and 2.11

SYMPTOMS

If an APPC application issues an Allocate using AP_PGM conversation security and specifies a password of NULL (where the remote system is configured with conversation security and a zero-length password), the Allocate will fail with a sense code of 080F6051 (AP_SECURITY_NOT_VALID).

CAUSE

Instead of sending a zero length password in the FMH-5 Attach message, the SNA Server APPC library sends a 1-byte password set to a value of "0x40", instead of specifying a NULL password as it should.

RESOLUTION

Microsoft has updated the files, WAPPC32.DLL (for Windows NT), WINAPPC.DLL (for Windows 3.x), and APPC.DLL (for OS/2), to correct this problem.

STATUS

Microsoft has confirmed this to be a problem in SNA Server for Windows NT. This problem was corrected in the latest SNA Server for Windows NT, 2.11 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

KBCategory: kbnetwork kbprg kbbug2.00 kbbug2.10 kbbug2.11
KBSubcategory: ntnetserv
Additional reference words: 2.00 2.10 2.11 prodsna

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