You are currently offline, waiting for your internet to reconnect

Error message: Users cannot log on to a workstation

This article was previously published under Q160783
This article has been archived. It is offered "as is" and will no longer be updated.
You receive the following error message when you use anon-Administrative account on a workstation to log on to a domain.

Windows NT-based client computer

Your account is configured to prevent you from logging on and using thisworkstation. Please try another workstation.

Other Windows-based client computers

The user is not allowed to log on from this workstation.
Depending on the client, the associated network message number 2240 mayalso be included with the error message.

Windows 2000-based clients may also receive the following error message during an attempt to map a drive letter to the server:
Unable to impersonate using a named pipe until data has been read from that pipe.
This issue may occur if the security event log is full, and CrashOnAuditFail is enabled. CrashOnAuditFail may be enabled on a Windows NT 4.0 computer if the C2 Configuration Manager (C2Config.exe) has been run on the computer. When the security log size reaches capacity, only administrators can access the server.

This issue may also occur if the user account is configured to log onfrom specific workstations.

Note The Logon To option is in the User Properties dialog box.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

To resolve this issue, clear the security log andrun C2CONFIG to reset the CrashOnAuditFail value.To do this, follow these steps:
  1. Restart the computer and log on using an account in the Administrators group.
  2. Use Event Viewer to clear all events from the security log, archiving the currently logged events. For details, see the "Event Viewer" chapter in the Windows NT Workstation or Windows NT Server System Guide.
  3. Click Start, click Run, type regedit in the Open box, and then click OK.
  4. Locate and then delete the
    registry entry from the following registry subkey:
  5. Quit Registry Editor, and then restart the computer to cause the change to take effect.
For additional information about the
registry entry, click the following article numbers to view the articles in the Microsoft Knowledge Base:
149393 CrashOnAuditFail activates on shutdown with ProcessTracking
178208 CrashOnAuditFail with Logon/Logoff Auditing causes blue screen
140058 How to prevent auditable activities when security log is full
Microsoft has confirmed that this is a bug in Windows NT version 3.5x and Windows NT version 4.0. Microsoft is researching this problem and will post new information here inthe Microsoft Knowledge Base as it becomes available.
permit access policy registry

Article ID: 160783 - Last Review: 12/04/2015 15:53:47 - Revision: 4.4

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft LAN Manager 2.2c, Microsoft Windows for Workgroups 3.11, Microsoft Windows 95, Microsoft Network Client 3.1

  • kbnosurvey kbarchive kbbug kberrmsg KB160783