Error Message: System Cannot Log You on Because Domain <Computername> Is Not Available

ID: Q244671

The information in this article applies to:
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
  • Microsoft Windows 2000 Professional
  • Microsoft Windows 2000 Server
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

When you attempt to log on to a computer, you may receive the following error message immediately after you type your user name and password:

System cannot log you on because domain Computername is not available
where Computername is the name of the local computer you are trying to log on to.

NOTE: This behavior also occurs after you start into Safe mode and attempt to log on locally.


CAUSE

This behavior can occur if the required cryptography files are missing, corrupted, or do not match the cryptography information stored in the registry (for example, if the registry is configured to use 128-bit encryption, but the 128-bit encryption files are not on the computer).


RESOLUTION

To resolve this issue, use one of the following methods.

Method 1: Default Windows 2000 Security Provider

If you are using the default Windows 2000 security provider, use the standard Windows 2000 repair options or Recovery Console to verify the required cryptography .dll files are intact. Refer to the "More Information" section of this article for file details.

Method 2: Alternate Encryption Package

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

If you installed an alternate encryption package before this behavior occurred, you may need to modify the registry to use standard encryption and successfully log on.

To modify the registry, you must perform a parallel installation of Windows 2000 or use Recovery Console to copy the Software registry file onto removable media so you can edit the file on another computer (the Software registry file is located in the %SystemRoot%\System32\Config folder and is named Software with no extension).
  1. From a computer running Windows 2000, start Registry Editor (Regedt32).


  2. From the HKEY_Local_Machine window, click the HKEY_LOCAL_MACHINE key.


  3. On the Registry menu, click Load Hive.


  4. Locate the Software file, and then double-click it.


  5. In the Key Name box, type test, and then press ENTER.


  6. Double-click the Test key, and then locate the following entry:


    7. Microsoft\Cryptography\Defaults\Provider Types\Type 001
  7. Double-click the Name value and change its name to Microsoft Base Cryptographic Provider v1.0.

    NOTE: This action sets the base encryption back to its default, but should allow you to log on to the system.


  8. Click the Test key.


  9. On the Registry menu, click Unload Hive.


  10. Ensure the modified Software file is placed back into the Winnt\System32\Config folder on the computer that is not working.


This change allows you to log on to the computer, but sets the encryption level back to base encryption. You may need to reinstall any encryption packs or encryption software after you make these changes to regain the encryption level you want.


WORKAROUND

If you do not have enough free space to perform a parallel installation of Windows 2000, or you cannot copy the Software file to removable media using Recovery Console, use the following steps to work around the issue:

  1. Start into Recovery Console.


  2. Use the cd (change directory) command and go to the %SystemRoot%\System32\Config folder.


  3. Rename the Software file to Software.old.


  4. Use the cd (change directory) command and go to the %SystemRoot%\Winnt\Repair folder.


  5. Copy the Software hive to the Config folder (for example, copy software c:\winnt\system32\config\software).


  6. Quit Recovery Console.


  7. Restart the computer and log on normally.

    NOTE: This Software hive does not contain all the changes that you have made to the computer since its initial installation. If you keep this Software file in place, you may have to reinstall all your software unless you make changes to the original file (Software.old), as outlined in the "Resolution" section of this article (Method 2).


  8. Modify the Software.old file using the steps in the "Resolution" section of this article (Method 2).


  9. After you modify and save the file, restart into Recovery Console.


  10. Locate the %SystemRoot%\System32\Config\ folder.


  11. Rename the existing Software hive (for example, rename Software to Software.repair).


  12. Rename the original file that you fixed to its previous name (for example, rename Software.old to Software).

    NOTE: This action puts the original Software hive with the one modification back into place so all your program settings are now back in the registry.


  13. Quit Recovery Console and restart the computer.



MORE INFORMATION

The following list shows Microsoft encryption providers and their associated .dll file name:

  • Microsoft Base Cryptographic Provider v1.0 uses the Rsabase.dll file.


  • Microsoft Base DSS Cryptographic Provider uses the Dssbase.dll file.


  • Microsoft Strong Cryptographic Provider uses the Rsaenhs.dll file (installed with High Encryption Pack).

    NOTE: Because the Rsaenhs.dll file is not included in Windows 2000 and is installed during the installation of High Encryption Pack, this file is not checked or replaced when you repair system files. You must check and replace this file using Recovery Console if the file is missing, corrupted, or is an incorrect version.



REFERENCES

For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

Q229716 Description of the Windows 2000 Recovery Console
Q235364 Description of the SET Command in Recovery Console

Additional query words: 128bit

Keywords : kbenv kbtool
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbprb


Last Reviewed: December 29, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.