You are currently offline, waiting for your internet to reconnect

"Invalid Password" Error When Joining A Domain with Sysprep Image

This article was previously published under Q322175
This article has been archived. It is offered "as is" and will no longer be updated.
If you try to join a domain during Windows 2000 Setup preinstalled by using Sysprep or a Remote Installation Services (RIS) image, you may receive the following error message:
You have entered an invalid password. Would you like to proceed for now and try joining a domain later?
This error may occur even if you use a valid user name and password to join the domain.
This problem occurs if both of the following are true:
  • Your Windows 2000 Sysprep image is at Windows 2000 Service Pack 2 (SP2) level or Windows 2000 Service Pack 3 (SP3) level.
  • TCP/IP was installed in the original operating system installation that was used for the image, but the computer name was different from the name that is being used during Setup.
With TCP/IP preinstalled, Kerberos is used for authentication during the process of joining the domain. Incorrect code in Kerberos causes the computer name to be substituted for the user name that is supplied for authentication. Restarting the computer avoids the incorrect code because the computer name is already set and is not changed.

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later:
   Date         Time   Version        Size       File name   ----------------------------------------------------------   05-Jun-2002  11:29  5.0.2195.5781    123,664  Adsldp.dll   05-Jun-2002  11:29  5.0.2195.5781    131,344  Adsldpc.dll   05-Jun-2002  11:29  5.0.2195.5781     62,736  Adsmsext.dll   05-Jun-2002  11:29  5.0.2195.5801    358,160  Advapi32.dll   05-Jun-2002  11:29  5.0.2195.5265     42,256  Basesrv.dll   05-Jun-2002  11:29  5.0.2195.5855     49,424  Browser.dll   05-Jun-2002  11:29  5.0.2195.5595    135,952  Dnsapi.dll   05-Jun-2002  11:29  5.0.2195.5595     96,016  Dnsrslvr.dll   05-Jun-2002  11:29  5.0.2195.5722     45,328  Eventlog.dll   05-Jun-2002  11:29  5.0.2195.5684    222,480  Gdi32.dll   05-Jun-2002  11:29  5.0.2195.5859    145,680  Kdcsvc.dll   04-Jun-2002  14:31  5.0.2195.5859    199,952  Kerberos.dll   05-Jun-2002  11:29  5.0.2195.4928    708,880  Kernel32.dll   05-Jun-2002  10:50  5.0.2195.5861     71,024  Ksecdd.sys   05-Jun-2002  10:50  5.0.2195.5861    505,616  Lsasrv.dll   05-Jun-2002  10:50  5.0.2195.5861     33,552  Lsass.exe   04-Jun-2002  14:31  5.0.2195.5859    107,792  Msv1_0.dll   05-Jun-2002  11:29  5.0.2195.5855    307,472  Netapi32.dll   05-Jun-2002  11:29  5.0.2195.5723    360,208  Netlogon.dll   05-Jun-2002  11:29  5.0.2195.5839    916,752  Ntdsa.dll   05-Jun-2002  11:29  5.0.2195.5585    386,832  Samsrv.dll   05-Jun-2002  11:29  5.0.2195.5837    128,784  Scecli.dll   05-Jun-2002  11:29  5.0.2195.5757    299,792  Scesrv.dll   25-Jun-2001  19:17        47,808  User.exe   05-Jun-2002  11:29  5.0.2195.4314    402,192  User32.dll   05-Jun-2002  11:29  5.0.2195.5644    369,936  Userenv.dll   05-Jun-2002  11:29  5.0.2195.5859     48,912  W32time.dll   04-Jun-2002  14:32  5.0.2195.5859     57,104  W32tm.exe   31-May-2002  10:26  5.0.2195.5840  1,642,192  Win32k.sys   03-May-2002  11:31  5.0.2195.5731    178,960  Winlogon.exe   05-Jun-2002  11:29  5.0.2195.4602    243,472  Winsrv.dll   05-Jun-2002  11:29  5.0.2195.5737    125,712  Wldap32.dll				

To work around this problem, turn off the computer when you receive the error message. When you restart the computer, Setup starts again and the computer can join the domain.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product
For additional information about how to install multiple hotfixes with only one restart, click the article number below to view the article in the Microsoft Knowledge Base:
296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot

Article ID: 322175 - Last Review: 10/24/2013 11:45:34 - Revision: 4.8

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbwin2ksp4fix kbsecurity kbbug kbfix kbwin2000presp4fix KB322175