DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=C769OUuxX5lja0ly
	TxQOu8dpqut51Lj169IFnwjO2ubOUXDn28ZzDsNW43LG64gEy3WymMhUUIVBFvGI
	d2pHMHQQ/6jnKN1FqOrp7NMUqUs+GGd+HrVIAaeWd9k8olHV+TKWPPJ0fvnRjsSX
	TqEobv/fxsJ8w31zysiGdqSYJcc=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-id: <5151C750.8020707@cygwin.com>
Date: Tue, 26 Mar 2013 12:05:36 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin, Windows Shared Drive Access
References: <1364307966 DOT 75066 DOT YahooMailRC AT web181701 DOT mail DOT ne1 DOT yahoo DOT com>
In-reply-to: <1364307966.75066.YahooMailRC@web181701.mail.ne1.yahoo.com>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 3/26/2013 10:26 AM, mcforum wrote:
> A new Windows 7 32 system with a fresh install of CYGWIN can't see any mapped
> network or shared drives on my other systems.  On the older XP system IT tells
> me to replace and on another older Windows 7 32 system, CYGWIN could access all
> drives.  What am I missing in the install that enables access to those drives?

As I tried to convey (unsuccessfully) with your original inquiry on the
Cygwin-X list, there isn't a specific Cygwin package that you just install
to make this work.  But you could, of course, look at the list of packages
you have installed on both your new machine and old to make sure that you
have achieved package parity.  If you'd like to do this comparison, you can
use 'cygcheck -cd' to get the list from the new and old systems.  I don't
think doing this will help with the problem at hand but it may be useful
for other reasons.

<snip>

> The shares don't seem to be shown anywhere on the system tree but I can soft
> link them to a directory name and then access them.
> On a CYGWIN restart "net use" shows the network names as being disconnected and
> reissuing the command doesn't change the status.  However, re-establishing the
> soft link allows full usability.
>
> Gremlins?

Indeed, those are always possible.  Typically here they take the form of
BLODA (http://cygwin.com/acronyms/#BLODA).  But I don't think that's the
problem in this case.  Given the steps you outlined above (and I snipped
for brevity) I played around with this some on my systems.  I found I could
get myself into what looked like your situation if I was dealing with a
share with a password.  Once I created a persistent mapping with the
password, everything worked as expected in my Windows session (and any
Cygwin terminal, Cygwin cmd.exe, or Windows cmd.exe windows).  I didn't
try rebooting.  The steps above do not show you supplying passwords but
once I did that for a particular share, I didn't need to use it again to
recreate the share so I'm wondering if your shares do require passwords
too.  If so, then what I'm seeing may match yours and you may find that
deleting the existing shares and recreating them persistently with the
passwords will help.


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple