Workstation password change breaks mapped drive login

[Guest]

Environment;

Clients = XP pro
Server = Win2K server
Network - peer, no domain

User profiles/passwords on workstations are different from
profiles/passwords on the server.

Workstation login -limited user- (example) WSUSER, password "a"
Server folder access (example) SRVRUSER, password "b"

Issue;

We have *some* workstations that, when the workstation password for WSUSER
is changed from "a" to a new one, the folder access fails because the server
is looking for SRVRUSER, password "b".

We presently work around this by;

Disconnecting the drive, removing the map entirely

Remap using SRVRUSER password "b" and check the dialog box to save this user
and password login information.

This works until it's time to change the password on the workstation agian,
then we have to disconnect and remap and check the box.

I know, there should be a domain and not use the workstation login, but
that's not an option right now.

How can we force the XP Pro workstations to retain the drive map using
SRVRUSER profile and password "a" when we change the workstation login
WSUSER's password? Some fail and some don't.

It's gotta be a simple fix, but darned if I can find it..

 

[Lanwench [MVP - Exchange]]

Environment;

Clients = XP pro
Server = Win2K server
Network - peer, no domain

User profiles/passwords on workstations are different from
profiles/passwords on the server.

Workstation login -limited user- (example) WSUSER, password "a"
Server folder access (example) SRVRUSER, password "b"

Issue;

We have *some* workstations that, when the workstation password for
WSUSER is changed from "a" to a new one, the folder access fails
because the server is looking for SRVRUSER, password "b".

We presently work around this by;

Disconnecting the drive, removing the map entirely

Remap using SRVRUSER password "b" and check the dialog box to save
this user and password login information.

This works until it's time to change the password on the workstation
agian, then we have to disconnect and remap and check the box.

I know, there should be a domain and not use the workstation login,
but that's not an option right now.

How can we force the XP Pro workstations to retain the drive map using
SRVRUSER profile and password "a" when we change the workstation login
WSUSER's password? Some fail and some don't.

It's gotta be a simple fix, but darned if I can find it..

I don't think this is a simple fix. If you change a password in one place,
you need to either change it in the other place, or delete/recreate the
drive mapping so the user will be prompted for the server-side password. And
it will always do this (ask for the password) until you change the password
on the server to match.

There's no way to sync passwords in a workgroup. This is yet another reason
to use a client/server domain model...you already have Win2k server, so why
not use it? And then store all data in a central location so you can easily
back it up and have some semblance of 'version control', which you don't
have now....just my two cents.

 

[Guest]

I don't think this is a simple fix. If you change a password in one place,
you need to either change it in the other place, or delete/recreate the
drive mapping so the user will be prompted for the server-side password. And
it will always do this (ask for the password) until you change the password
on the server to match.

There's no way to sync passwords in a workgroup. This is yet another reason
to use a client/server domain model...you already have Win2k server, so why
not use it? And then store all data in a central location so you can easily
back it up and have some semblance of 'version control', which you don't
have now....just my two cents.

Thanks for the reply!

Configuring a domain would be better, but unfortunately beyond my control to
do so. I did find
http://support.microsoft.com/default.aspx?scid=kb;en-us;306541 which sheds
some light on the subject. With this it seems I'd be able to manage them
separately, albeit clumsily without central management. I'll need to test
though and need to figure out why some connections break on local password
change and some don't.

Another thing I might try is NET USE and specify persistent=yes (although I
think that's the default).

Any more ideas welcome...

 

[Guest]

I did find

http://support.microsoft.com/default.aspx?scid=kb;en-us;306541 which sheds
some light on the subject.

Checked link, seems I put a broken one in my post. It is KB 306541 though...
title in the KB is "How To Manage Stored User Names and Passwords on a
Computer That Is Not in a Domain in Windows XP"

EG