I have situation at a site where we have login scripts mapping a "home"
folder for users that create a "W:" . This mapping seems to lock access back
to the server when I try to access the server with the administrator account
while still being logged on as the user on the local machine. As soon as I
disconnect the "w:" I can then authenticate to the server as administrator.

Steps I have taken:

1.) reset permissions on the users shared home folder.
2.) deleted local profile
3.) checked "open shares" on server to make sure the account does not
already have a file or directory open or locked.

There are 7 or 8 other mapped drives in the users profile. And only when I
delete this one does it allow me to authenticate to the server as
administrator

Any help would be useful.

"cvogel" <cvogel@discussions.microsoft.com> wrote in message
news:B681748E-4BAD-436A-950B-A98A90D747AC@microsoft.com...
>I have situation at a site where we have login scripts mapping a "home"
> folder for users that create a "W:" . This mapping seems to lock access
> back
> to the server when I try to access the server with the administrator
> account
> while still being logged on as the user on the local machine. As soon as
> I
> disconnect the "w:" I can then authenticate to the server as
> administrator.
>
> Steps I have taken:
>
> 1.) reset permissions on the users shared home folder.
> 2.) deleted local profile
> 3.) checked "open shares" on server to make sure the account does not
> already have a file or directory open or locked.
>
> There are 7 or 8 other mapped drives in the users profile. And only when
> I
> delete this one does it allow me to authenticate to the server as
> administrator
>
> Any help would be useful.

This is by design. You MUST kill all existing connections before
making new connections under an admin account.