From owner-freebsd-questions@FreeBSD.ORG Sat Sep 20 16:52:18 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37AB716A4BF for ; Sat, 20 Sep 2003 16:52:18 -0700 (PDT) Received: from booch.minidns.net (c-67-160-219-187.client.comcast.net [67.160.219.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1894843FE0 for ; Sat, 20 Sep 2003 16:52:17 -0700 (PDT) (envelope-from brian@dessent.net) Received: from [127.0.0.1] (helo=dessent.net) by booch.minidns.net with esmtp (Exim 4.22) id HLJEB0-0002CG-CV for freebsd-questions@freebsd.org; Sat, 20 Sep 2003 16:52:12 -0700 Message-ID: <3F6CE829.F089198B@dessent.net> Date: Sat, 20 Sep 2003 16:52:09 -0700 From: Brian Dessent Organization: My own little world... X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,en-US MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <200309201951.h8KJpcLx008465@mauibuilt.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Samba over SSH X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Sep 2003 23:52:18 -0000 FreeBSD MAIL wrote: > > I guess the problem I am having is with PuTTY, I am forcing ssh 2 and putting > in the ports and addresses for the client and server as best I can, I have > been able to get VPN to work over pptp, which is cool but I would prefer using > ssh. > > If you have a copy of putty laying around would you mind trying it? > > Or even teraterm-ssh, I am reluctant to use cygwin and such because of the > user interface. The problem you are going to have is that windows binds its NetBIOS stuff to local port 139 et. al. so there's no way to forward them with ssh. The only way to do this is to use a second, non-windows machine on your local LAN, and have IT ssh into the remote and then forward 139 et. al. After doing that, it will appear to have local shares to the windows box. Alternatively, you could try disabling "File and Printer Sharing" on the windows end and try to get whatever is listening on 139 to stop so that ssh can forward that port... I don't know if that's possible or not. The VPN method with PPTP (and mpd on the remote FreeBSD end) is what I ended up doing. I finally got it all working finally, and was quite disappointed with the speed. Samba over a broadband link to a server very far away was verrrrry sloooow. If your link is faster you'd probably have better luck. Brian