CSNW Connection Leak When Running 16-bit Applications (175877)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Server 4.0
This article was previously published under Q175877 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 <NetWare Tree and Context> 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, click the following article number to view the article in the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUSMicrosoft has confirmed that this is 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.
Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbArtTypeINF kbbug kbfix kbinfo kbnetwork KB175877 |
---|
|