SNA Server Setup Always Adds COMNETMN to Registry in Error
Article ID: 138863
Article Last Modified on 10/23/2003
APPLIES TO
- Microsoft SNA Server 3.0, when used with:
This article was previously published under Q138863
SYMPTOMS
When you install SNA Server 2.11, SNA Server Setup incorrectly adds a
second COMNETMN entry to the registry even though the existing entry is the
only entry necessary for SNA Server link services to send link alerts to
Netview, provided a Netview connection is configured in SNA Server Admin.
The second COMNETMN entry is added to the Windows NT registry under the
subtree HKEY_LOCAL_MACHINE under the following subkey:
SYSTEM/CurrentControlSet/Services/LanmanServer/Parameters/NullSessionPipes
CAUSE
SNA Server Setup fails to check if the COMNETMN pipe name is already
specified in the registry.
RESOLUTION
Obtain the update to SNA Server Setup mentioned below.
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):
KBCategory: kbnetwork kbbug2.11
KBSubcategory: ntnetserv
Additional query words: prodsna 2.11
Keywords: kbbug kbfix KB138863