[NTLUG:Discuss] Need help getting sambs to work over stunnel(please help!)

[Neil Aggarwal]

MadHat:

The problem with that approach (which I did get to work) is
that the ssl option for samba is slated to be removed.

The samba developers recommend using stunnel instead, but
I can't get it working.

Thanks,
	Neil.

--
Neil Aggarwal
JAMM Consulting, Inc.    (972) 612-6056, http://www.JAMMConsulting.com
Custom Internet Development    Websites, Ecommerce, Java, databases


> -----Original Message-----
> From: discuss-admin at ntlug.org [mailto:discuss-admin at ntlug.org]On Behalf
> Of MadHat
> Sent: Wednesday, May 08, 2002 12:37 PM
> To: NTLUG-Discuss
> Subject: Re: [NTLUG:Discuss] Need help getting sambs to work over
> stunnel(please help!)
>
>
> Why use samba at all?
>
> Have you looked at this?
> http://www.stunnel.org/examples/smb_grant.html
>
>
> On Wed, 2002-05-08 at 10:41, Neil Aggarwal wrote:
> > Hello:
> >
> > I have samba set-up and working completely fine
> > on my Linux server.  I can get to it using network
> > neighborhood just fine.
> >
> > Now, I want to set-up and stunneled connection to the server
> > so that the data is protected.
> >
> > I know about the ssl option for samba, but that is slated to
> > be removed so I want to get this working with stunnel.
> >
> > So, on the server, I issued this command:
> > /usr/sbin/stunnel -D 7 -d 2139 -r 139
> >
> > On my client (A windows 2000 machine), here is what I did:
> > 1. Created a directory c:\bin
> > 2. Downloaded the file
> > http://www.kuix.de/ssl/stunnel-3.11-kai-gui-winexe.zip
> > 	and extracted it.
> > 3. I then went to a command line, changed to the c:\bin directory
> >    and typed this command:
> >  	stunnel.exe -D 7 -c -d 127.0.0.2:139 -n smb -r 204.130.252.205:2139
> >
> > I then went to windows explorer and tried to add a network
> > place with the location \\127.0.0.2\Documents but when it
> > tries to connect, I get a pop-up that says the network path
> > was not found.
> >
> > On the client here is what I see:
> > C:\bin>stunnel.exe -D 7 -c -d 127.0.0.2:139 -n smb -r
> 204.130.252.205:2139
> > LOG5[1308:1256]: Using '204.130.252.205.2139' as tcpwrapper service name
> > LOG7[1308:1256]: RAND_status claims sufficient entropy for the PRNG
> > LOG7[1308:1256]: Seeded PRNG with RAND_screen
> > LOG6[1308:1256]: PRNG seeded successfully
> > LOG5[1308:1256]: stunnel 3.11 on x86-pc-unknown WIN32
> > LOG7[1308:1256]: 204.130.252.205.2139 bound to 127.0.0.2:139
> > LOG7[1308:1012]: 204.130.252.205.2139 started
> > LOG5[1308:1012]: 204.130.252.205.2139 connected from 192.168.1.3:1753
> > LOG7[1308:1012]: 204.130.252.205.2139 connecting 204.130.252.205:2139
> > LOG7[1308:1012]: Remote host connected
> > LOG7[1308:1012]: Negotiations for smb(client side) started
> >
> > On the server, I see this message when I try to connect:
> > May  6 13:05:57 www stunnel[1362]: 139 connected from 65.185.3.177:1754
> >
> > Any ideas?
> >
> > Thanks,
> > 	Neil.
> >
> > --
> > Neil Aggarwal
> > JAMM Consulting, Inc.    (972) 612-6056, http://www.JAMMConsulting.com
> > Custom Internet Development    Websites, Ecommerce, Java, databases
> >
> >
> > _______________________________________________
> > http://www.ntlug.org/mailman/listinfo/discuss
> >
> --
> MadHat at Unspecific.com
> gpg --keyserver wwwkeys.us.pgp.net --recv-keys 9DDC3E98
> Key fingerprint = E786 7B30 7534 DCC2 94D5  91DE E922 0B21 9DDC 3E98
>
>
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss