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: <434D8E7D.DB3D6563@dessent.net>
Date: Wed, 12 Oct 2005 15:30:21 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: ssh tunnel and permission denied
References: <5d3f5dd52c71ff2e4e5e7b2734b19c0e AT alternative DOT ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Leonard Bouchet wrote:

> # Step 1: open the ssh tunnel
> $ ssh -fNL 139:myserver:139 user AT myserver

I'm surprised that this works.  Normally if you try this on a windows
machine the port forwarding setup will fail because the local SMB
service on that machine is already listening on 139, and so it's
impossible for ssh to bind to that port.  How are you getting around
this?  Have you tried adding verbosity (-vvv) to the ssh command to see
if there are errors setting up the port forwarding?

Brian

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