The information in this article applies to:
SYMPTOMS
If you use the account lockout feature in User Manager on your Windows NT
RAS server, you may eventually see the following error in the System Log of
the Event Viewer:
CAUSEThis error results from an RAS client's exceeding the number of bad logon attempts permitted by the setting in the Account Policy option of the User Manager. WORKAROUND
By itself, the error message text for event 20077 does not provide the
information needed to identify the RAS client responsible for the error. To
track the source of the invalid logon attempts, you can enable the Auditing
for Logon Failure option. To do this, go into User Manager, open the
Policies menu, and use the Auditing option to enable Auditing for Logon
Failure." You should then be able to correlate the failed logon
error message with the RAS client that triggered the error.
STATUSMicrosoft has confirmed this to be a problem in Windows NT version 3.5 and 3.51. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATION
When the limit of bad logon attempts is exceeded, on a Windows NT 3.5 or
3.51 RAS client, the following error will display on the screen:
When the bad logon limit is reached but not exceeded by a Windows 95 dial-up networking (DUN) client to an NT RAS server, the client may display the following error:
When a Windows 95 DUN client exceeds the logon limit, the following error is displayed:
Additional query words: login logout freeze out lock
Keywords : kbinterop ntras NTInterop kbbug3.51 |
Last Reviewed: February 17, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |