This is the mail archive of the
mailing list for the Cygwin project.
Re: Error accessing mapped drive >2TB?
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Brian Inglis <Brian dot Inglis at SystematicSw dot ab dot ca>, cygwin at cygwin dot com
- Date: Tue, 22 Sep 2015 11:28:54 +0300
- Subject: Re: Error accessing mapped drive >2TB?
- Authentication-results: sourceware.org; auth=none
- References: <CA+2x6-L_pqdN6PHE0c15hcmrmB66Z75Hz95cH+dbcn4yXuVZNg at mail dot gmail dot com> <712A87EA-64C7-4033-BE7F-39C8C8D527EB at etr-usa dot com> <110723294 dot 20150915064630 at yandex dot ru> <CA+2x6-LtkKk15AOavG5pUD+YwcKKa=TKU1nnHwEy45LKwLkFJg at mail dot gmail dot com> <0C37A612-5E78-48A8-9503-F3A34129BC7B at etr-usa dot com> <CA+2x6-L+dr92-O1b2bnqnaCxOzZ9GCLv1ekXEPcALkuYvFp_yQ at mail dot gmail dot com> <B35CA86C-3AFD-424A-AFE7-7A2B4FE0B421 at etr-usa dot com> <loom dot 20150921T061240-314 at post dot gmane dot org> <1536508568 dot 20150921085631 at yandex dot ru> <loom dot 20150921T232032-792 at post dot gmane dot org>
- Reply-to: cygwin at cygwin dot com
Greetings, Brian Inglis!
>> > Windows Explorer drive mappings are not visible from cmd or mintty/bash
>> > windows, but "net use x: \\live.sysinternals.com\tools" mappings are visible
>> > from separate cmd and mintty/bash windows as drive X: or /cygdrive/x, but
>> > x:\ is not accessible from Windows Explorer.
>> Are you sure you're looking from the same user session?
> Same user session, different (elevated) cmd and mintty/bash console sessions.
Elevated process uses different user session.
Network mapped drive letters are session-bound.
>> If you start mintty/cmd elevated, you won't see drives mapped in Explorer
> Kind of figures on Windows - I would expect elevated sessions to be able to
> see mappings on non-elevated sessions.
That's not how it works. And is a part of reason why using mapped drives is
discouraged. For 15 years now, at least.
>> For me, everything works as expected. Drives mapped in batch file on system
>> start visible in Explorer without an issue.
> Found that when I started using W7 console sessions, net utilities, both MS
> and Cygwin nslookup, ping, tracert, etc. could not see the network unless
> they were run in elevated sessions, so set up all console sessions to start
> elevated. Was that something that happened on early releases and was fixed
> later, or some incorrect assumption or setting on my part years ago?
If your logon script attempts to mount (net use) drive letters, but Explorer
don't see them, double check that it did indeed mounted them. I.e. insert
"pause" before the end of the script and check for any errors after its
Another possible solution (Cygwin-specific) is to use fstab bind mount for
Third one, and that I've gone with myself is to use Vista+ NTFS functionality
to symlink network paths to local FS. Just remember to use FQDN host names or
IPs when doing so, else you could intermittently lose connectivity when using
VPN connections to other networks with different domain search suffixes.
With best regards,
Tuesday, September 22, 2015 11:20:20
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple