DOCUMENT:Q175877 10-AUG-2001 [winnt] TITLE :CSNW Connection Leak When Running 16-bit Applications PRODUCT :Microsoft Windows NT PROD/VER:WinNT:4.0 OPER/SYS: KEYWORDS:kbnetwork kbWinNT400sp4fix kbinfo kbArtTypeINF ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Windows NT Workstation version 4.0 - Microsoft Windows NT Server version 4.0 - Microsoft Windows NT Server version 4.0, Terminal Server Edition ------------------------------------------------------------------------------- SYMPTOMS ======== When you use Client Services for NetWare (CSNW) or Gateway Services for NetWare (GSNW) to connect to a NetWare server and you are running a logon script or manually invoking a 16-bit application on a NetWare server, you may receive the following error when you attempt to log back on: NetWare Authentication Failure You cannot be authenticated on due to the following reason: A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached. Do you want to select another preferred server or context? CAUSE ===== The NetWare server has Limit Concurrent Connections for your user account set to 1. When the client logs off after running the 16-bit application, the connection on the NetWare server is not closed. This results in an unlicensed connection on the NetWare server. The connections are cleaned up if the user shuts down and restarts the server before logging back on. NOTE: You can determine if a connection is unlicensed by going to the NetWare server, loading monitor, and then selecting the active connection list. Unlicensed connections will have an asterisk (*) in front of the user name. RESOLUTION ========== You can work around this problem by performing any of the following: - Set the concurrent connections for your user account to a higher value on the NetWare server. -or- - Shut down and restart the workstation after each use. To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, please see the following article in the Microsoft Knowledge Base: Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack STATUS ====== Microsoft has confirmed this to be a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4. MORE INFORMATION ================ For additional information on ensuring that the connection leak is fixed, please see the following article in the Microsoft Knowledge Base: ARTICLE-ID: Q174676 TITLE : "NetWare Authentication Failure" Logging On to NetWare Server ====================================================================== Keywords : kbnetwork kbWinNT400sp4fix kbinfo kbArtTypeINF Technology : kbWinNTsearch kbWinNTWsearch kbWinNTW400 kbWinNTW400search kbWinNT400search kbWinNTSsearch kbWinNTS400search kbWinNTS400 kbNTTermServ400 kbNTTermServSearch Version : WinNT:4.0 Issue type : kbbug Solution 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. Copyright Microsoft Corporation 2001.