Can't logon to domain after changing password

27 Oct 2006 1:30 PM

RKinch

I have a customer with a Windows 2003 Small Bus. Server and a Windows XP Pro
workstation. After changing her password as required by the password policy,
she has trouble logging onto the domain. It tells her she can't connect and
none of the drive letters are mapped (which come from her logon script). If
she manually deletes all her previous persistant connections and then logs on
again, then her drive letters will show up. But the next time, she'll be
right back where she started.

The symptom also shows up in Outlook, where it won't accept her logon
credentials for her .pst file, which is located on one of the mapped drives.

She's changing her password in the normal way, but it seems like Windows XP
is still trying to use the previous password to authenticate in some cases
for some reason. All the other stations on the network work normally even
after changing passwords.

27 Oct 2006 2:24 PM

RKinch

An additional note: The Windows Server event logon shows event ID 529
(invalid username or password) with the domain listed as the name of the
server rather than that of the domain.

The workstation shows event ID 1006 and 1030 and talks about invalid
credentials.

Show quoteHide quote

"RKinch" wrote:

> I have a customer with a Windows 2003 Small Bus. Server and a Windows XP Pro
> workstation. After changing her password as required by the password policy,
> she has trouble logging onto the domain. It tells her she can't connect and
> none of the drive letters are mapped (which come from her logon script). If
> she manually deletes all her previous persistant connections and then logs on
> again, then her drive letters will show up. But the next time, she'll be
> right back where she started.
>
> The symptom also shows up in Outlook, where it won't accept her logon
> credentials for her .pst file, which is located on one of the mapped drives.
>
> She's changing her password in the normal way, but it seems like Windows XP
> is still trying to use the previous password to authenticate in some cases
> for some reason. All the other stations on the network work normally even
> after changing passwords.
>

27 Oct 2006 6:13 PM

Lanwench [MVP - Exchange]

In news:DA943E5C-9251-4A1C-9A13-DB92874EC361@microsoft.com,

RKinch <RKi***@discussions.microsoft.com> typed:

> I have a customer with a Windows 2003 Small Bus. Server and a Windows
> XP Pro workstation. After changing her password as required by the
> password policy, she has trouble logging onto the domain. It tells
> her she can't connect and none of the drive letters are mapped (which
> come from her logon script). If she manually deletes all her
> previous persistant connections and then logs on again, then her
> drive letters will show up. But the next time, she'll be right back
> where she started.

Not using wireless, are you?

>
> The symptom also shows up in Outlook, where it won't accept her logon
> credentials for her .pst file, which is located on one of the mapped
> drives.

Oops. Don't do that.

MS doesn't support accessing PST files on LAN/WAN connections.
http://support.microsoft.com/?id=297019

And, since you have Exchange, you really ought not to use PST files at all.
See
http://www.exchangefaq.org/faq/Exchange-5.5/Why-PST-=-BAD-/q/Why-PST-=-BAD/qid/1209

>
> She's changing her password in the normal way, but it seems like
> Windows XP is still trying to use the previous password to
> authenticate in some cases for some reason. All the other stations
> on the network work normally even after changing passwords.

You might post in microsoft.public.windows.server.sbs. I'd post an unedited
ipconfig /all from the server, and from this user's workstation (clearly
labeled as to which is which).