Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 10 May 2005 15:03:17 -0400 From: Chip Olson To: cygwin AT cygwin DOT com Subject: Permissions problem mounting NFS shares from Cygwin sshd Message-ID: <20050510190317.GB27244@thsi.org> Mail-Followup-To: cygwin AT cygwin DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-IsSubscribed: yes For reasons too complicated to explain, I need to configure a Windows 2000 machine to mount NFS shares from a Cygwin sshd session. The NFS mounting part of this is taken care of by Windows Services for Unix, and I have User Name Mapping set up so that my Windows user account mounts as its Unix counterpart. If I run the SFU mount command from a bash shell on the Windows desktop, all is peachy, and it mounts with UID and GID both 0. If I mount from an SSH login, however, it mounts with UID and GID both -2, aka nobody, and I don't have write access on the NFS share. I'm pretty sure that what I need to do is configure the Cygwin sshd service to log in as Administrator, rather than as "local user". However, when I configure it that way and restart the sshd service, it fails to start. In the error log, I get "...starting service `sshd' failed: execv: 128, Transport endpoint is not connected". On one or two occasions, I got "permission denied" errors from either starting sshd or writing to its logfile. I read in the archives that logging in with public-key authentication can cause problems like this, and indeed, if I log in via ssh with -o PubKeyAuthentication=no, the mount works fine (and reports my user's UID and GID, not 0 for both as when I mount from the desktop). I have another machine here that mounts just fine from a public-key ssh session. Unfortunately, the person who configured it is no longer with the company. :-( The really irritating aspect of this is that, when sshd fails to start, it is now stuck in state "starting", and the usual stop, start etc. buttons are greyed out. It appears the only way to get it out of that state is Windows Troubleshooting Procedure Number 1, aka reboot. (Number 2 is, of course, reinstall the operating system). Many thanks for any hints. -- -Chip Olson | ceo AT thsi DOT org | "And the sands will roll out a carpet of gold / For your weary toes to be a-touchin' / And the ship's wise men will remind you once again / The whole wide world is watchin'" -Bob Dylan, "When The Ship Comes In" -- 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/