Multi Commander > Support and Feedback
Network drives are not showed in MC
Turpal:
--- Quote ---and from the admin command prompt you can do "dir Z:\" if it now is Z..
--- End quote ---
Yes, when I do dir I can see the contents.
However, as you can notice they are RDP auto-shares, and don't have letter assigned. Maybe that is the problem?
This is definitely a bug, 'cause all shares must be showed, disregard of presence/absence of letter.
Mathias (Author):
No that are not mapped drive.. Mapped drives are network path that are connected to drive letters. like Z: X: and so on.
RDP connected devices are something completely different
Drives connected via RDP are located under the virual server path \\TSCLIENT you find them under the network (Net:) or by going to \\TSCLIENT
Turpal:
--- Quote ---No that are not mapped drive.. Mapped drives are network path that are connected to drive letters. like Z: X: and so on.
RDP connected devices are something completely different
Drives connected via RDP are located under the virual server path \\TSCLIENT you find them under the network (Net:) or by going to \\TSCLIENT
--- End quote ---
Okay, I don't wanna to argue about the terms: mapped, network or redirected drives, doesn't matter. Let's treat this as a feature request. Could you add the support for Terminal Services drives?
If I map this drive manually
--- Code: ---net use Z: \\tsclient\C
--- End code ---
it works wonderfully and become visible in MC. Okay, I can schedule this command at start but maybe it can be done in a more native way?
Mathias (Author):
TS devices are supported, they are shown under NET: since windows expose then as virtual network shares
Turpal:
--- Quote from: Mathias (Author) on April 13, 2017, 20:19:38 ---TS devices are supported, they are shown under NET: since windows expose then as virtual network shares
--- End quote ---
Ok, they are. So the question is closed.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version