Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <8667c75d050623114741c247cf@mail.gmail.com>
Date: Thu, 23 Jun 2005 11:47:14 -0700
From: Monkey Pet <monkeypet AT gmail DOT com>
Reply-To: Monkey Pet <monkeypet AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: mounting network shares to make it persistent.
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j5NIlNU1002682

I want to be able to access a resource (aka map) and make it available
the next time a user logs into ssh.  I am using cywin with the open
ssh server.

I would like know answers to the following questions:
     1. Can mount be given a username/password and domain?
     2.  Is the net use command the correct command to use in the
cgywin environment.
     3.  Any attempts to mount before starting ssh will not be
acceptable since the network shares will change from time to time. 
Everything needs to be done over ssh for automation.

Here is an example:

ssh administrator AT ip
net use z: \\\\share\\fs2 password /USER:qadomain\\Administrator /PERSISTENT:No
(Share is available and accessible)
(logout)

ssh administrator AT ip
(share is gone)

Now do the following:
net use z: \\\\share\\fs2 password /USER:qadomain\\Administrator /PERSISTENT:No
mount \\\share\\fs2 /test
(Share is available and accessible)
(logout)

ssh again
(share exists, but can't access directory until I do the "net use")

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