Article ID: 829652 - View products that this article applies to.
After you change your password, you cannot access the workstation if you log off and then try to log on again. This problem occurs after you log on to a workstation that contains cached credentials (password and domain), then change your domain password while you are connected to the domain by using a dial-up or a VPN connection, then log off, and then log on again. However, if you turn off the Automatically use my Windows logon name and password option, you can log on to the workstation.
This problem occurs because the new domain password is not synchronized with the password of the cached credentials. When you log off and then log on again without a network connection to the domain, you cannot access the workstation. If you turn off the Automatically use my Windows logon name and password option, the changed domain password is synchronized with the cached credentials. Therefore, you can log on.
Service pack informationTo resolve this problem, obtain the latest service pack for Windows XP. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322389/ )How to obtain the latest Windows XP service pack
Hotfix informationA 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
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, contact 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:
http://support.microsoft.com/contactus/?ws=supportNote 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 hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ------------------------------------------------------------- 25-Sep-2003 15:35 5.1.2600.1254 183,808 Gptext.dll 25-Sep-2003 15:27 5.1.2600.1271 74,240 Ipsec.sys 02-Aug-2003 00:37 5.1.2600.1254 98,304 Ipseccmd.exe 25-Sep-2003 15:35 5.1.2600.1254 334,848 Ipsecsnp.dll 25-Sep-2003 15:35 5.1.2600.1254 159,744 Ipsecsvc.dll 25-Sep-2003 15:35 5.1.2600.1254 364,544 Ipsmsnap.dll 25-Sep-2003 15:35 5.1.2600.1254 827,392 Oakley.dll 25-Sep-2003 15:35 5.1.2600.1254 98,304 Polstore.dll 25-Sep-2003 15:35 5.1.2600.1276 219,648 Rasapi32.dll 25-Sep-2003 15:35 5.1.2600.1254 55,808 Rasman.dll 25-Sep-2003 15:35 5.1.2600.1254 163,840 Rasmans.dll 25-Sep-2003 15:35 5.1.2600.1254 29,184 Winipsec.dll 22-Sep-2003 12:02 5.1.2600.1275 568,832 Xpsp2res.dll
To work around the problem, you may be able to log back on to the workstation by using your previous credentials. After you log on to the workstation, click to clear the Automatically use my Windows logon name and password check box in the Log on dialog box.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. This problem was first corrected in Microsoft Windows XP Service Pack 2.