User Cannot Log On to LAN Because of RAS Logon Failures
This article was previously published under Q177125
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about editing the registry.Before you edit the registry, make sure you understand how to restore it ifa problem occurs. For information on how to do this, view the "Restoringthe Registry" online Help topic in Regedit.exe or the "Restoring a RegistryKey" online Help topic in Regedt32.exe.
When you attempt to log on to your local area network (LAN), you mayreceive the following error message:
Unable to log you on because your account has been locked out, please
contact your administrator.
contact your administrator.
NOTE: This error may occur even though you have not previously failed anylogon attempts.
With the Account Lockout feature in Windows NT enabled in User Manager,unsuccessful attempts to log on to the network through a Remote AccessService (RAS) connection will trigger the lockout. This prevents you fromlogging on to the LAN.
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 theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
This fix introduces a new feature called Remote Access Account LockoutManager (RAALM), which resolves the above problem by separating the twolockout mechanisms. By making the RAS lockout count lower than the AccountLockout, failed RAS logon attempts will not affect a user on the LAN fromlogging on to the domain. This is done by the RAALM revoking the dial-inpermissions of the user.
WARNING: Using Registry Editor incorrectly can cause serious problems thatmay require you to reinstall your operating system. Microsoft cannotguarantee that problems resulting from the incorrect use of Registry Editorcan be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys AndValues" online Help topic in Registry Editor (Regedit.exe) or the "Add andDelete Information in the Registry" and "Edit Registry Data" online Helptopics in Regedt32.exe. Note that you should back up the registry beforeyou edit it.
After you have applied the above fixes, follow these steps:
- If your primary user account database is on the RAS Server, skip to Step 2. If not, follow these steps:
- Install the Remote Access Account Lockout Helper service by running Raslock.exe at a command prompt.
- In Control Panel, open Services, and then select Remote Access Account Lockout Helper, and click Startup.
- Click Log On As This Account and enter an account and password that has appropriate permissions to edit user accounts, such as Administrator or Account Operators.
- Start Registry Editor (Regedit.exe or Regedt32.exe).
- Go to the following registry subkey:HKLM\SYSTEM\CurrentControlSet\Services\RemoteAccess\Paramete
- Edit the value MaxDenials to the number of consecutive bad password attempts before locking out the account.
NOTE: The default value of 0 disables RAS account lockout.
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.
Article ID: 177125 - Last Review: 10/26/2013 04:45:00 - Revision: 3.0
Microsoft Windows NT Server 4.0 Standard Edition
- kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kberrmsg kbfix kbnetwork KB177125