JSI Tip 8511. You cannot log on, or you experience a long delay on domain computers that are running Windows 2000, Windows XP, or Windows Server 2003?

When you experience the subject behavior, one or more of the following may also be true:

The System event log records:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
User: N/A
Description: The Service Name service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

NOTE: The Service Name is one of the following:

Eventlog (Event Log)
HTTPFilter (HTTP SSL)
KDCSVC (Kerberos Key Distribution Center)
Netlogon (Net Logon)
NTLMssp (NTLM Security Support Provider)
PlugPlay (Plug and Play)
PolicyAgent (IPSEC Services)
ProtectedStorage (Protected Storage)
SamSs (Security Accounts Manager)

Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 7
User: N/A
Description: The Kerberos subsystem encountered a PAC verification failure. This indicates that the PAC from the client in realm had a PAC which failed to verify or was modified. Contact your system administrator.
Data: 0000: c0000192

The computer restarts before the log on dialog appears.

You may receive a lsass.exe - System Error, Object Name not found after the log on dialog appears. When you press OK, your computer may restart.

You experience a long delay when you try to browse through the domain list on the log on dialog box.

When the computer restarts, you experience a long delay before the log on dialog appears. When you attempt to log on to a domain account, you cannot log on, or you experience a long delay.

On Windows XP, or Windows Server 2003, you are notified that the hardware significantly changed after the last activation, and you may be required to reactivate Windows.

Device Manager doesn't show any devices.

The log on dialog does NOT respond.

CTRL+ALT+DEL does NOT function.

Manually starting a service results in lsass.exe - System Error, Object Name already exists and the computer restarts.

This behavior will occur if one or more services that run in the Lsass.exe or Services.exe process have been altered to no longer run as shared service processes.

NOTE: The Type data value of a service that runs in a shared process is 0x20, and a service that runs in a separate memory processes is 0x10.

Restart your computer and press F8 on the boot menu to select Last Known Good Configuration.

If the problems persist:

1. Restart your computer.

2. Press F8.

3. Select Safe Mode with Command Prompt.

4. At the Command Prompt, run the following FixType.bat file:

@echo off
setlocal
call :config Eventlog
call :config HTTPFilter
call :config KDCSVC
call :config Netlogon
call :config NTLMssp
call :config PlugPlay
call :config PolicyAgent
call :config ProtectedStorage
call :config SamSs
endlocal
goto :EOF
:config
set svc=%1
for /f "Tokens=*" %%a in ('Sc query %svc%^|Find "TYPE"^|Find /V "20"') do (
 @echo %%a
 sc config %svc% type= share 
)

NOTE: FixType.bat uses Sc.exe, built in to Windows XP and Windows Server 2003, or available in the Windows 2000 Server resource kit.

NOTE: If you received the activation notification, you MUST reactive your copy of Windows.