Network disk mapping bugs

ross104 · Post by *ross104 » 2013-10-26, 13:04 UTC

What we've got:
Windows 8.1 64 Bit
SAMBA share on Ubntu, mapped as network disk Y
SAMBA share on HD Player, mapped as network disk Z

What I've discovered:
1. After rebboting of a PC Total Commander shows that network disks are not accessible, but windows shows that drives are connected ok. When I click on a drive icon Total Commander opens network disk without a problem.

2. Most interesting. In some moment Total Commander shows:
Image: http://imageshack.us/a/img39/6623/1ep9.jpg
All free drive letters become used by Samba share network disk.
Sametime windows show me correct letters of correct network drives...
Image: http://imageshack.us/a/img13/9838/t119.jpg

Whrere to dig to find a solution for this bug?

Post by *ghisler(Author) » 2013-10-27, 14:23 UTC

Are you running TC with different user rights (elevated)? Network connections are user-specific.

ross104 · Post by *ross104 » 2013-10-27, 19:51 UTC

Yep.. It is set to run under Administrator.

Post by *ghisler(Author) » 2013-10-28, 15:08 UTC

OK, then you need to configure the connections for this user separately, e.g. by connecting the drive from TC, or run cmd.exe from TC and use "net use".

ross104 · Post by *ross104 » 2013-10-29, 07:09 UTC

Tried both ways - and those shares disappear after rebooting the PC.

Built a batch file like this:
NET USE Y: \\Ubuntu\Storage /PERSISTENT:NO /User:user pass
NET USE Z: \\Popcornhour\share /PERSISTENT:NO
And set it to run at startup. So Windows shows mapped network drives ok, total doesnt show them at all.

Post by *ghisler(Author) » 2013-10-29, 16:37 UTC

You need to run the batch file with administrator rights too to set the connections, because Windows sees them as separate users. You can use the Windows scheduler in control panel to do this automatically (it allows you to save the credentials).

ross104 · Post by *ross104 » 2013-10-29, 20:12 UTC

Ok. Got it working with batch file and system sheduler.
Thanks!!

What about second problem?
Why do I get all possible drive letters appear to be used by network disk?

sqa_wizard · Post by *sqa_wizard » 2013-10-29, 23:13 UTC

Why do I get all possible drive letters appear to be used by network disk?

Well, TC displays just what your operating system is reporting!
TC does not assign any drive by himself. This must be caused by a script or your previous manual attempts.

ross104 · Post by *ross104 » 2013-10-30, 07:16 UTC

See images above. My system reports are ok. After rebooting everything is fine, but after some time (15 mins - 2 hours) TC starts showing all possible drive letters assigned to a network share. Sametime windows shows everything wright (onle one letter used by network share).

Post by *petermad » 2013-10-30, 09:21 UTC

2ross104

after some time (15 mins - 2 hours) TC starts showing all possible drive letters assigned to a network share.

What happens if you restart TC after these 15 mins - 2 hours ?

ross104 · Post by *ross104 » 2013-10-30, 10:53 UTC

Nothing it still shows all letters.
Only system reboot does the trick to remove all letters

Post by *petermad » 2013-10-30, 14:11 UTC

2ross104
Well, to me that seems to indicate that the problem doesn't come from TC but from the system...

Post by *ghisler(Author) » 2013-10-30, 15:02 UTC

Yes, it sounds like something is creating these drive letters automatically. Maybe your script is loaded repeatedly instead of just loading during system start?

ross104 · Post by *ross104 » 2013-10-30, 21:52 UTC

After doing some observations found that all those connections start with launchug TuneUp Utilities...

Dont know where to dig more...

Post by *ghisler(Author) » 2013-10-31, 13:55 UTC

Sorry, no idea - a quick Google search didn't reveal any similar problems so far. Maybe ask the makers of TuneUp?