Well you don't want to use the whole Windows environment over the tunnel - it would be painfully slow. But to get filesystem access (Network Neighbourhood) so that you can remotely access your DATA files you need to point Network Neighbourhood at the localhost for the tunnel.
Get Tunellier to forward 137/138/139 from locahost then go Start -> Find -> Computer and type in "\\127.0.0.1\" and Find Now. This should get you to the remote end of the tunnel. It is important to remember that the tunnel emminates from the machine where the ssh server resides but it does not need to be pointed at it. It can be Samba on the that server or something else on that LAN. If you don't want to use \\127.0.0.1\ then you can try adding MS Loopback as an additional adapter to your WinXX machine and give it a non-127.0.0.1 address probably in one of the non-routable blocks ie;172.16.1.1. Then you don't blow away localhost functionality of whatever you tunnel. dbc. On Thu, 18 Oct 2001, Mark Plowman wrote: > David, > > > From: "David B. Cook" <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]> > > Date: Thu, 11 Oct 2001 09:47:28 -0400 (EDT) > > > > Port forwarding through ssh is a *fabulous* solution. > > I am new to this (forwarding through ssh), but *indeed* it does look > neat. > > > > Look at Tunnelier (http://www.bitvise.com/tunnelier.html) for WinX > > environments. > > Thanks! I am also investigating various other possibilities, PuTTY > comes into the picture for me because it supports Public Key > authentification whilst I don't think Tunnelier does (or am I wrong?). > But on the other hand PuTTY doesn't appear to support configuration > files and command line parameters (drat!). > > > > I forward 137/138/139 to my house and I can use my Samba shares from > > anywhere through an encrypted tunnel. > > OK, here comes the question: > > Yesterday I was playing with this, forwarding 137/138/139 through an > encryted tunnel (still *on* the company network - I haven't yet > punctured my LEAF Firewall!) from a Win NT box to a Linux box. > > Experiments with tunneling HTTP were easy, point browser at localhost > or configure the browser with localhost as proxy and Bingo! > > However, how do I get the MS client software (this is for rodent bound > road-warriors) to look into the tunnel? Or did you do it with SAMBA > related tools on Linux? > > > > MS functionality without their security problems! (I know, technically I > > have extended the risk element on associated server procs from my server > > to the end-of-line Windows device ... but don't burst my bubble!) > > Yeah, it's nice, but the worries persist... > > > Greetings > > Mark > -- David B. Cook, <[EMAIL PROTECTED]> Linux -- up 13 days because it can. 3:40pm up 13 days, 19:56, 1 user, load average: 0.00, 0.00, 0.00 _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
