Email address obfuscation in effect -- please
click here to turn it off.
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
- To: MLUG Members <EMAIL:PROTECTED>
- Subject: Re: [MLUG] SSH Remote port forwarding
- From: Stephen Montgomery-Smith <EMAIL:PROTECTED>
- Date: Tue, 06 Feb 2007 18:50:54 -0600
- Delivery-date: Tue, 06 Feb 2007 18:52:05 -0600
- Envelope-to: EMAIL:PROTECTED
- In-reply-to: <EMAIL:PROTECTED>
- References: <EMAIL:PROTECTED>
- Reply-to: MLUG Members <EMAIL:PROTECTED>
- Sender: EMAIL:PROTECTED
- User-agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070131
Mark Rupright wrote:
Hi All,
The development team at my workplace are working on centralizing all of our field office cobol programs to the home office. They have decided on using SSH for the connection bit and would like to utilize port forwarding for sending print to the local printers in the field. My thought is that in order for the server to send print over ssh to the remote client, it would require remote port forwarding as apposed to local port forwarding. My second thought is would it work and if not is there an alternative direction someone could point me to?
Let me know if clarification is needed. :-)
Thanks,
Mark Rupright
_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members
Is this what you mean? On local client run (this example is for pop3):
ssh -L 110:remote.host.org:110 remote.host.org
Then any attempts to access port 110 on the local client will become
attempts to access port 110 on the remote host. And it all goes through
ssh, so no-one can listen in.
_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members