Your account is locked out. The policy may setup to lock out your account after 5 unsuccessful login attempts.
Symptom: After logon to W2K, you may see a blank desktop or no desktop. If you use CTRL+ALT+DELETE to start Task Manager, you may find that Explorer.exe is not listed in the list of running tasks or processes. Starting a new instance of Explorer.exe does not resolve the issue.
Resolution: open Task Manager>File>New Task (Run). Type cmd.exe, and then press ENTER. If necessary, change to the %SystemRoot% folder. This is typically the Winnt or Windows folder. Rename the Shdocvw.dll file by typing ren shdocvw.dll shdocvw.old. Restart the computer.
Note: Other older files that may cause problems with Explorer.exe or the shell if they are located in %SystemRoot% folder: Browseui.dll, Comctl32.dll, Comdlg32.dll, Mlang.dll, Ole32.dll, Oleaut32.dll, Shdocvw.dll, Shell32.dll, Shlwapi.dll, Urlmon.dll, Wininet.dll, Setupapi.dll.
Symptom: you get a blue screen while logon one of the users. However other users work fine.
Cause: the profile was damaged. For consultants, refer to 083104TB
Symptoms: After you join a
Windows XP client to a Windows NT domain, the client may be unable to log on
to the domain.
Resolutions: This behavior occurs because the Windows XP client tries to sign or seal the secure channel. Windows XP does this by default. However, Windows NT is not configured to do this by default. To resolve this issue, open Local Security Policy from Administrative Tools. Under the Local Policies\Security Options node, double-click the Domain Member:Digitally encrypt or sign secure channel data (always) policy to open it and click Disabled.
Cause: it could be the name resolution issue, especially DNS issue.
Symptom: When attempting to logon using the Terminal Services client, you may receive the following error message: "Logon Message: You do not have access to logon to this session".
Resolution: By default, TS connection security setting allows only administrators to log on. To set custom TS connection permissions, go to Terminal Services Configuration>Connections folder. Right-click the connection (RDP-TCP)>Properties>Permissions, add the users or/and groups that needs access to this connection.
Q: When I tried to logon one of our servers locally, I found that there isn't local computer name there. Why?
A: If this is domain comptroller, it won't show the computer name.
Symptoms: When you start Windows, you may not receive a logon dialog box, or you may receive one of the following error messages:
"No network provider accepted the given network path". And "The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist". Or, the Change Passwords tab may be missing from the Passwords Properties dialog box. Note that this symptom occurs only if the second cause listed below is in effect. In addition, if you are not prompted to log on and then you immediately log off, you will then receive a prompt to log on.
1) The Primary Network Logon setting is not set correctly.
2) AutoLogon is enabled.
3) Group Policy may disable the logon dialog box.
This is a misleading message that really means that you didn't enter an acceptable password.
This web is provided "AS IS" with no warranties.
Copyright © 2002-2017 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.