TC can't handle changed mapped drives

[HBB]

Win7HP-64 with TC7.55a :

When a mapped drive letter (which is currently assigned to any network location) is assigned to another network location, TC can not handle it.

EDITED >>> After reboot, it handles...

[ghisler(Author)]

Did you start TC with a different user name? Network drives are user-specific.

[HBB]

same username and password for both sharing...
However, as I said, after reboot it worked with same account.

EDITED >>> I tested that Windows explorer accessed new mapped drive while TC does not.

[karlchen]

Hello, HBB.

In this testing environment I cannot reproduce the reported problem:
+ Windows Server 2008 R2, 64-bit
+ Total Commander 7.55a
(As Server 2008 R2 and Windows 7 share the same code base, T.C. should not behave differently on Windows 7 than it does on Server 2008 R2.)

Steps:

First for server1, server2, server3 the following steps were performed
+ net use K: \\server{1,2 or 3}\share
+ test that T.C. can access drive K: no matter which share it points to
+ net use K: /dele
+ next server in the list

Next the drive letters where changed, too.
For server1, server2, server3 the following steps were performed
+ net use H: \\server{1,2 or 3}\share
+ test that T.C. can access drive H: no matter which share it points to
+ net use H: /dele
+ check that drive H. was gone in T.C.
+ net use J: \\server{1,2 or 3}\share
+ test that T.C. can access drive H: no matter which share it points to
+ net use J: /dele
+ check that drive K: was gone in T.C.
+ next server in the list

No problems were encountered.

Kind regards,
Karl

[HolgerK]

The problem occurs if you map the drive as "Protected Administrator" and restart TC "As Administrator".
While Explorer still runs as "Protected Administrator", TC now has "Elevated Administrators" rights.

Run As Administrator loses access to mapped drives

Regards
Holger

[karlchen]

Hi, Holger.

All right I see. And I admit, I was logged on using an administrative account all the time, but not elevated. Administrator in private gear.

So the essence of the thread which you link to is that it is not a fault caused by T.C., but the intended behaviour of Windows: the unelevated administrator and the elevated administrator are almost like two different accounts.

Side note:
How do you manage to have the right article / thread at hand for every Windows issue in the world? You must have stored all available links in an enormously large Oracle database.

Karl

[HolgerK]

How do you manage to have the right article / thread at hand

N-way associative cache for the right key words between the ears and google search.

Holger

[HBB]

I observed this problem when I replace the server machines (PCs). I had prepared the new server which is identical with old one, except computer name and tcp-ip because of sharing issues. At the same time, the old server was already running.

In my PC, I firstly disconnet the mapped drive letters which linked to old server, then, I connected same drive letters to the new server (same account name, same password and same shared folder names, but different machine, different computer name and IP) :
Old sharing : S:\ --> \\Machine1\Shared\
New sharing : S:\ --> \\Machine2\Shared\

Since I always start TC as run as administrator, I don't think the problem is due to different administrator permissions. However, as I write before, windows explorer could handle while TC does not. So, Holger's link is not valid for this case according to me.

Unfortunately, I do not have any possibility to test this situation again. Because I cancelled the old server. If I have another opportunity to test this problem with two different machines, I will report it.

Regards.

[karlchen]

Hello, HBB.

Hm, to me your post seems to suggest that HolgerK's post does apply: the drive mapping / unmapping / re-mapping is done by the administrator in un-elevated mode (via "net use" or via Explorer?). But T.C. is run by the administrator in elevated mode.

Kind regards,
Karl