Browsing is going to fail. Just do the port forwarding and then use the NET USE command to map to the resource. Also, why are you pointing to 192.168.1.17 for ports 137 and 139 but to 192.168.1.20 for port 139?
Anyway, let's assume that the UNC that you want is \\192.168.1.4\data. Do this: $ ssh -L 137:192.168.1.4:137 -L 139:192.168.1.4:139 ssh-server $ smbclient //localhost/data ----- Original Message ----- From: "John Hebert" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, November 13, 2003 10:37 PM Subject: [brlug-general] Can Samba work via ssh tunnels? > Howdy, > > At the Samba presentation, I asked if it was possible to use Samba via > ssh port forwarding and was told that yes, it is possible. > > I'm trying to do that right now, but I'm not making much headway. > > Has anybody done this before? Do you know of any written docs showing > how to do this? > > What I'm doing right now is: > > ssh -L 137:192.168.1.17:137 -L 138:192.168.1.17:138 -L > 139:192.168.1.20:139 -l john my.server.com > > but when I try to use Windows Exploder to browse my network, it times > out after a while and gives me a network access error. > > How should I be configuring this? Should I setup a hosts file entry on > my Windows client box? > > Thanks, > John Hebert > > > _______________________________________________ > General mailing list > [email protected] > http://brlug.net/mailman/listinfo/general_brlug.net > >
