John Hebert <[EMAIL PROTECTED]> writes: cool. This also works fine with terminal services client connections as well (tcp port 3389). And yes, linux has a client for that as well: http://rdesktop.sf.net
ssh makes a quick and dirty ad-hoc vpn tool as well. ssh -f -N -C -L25:myhomemailserver:25 -L143:myhomemailserver:143\ [EMAIL PROTECTED] set up laptop mail client to use localhost for smtp and imap. make sure smtp auth is configured on server and client. For a "full-on" vpn solution that is REALLY easy, use vtun over ssh, vtun.sf.net . Linux Server Hacks from O'Reilly showed me this one. > Well, crap, that worked! > > I thought for sure I had tried that iteration. > > In any case, thanks Scott! > > In summary for those who are interested: > > This is what you have to do to connect two M$ Windows PCs when they are both > behind firewalls and separated by the big, bad Internet: > > Target PC: > 1. Download and install TightVNC (http://www.tightvnc.com) on the target PC. > Start VNC server. > 2. Download plink.exe > (http://the.earth.li/~sgtatham/putty/latest/x86/plink.exe) from the Putty > download page > (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html). > 3. Run: plink.exe [-l username -pw userpasswd] -R 5900:192.168.1.23:5900 > [EMAIL PROTECTED] (where 192.168.1.23 is the IP address of the > target PC) > Note that you can supply the "-l username -pw userpasswd" part to bypass the > prompts. If you do, you don't need "username@". > > Home PC: > 1. Download and install TightVNC (http://www.tightvnc.com) on the target PC. > 2. Download plink.exe > (http://the.earth.li/~sgtatham/putty/latest/x86/plink.exe) from the Putty > download page > (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html). > 3. Run: plink.exe [-l username -pw userpasswd] -L 5900:192.168.1.23:5900 > [EMAIL PROTECTED] > 4. Start VNC viewer, connect to localhost. > > You should get a password prompt from the VNC server on the target PC. > > For Linux users, use "ssh" instead of "plink.exe". > > John Hebert > > -----Original Message----- > From: Scott Harney > To: [email protected] > Sent: 8/21/03 8:07 AM > Subject: Re: [brlug-general] ssh port forwarding question > > John Hebert <[EMAIL PROTECTED]> writes: > >> However, what I want to do is run a vnc client on a machine behind >> myhomefirewall and connect to the target PC. How would I do this? The >> machine myhomefirewall is an OpenBSD box, so I'm suspecting I need to > change >> pf.conf, though one the other hand, it seems I should be able to > connect via >> ssh to myhomefirewall and some how get to port 5900 on the target PC. > ??? > > would this not do what you want? > > $ ssh -L 5900:targetmachinebehindfirewall:5900 [EMAIL PROTECTED] > $ xvncviewer localhost > > It avoids the need of having a machine in the middle running a vnc > client. > >> I tried a number of different methods on the third machine but now my > brain >> is a little fuzzy. Can anybody hit me with a cluebat? > > -- > Scott Harney<[EMAIL PROTECTED]> > "...and one script to rule them all." > gpg key fingerprint=7125 0BD3 8EC4 08D7 321D CEE9 F024 7DA6 0BC7 94E5 > > _______________________________________________ > General mailing list > [email protected] > http://brlug.net/mailman/listinfo/general_brlug.net > > _______________________________________________ > General mailing list > [email protected] > http://brlug.net/mailman/listinfo/general_brlug.net -- Scott Harney<[EMAIL PROTECTED]> "...and one script to rule them all." gpg key fingerprint=7125 0BD3 8EC4 08D7 321D CEE9 F024 7DA6 0BC7 94E5
