X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=cKgnGs9EzpHGhscs
	j2wOaNOZ1eje/QrpRqapBQzlmqHGvDCCty15HH8ZyMQOXzJ2j6oUwO/HTj94JRib
	TYkNocEnn3ozxDamnkfU8A1Eld5GiJ6rSROH4m6z3i/xBMa7kfsDKPWU9g9rhVRq
	lB47yTX+MWXKXMnBco3XXQPS7LI=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=W4WWaXA/8hnPZbTH0Z89UJ
	4b4Fk=; b=dHGI7uFUB2D47aspZ1JH+0PVW1nGfJ6Tzdstqh632c7qo36VJXEc7W
	qeaDwF5lNOKAUIh+r3zFEIshIb+9DPAaa4vwfQvN7wJVRTrzYZErwS+cwPuI8et0
	fChX6YhezCRtlWncNG8a8kiygeF1iiBKv7PhhkAptSsA/9NZTzvN0=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=4.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	smtpback.ht-systems.ru
Date:	Sun, 26 Jan 2014 10:15:52 +0400
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	Andrey Repin <cygwin AT cygwin DOT com>
Message-ID:	<1867136502.20140126101552@mtu-net.ru>
To:	Damian Harty <Damian DOT Harty AT polaris DOT com>, cygwin AT cygwin DOT com
Subject:	Re: Windows 7 64 Bit - Mounting Network Drives
In-Reply-To:	<8f0b000fde5f4f64a63309e93cc94752@BL2PR02MB449.namprd02.prod.outlook.com>
References:	<5d086b5de9f248deae22fa7a6f8d7cc2 AT BL2PR02MB449 DOT namprd02 DOT prod DOT outlook DOT com> <461321165 DOT 20140124151041 AT mtu-net DOT ru> <40eab36225614694a42fa9215b210fdb AT BL2PR02MB449 DOT namprd02 DOT prod DOT outlook DOT com> <282663683 DOT 20140124163010 AT mtu-net DOT ru> <8f0b000fde5f4f64a63309e93cc94752 AT BL2PR02MB449 DOT namprd02 DOT prod DOT outlook DOT com>
MIME-Version:	1.0
X-IsSubscribed:	yes

Greetings, Damian Harty!

>> Can you please do the following commands in order (native windows console
>> preferred, but not necessary): 
>> net use

>     % net use
>     New connections will be remembered.


>     Status       Local     Remote                    Network

>     -------------------------------------------------------------------------------
>     Unavailable  H:        \\brt1itssrv003\homes\daharty
>                                                    Microsoft Windows Network
>     Unavailable  Z:        \\wym1itsnas001\cae3\adams_db
>                                                     Microsoft Windows Network
>     The command completed successfully.

That's <somewhat> normal in certain network setups, but only until you first
access the network drive in Explorer.

>> subst

>     % subst

>     %

>> cd /cygdrive/h

>     % cd /cygdrive/h
>     /cygdrive/h: No such file or directory.

>> explorer H:\\

>     (opens the drive correctly)

The "thing" should now work as normal, but...

>> Close the window in either case. net use; subst; cd /cygdrive/h (does it work now?)

>    2nd lap exactly reproduces the results of the first lap.

That sad to know...
I'm, unfortunately, out of ideas.
Perhaps,
cygcheck -srv
would shed some light.

>> Also, a crucial moment - do you use a terminal session, or your machine is
>> physically present at the place, and you are logging to its desktop as
>> normal?

> I am sat at the laptop keyboard running the laptop in question. I log into
> its Windows desktop in the normal fashion. 

> So, to recap:

> - Windows can see the networked drives just fine.
> - Cygwin knows about them but declares them unavailable.

> Since I don't know what I don't know, I am unable to fashion a precision
> question to proceed further, except to ask "what stands between me and the
> ability to make the network drives available from within cygwin?"


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 26.01.2014, <10:11>

Sorry for my terrible english...


--
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

- Raw text -