From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12696 invoked by alias); 12 Oct 2005 22:30:25 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 12630 invoked by uid 22791); 12 Oct 2005 22:30:23 -0000 Received: from dessent.net (HELO dessent.net) (69.60.119.225) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 12 Oct 2005 22:30:23 +0000 Received: from localhost ([127.0.0.1] helo=dessent.net) by dessent.net with esmtp (Exim 4.52) id 1EPp77-0006sI-Dw for cygwin@cygwin.com; Wed, 12 Oct 2005 22:30:21 +0000 Message-ID: <434D8E7D.DB3D6563@dessent.net> Date: Wed, 12 Oct 2005 22:30:00 -0000 From: Brian Dessent MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: ssh tunnel and permission denied References: <5d3f5dd52c71ff2e4e5e7b2734b19c0e@alternative.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com X-SW-Source: 2005-10/txt/msg00338.txt.bz2 Leonard Bouchet wrote: > # Step 1: open the ssh tunnel > $ ssh -fNL 139:myserver:139 user@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/