Article ID: 219345 - View products that this article applies to.
This article was previously published under Q219345
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
When you configure Microsoft Gateway (and Client) Services for NetWare (GSNW/CSNW) to use the Default Tree and Context logon option, your computer may connect to multiple servers in different contexts.
This problem occurs when you log on through a Novell NetWare Directory Services (NDS) tree containing more than one NetWare server. You may not be able to establish a connection to the server that responds to the GSNW/CSNW client's GetNearestServer (GNS) request. It is possible to use a connection to one server for authentication and logon, while using other licensed connections to other servers for mapped resources. This may create redundant licensed connections to multiple servers and has the potential to more than double the required number of licensed connections.
To resolve this issue, apply the hotfix listed below to your computer. This fix allows you to specify which server you run your authentication credentials against, giving you the ability to use the same computer for authentication and resource usage.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Then perform the following steps to modify the Windows NT registry:
To resolve this problem, obtain the latest service pack for Windows NT 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT Server 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.