Re: [MLUG] SSH Remote port forwarding

[Mark Rupright <EMAIL:PROTECTED>]

Hi Russell,

>Surely if the client has connected to the server with SSH, the server
>already knows the client's IP.

You know I look rather dumb on that one... :-p

>We have a number of laptops set up with a dos batch script that calls
>plink (from the makers of putty).

Would you mind letting me look at the script you created?

mark at fivepetals.net


Thanks,

Mark Rupright

----- Original Message -----
From: "Russell Horn" <EMAIL:PROTECTED>
To: "MLUG Members" <EMAIL:PROTECTED>
Sent: Monday, February 12, 2007 2:31:18 PM (GMT-0600) America/Mexico_City
Subject: Re: [MLUG] SSH Remote port forwarding

On Fri, 2007-02-09 at 21:27 -0600, Mark Rupright wrote:
> Hi Stephen,
> 
> No, that's local port forwarding, I'm talking about remote port forwarding in which this case, the server would forward the print job to the remote client's printer. Since remote is the reverse of local forwarding than the server would need to know the  ip address of every client...correct?    

Surely if the client has connected to the server with SSH, the server
already knows the client's IP.

We have a number of laptops set up with a dos batch script that calls
plink (from the makers of putty). It instigates a connection to my
computer and opens up a connection from here back to their port 3389 so
I can then log onto their laptop via rdesktop for troubleshooting. 

All the users need to know is the password for the SSH key installed on
their laptop.

As for sending a print job, how much bandwidth will you have available?
Printjobs tend to be quite bandwidth intensive.

Russell


_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members


_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members