From owner-freebsd-questions@FreeBSD.ORG Sat Sep 20 20:39:16 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 482FD16A4BF for ; Sat, 20 Sep 2003 20:39:16 -0700 (PDT) Received: from mail3.bluewin.ch (mail3.bluewin.ch [195.186.1.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A39B144003 for ; Sat, 20 Sep 2003 20:39:14 -0700 (PDT) (envelope-from raphael@computer-rental.ch) Received: from computer-rental.ch (62.203.148.45) by mail3.bluewin.ch (Bluewin AG 7.0.020) id 3F570589001E51B9; Sun, 21 Sep 2003 03:39:13 +0000 Date: Sun, 21 Sep 2003 05:36:52 +0200 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: Brian Dessent From: =?ISO-8859-1?Q?Rapha=EBl_Marmier?= In-Reply-To: <3F6CE829.F089198B@dessent.net> Message-Id: Content-Transfer-Encoding: quoted-printable X-Mailer: Apple Mail (2.552) cc: freebsd-questions@freebsd.org 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: Sun, 21 Sep 2003 03:39:16 -0000 Unless you _must_ use samba, try using nfs with tcp connection through=20= your vpn. It is much faster and still reliable. mount -t nfs -o -T host:/the/path/ /mount/point will use tcp for transport, thus ensuring you don't suffer problems=20 even in the case of a disconnection of the vpn. Of course, the server=20 must supprt nfs over tcp (most bsd do that). We use this to connect to a cvs server and it works great. Rapha=EBl Le Dimanche, 21 sep 2003, =E0 01:52 Europe/Zurich, Brian Dessent a =E9crit= : > FreeBSD MAIL wrote: >> >> I guess the problem I am having is with PuTTY, I am forcing ssh 2 and=20= >> putting >> in the ports and addresses for the client and server as best I can, I=20= >> have >> been able to get VPN to work over pptp, which is cool but I would=20 >> 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=20= >> 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=20= > on > your local LAN, and have IT ssh into the remote and then forward 139=20= > 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 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to=20 > "freebsd-questions-unsubscribe@freebsd.org"