Re: Samba over SSH

2003-09-20 Thread sebastian ssmoller
On Sat, 2003-09-20 at 08:25, FreeBSD MAIL wrote:
 I want to use PuTTY and ssh to port forward and map a samba share across the
 internet. From what I have read on the net it almost seems possable.

i guess u have to set up ssh port forwarding for the ports 137,138 and
139. 

which box shall provide the share (windows, fbsd, linux...) ? what kind
of OS is used on the client boxes ?

seb

 
 Does anyone know how this can be done? If it cant I guess I will have to use
 some VPN thing..
 
 Thanks in advance
 
 Richard Puga
 [EMAIL PROTECTED]
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Samba over SSH

2003-09-20 Thread FreeBSD MAIL
I am using FreeBSD 4.8 and Samba 2.2.8 as the server, I would like to use any 
windows operating system for the client side, but probably XP.
(I want to map the samba share to the windows box)

Thanks for your Help

Richard Puga
[EMAIL PROTECTED]


 On Sat, 2003-09-20 at 08:25, FreeBSD MAIL wrote:
  I want to use PuTTY and ssh to port forward and map a samba share across the
  internet. From what I have read on the net it almost seems possable.
 
 i guess u have to set up ssh port forwarding for the ports 137,138 and
 139. 
 
 which box shall provide the share (windows, fbsd, linux...) ? what kind
 of OS is used on the client boxes ?
 
 seb
 
  
  Does anyone know how this can be done? If it cant I guess I will have to use
  some VPN thing..
  
  Thanks in advance
  
  Richard Puga
  [EMAIL PROTECTED]
  
  ___
  [EMAIL PROTECTED] mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to [EMAIL PROTECTED]
  
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Samba over SSH

2003-09-20 Thread sebastian ssmoller
 I am using FreeBSD 4.8 and Samba 2.2.8 as the server, I would like to use any 
 windows operating system for the client side, but probably XP.
 (I want to map the samba share to the windows box)
 

so one idea could be to start three ssh tunnels from client side. which
command line u may wonna do something like this:

$ ssh -L 137:localhost:137 -N -f [EMAIL PROTECTED]
$ ssh -L 138:localhost:138 -N -f [EMAIL PROTECTED]
$ ssh -L 139:localhost:139 -N -f [EMAIL PROTECTED]

(putty should be able to do something similar. but i guess u will need
some scripting so that these ssh commands will be executed on startup of
the client systems or at least before the shares will be mounted of
course.)

now u should be able to connect ur clients to any share on server side
with \\localhost\share-name

i am not familiar with VPN. possibly its a better solution (?)

seb

 Thanks for your Help
 
 Richard Puga
 [EMAIL PROTECTED]
 
 
  On Sat, 2003-09-20 at 08:25, FreeBSD MAIL wrote:
   I want to use PuTTY and ssh to port forward and map a samba share across the
   internet. From what I have read on the net it almost seems possable.
  
  i guess u have to set up ssh port forwarding for the ports 137,138 and
  139. 
  
  which box shall provide the share (windows, fbsd, linux...) ? what kind
  of OS is used on the client boxes ?
  
  seb
  
   
   Does anyone know how this can be done? If it cant I guess I will have to use
   some VPN thing..
   
   Thanks in advance
   
   Richard Puga
   [EMAIL PROTECTED]
   
   ___
   [EMAIL PROTECTED] mailing list
   http://lists.freebsd.org/mailman/listinfo/freebsd-questions
   To unsubscribe, send any mail to [EMAIL PROTECTED]
   
  
  ___
  [EMAIL PROTECTED] mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to [EMAIL PROTECTED]
  
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Samba over SSH

2003-09-20 Thread FreeBSD MAIL
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.


Thanks again.

Richard Puga
[EMAIL PROTECTED]
PS Have you gotten this to work with cygwin or somthing before?

  I am using FreeBSD 4.8 and Samba 2.2.8 as the server, I would like to use any 
  windows operating system for the client side, but probably XP.
  (I want to map the samba share to the windows box)
  
 
 so one idea could be to start three ssh tunnels from client side. which
 command line u may wonna do something like this:
 
 $ ssh -L 137:localhost:137 -N -f [EMAIL PROTECTED]
 $ ssh -L 138:localhost:138 -N -f [EMAIL PROTECTED]
 $ ssh -L 139:localhost:139 -N -f [EMAIL PROTECTED]
 
 (putty should be able to do something similar. but i guess u will need
 some scripting so that these ssh commands will be executed on startup of
 the client systems or at least before the shares will be mounted of
 course.)
 
 now u should be able to connect ur clients to any share on server side
 with \\localhost\share-name
 
 i am not familiar with VPN. possibly its a better solution (?)
 
 seb
 
  Thanks for your Help
  
  Richard Puga
  [EMAIL PROTECTED]
  
  
   On Sat, 2003-09-20 at 08:25, FreeBSD MAIL wrote:
I want to use PuTTY and ssh to port forward and map a samba share across the
internet. From what I have read on the net it almost seems possable.
   
   i guess u have to set up ssh port forwarding for the ports 137,138 and
   139. 
   
   which box shall provide the share (windows, fbsd, linux...) ? what kind
   of OS is used on the client boxes ?
   
   seb
   

Does anyone know how this can be done? If it cant I guess I will have to use
some VPN thing..

Thanks in advance

Richard Puga
[EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

   
   ___
   [EMAIL PROTECTED] mailing list
   http://lists.freebsd.org/mailman/listinfo/freebsd-questions
   To unsubscribe, send any mail to [EMAIL PROTECTED]
   
  
  ___
  [EMAIL PROTECTED] mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to [EMAIL PROTECTED]
  
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Samba over SSH

2003-09-20 Thread Brian Dessent
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 very slw.  If your link is faster you'd
probably have better luck.

Brian
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Samba over SSH

2003-09-20 Thread Raphaël Marmier
Unless you _must_ use samba, try using nfs with tcp connection through 
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 
even in the case of a disconnection of the vpn. Of course, the server 
must supprt nfs over tcp (most bsd do that).

We use this to connect to a cvs server and it works great.

Raphaël

Le Dimanche, 21 sep 2003, à 01:52 Europe/Zurich, Brian Dessent a écrit :

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 very slw.  If your link is faster you'd
probably have better luck.
Brian
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]