Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Tue, 25 Jan 2000 16:28:56 +0300
From: Egor Duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.029) S/N A0F2A05A
Reply-To: Egor Duda <deo AT logos-m DOT ru>
Organization: DEO
Message-ID: <10686.000125@logos-m.ru>
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Network drives in telnet session?
References: <Pine DOT LNX DOT 4 DOT 10 DOT 10001250729510 DOT 6635-100000 AT pii DOT fast DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

Jan 25 2000 Steven N. Hirsch shirsch AT adelphia DOT net wrote:

SNH> After a protracted battle, I finally have Cygwin inetd working properly
SNH> and can successfully telnet into a cygwin session.  Unfortunately, I
SNH> cannot access any mounted shares from such a login!  The cygwin 'mount'
SNH> and NT 'net' commands show the drives as being mounted, but any access is
SNH> met with "permission denied".

SNH> My session seems to be running under the correct NT user and group ids,
SNH> and I'm even able to umount and remount the shares!  I just can't do
SNH> anything with them.  The only obvious problem reported by 'net use' is
SNH> that the shares appear as "unavailable" in the telnet session.

SNH> I have tried having the inetd service run as 'System' and 'Administrator'
SNH> with no change in the misbehavior.

SNH> If I start a shell directly on the NT box, everything is fine.

SNH> Any hints?

try to use UNC names. i.e. you can create system mounts with command,
similar to

mount -b -s -f \\server\share /net/server/share

(note: if you're issuing your command from bash or sh, you should
duplicate every '\')

if you want to access network from your account only, you can create
user mounts instead of system ones.

i'm working for a long time in such environment with no problems.

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com