Microsoft KB Archive/174676: Difference between revisions

From BetaArchive Wiki
m (Text replacement - "<" to "<")
m (Text replacement - ">" to ">")
 
Line 53: Line 53:
NetWare Authentication Failure<br />
NetWare Authentication Failure<br />
<br />
<br />
You cannot be authenticated on <NetWare Tree and Context&gt; due to the<br />
You cannot be authenticated on <NetWare Tree and Context> due to the<br />
following reason: A connection to the server could not be made because<br />
following reason: A connection to the server could not be made because<br />
the limit on the number of concurrent connections for this account has<br />
the limit on the number of concurrent connections for this account has<br />

Latest revision as of 01:46, 21 July 2020

Knowledge Base


NetWare Authentication Failure When Logging On to NetWare Server

Article ID: 174676

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition



This article was previously published under Q174676

SYMPTOMS

After you log off and then back on to a Novell NetWare server using Client Services for NetWare (CSNW) or Gateway Services for NetWare (GSNW), you may receive the following error message:

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

Windows NT does not disconnect from the NetWare server before attempting to log on again, and the setting to limit concurrent connections for your NetWare user account is enabled and set to 1 on the server.

RESOLUTION

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




STATUS

Microsoft 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.


Additional query words: ipx spx nds directory services bindery 3.11 3.12 4.1 4.00

Keywords: kbhotfixserver kbqfe kbbug kbfix kbwinnt400sp4fix KB174676