other cached id when connecting as user.

[bmiller]

I have a user that mapped a drive from domain 2k
workstaion to a stand alone XPpro machine using local XP
account. Once user changed his Domain password he started
to get account lockout issues and it looks like it is
associated w/ this connection - Does anyone know why?

Thanks, B

 

[Lanwench [MVP - Exchange]]

Any reason you don't want to join this PC to the domain and have the user
log into the domain? Then you can use login scripts and all that fun stuff.

Try net use * /del

and then re-mapping the drive.

 

[bmiller]

What and make things simple? No, No, No I love banging my
head against the wall. (It is a contractor's laptop and we
are abiding by his wishes....).

I did get this resolved by disconnecting the drive. What
doesn't make sense is that it looks like it takes the
logon user's credentials in addition to the 'connect as'
user - like a daily scheduled task runs until the password
becomes invalid...I was just thinking that since it
was 'connect as' that would overide.

 

[Lanwench [MVP - Exchange]]

How was he mapping the drive before?

What and make things simple? No, No, No I love banging my
head against the wall. (It is a contractor's laptop and we
are abiding by his wishes....).

I did get this resolved by disconnecting the drive. What
doesn't make sense is that it looks like it takes the
logon user's credentials in addition to the 'connect as'
user - like a daily scheduled task runs until the password
becomes invalid...I was just thinking that since it
was 'connect as' that would overide.