Microsoft KB Archive/164763

= CSNW Fails to Connect to Preferred Server =

Article ID: 164763

Article Last Modified on 2/27/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows NT Workstation 3.51
 * Microsoft Windows NT Workstation 4.0 Developer Edition
 * Microsoft Windows NT Server 3.51
 * Microsoft Windows NT Server 4.0 Standard Edition

-



This article was previously published under Q164763



SYMPTOMS
Client Services for NetWare (CSNW) clients may fail to connect to their preferred server with the following error:

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?



CAUSE
This problem only occurs if the following steps are used:
 * 1) A CSNW client creates a new printer, or prints to an existing printer during a logon session.
 * 2) The CSNW client logs out.
 * 3) The CSNW client immediately logs back on as the same user without restarting the workstation.

The problem occurs because the previous preferred server connection is never closed. It may fail to close if the Logon User ID (LUID) for the previous logon session was not released after a new printer was created or if an existing printer was used.

The previous logon session was not released because its LUID, which is maintained by the kernel, has a reference counter that is incremented when the user's credentials are impersonated (used) and decremented when the impersonation is released.

When the reference counter for an LUID reaches 0, the kernel notifies the Local Security Authority (LSA) that the user has logged out. The LSA then notifies CSNW to disconnect the user's preferred connection to the NetWare server. In this case, the LUID for the user who is currently logged on is never decremented to 0, so the LSA is never notified, which causes CSNW to never be notified of the logout to disconnect from the preferred server.



RESOLUTION
Currently, only a workaround exists for this problem. To enable the workaround, use the following steps:

For Windows NT 4.0
 Whenever a new printer is created, shut down and restart the workstation at the end of the day instead of logging out. Disable all spooler event logging using the following steps:  Open Printers in Control Panel. Click File and select Server Properties. Click the Advanced tab on the Print Server Properties page. Disable all Log Spooler options.</li> Click OK, and then shut down and restart.</li></ol> </li></ol>

For Windows NT 3.51
<ol> Whenever a new printer is created, shut down and restart the workstation at the end of the day instead of logging out.</li> Disable all spooler event logging using the following steps:

WARNING: Using Registry Editor incorrectly can cause serious, system- wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk. <ol style="list-style-type: lower-alpha;"> Run Registry Editor (regedt32.exe).</li> Go to the following key:

</li>  Add the following value: <pre class="fixed_text">     EventLog = REG_DWORD 0x00000000

</li> Close Registry Editor, and then shut down and restart.</li></ol> </li></ol>

For Windows 2000
Clear the following check boxes to work around this behavior:

Log Spooler error events

Log Spooler warning events

Log Spooler Information events

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbbug kbprint KB164763

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.