Cannot Open Pipe for NetMN (Access Denied)

Last reviewed: April 14, 1997
Article ID: Q165653

The information in this article applies to:

Microsoft SNA Server version 3.0

SYMPTOMS

The following event will be logged in the application event log when a Netview Connection is defined in the Server Properties page:

   Cannot open pipe for NetMN (Access denied)

CAUSE

The problem is caused by missing a registry value.

RESOLUTION

Setup now adds the following registry entry when adding a Netview connection:

   HKEY_LOCAL_MACHINE\CurrentControlSet\Services\LanmanServer\Parameters
      \NullSessionPipes:REG_MULTI_SZ:COMNETMN

To resolve this problem, obtain the hotfix mentioned below.

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 3.0. This problem was corrected in the latest Microsoft SNA Server 3.0 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

Additional query words: sna Netmn
Keywords : kbbug3.00 kbfix3.00.sp1 kbnetwork prodsna snasetup
Version : 3.0
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix

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