On Tue, 9 Jan 2001 23:18:33 -0600 (CST), William L. (Bill) Barth
<[EMAIL PROTECTED]> wrote:
>
> > "Ehud" == Ehud Karni <[EMAIL PROTECTED]> writes:
>
> Ehud> On Fri, 5 Jan 2001 20:36:09 -0600 (CST), William L. (Bill) Barth
> Ehud> <[EMAIL PROTECTED]> wrote:
> >>
> >> hom
> "Joseph" == Joseph A Knapka <[EMAIL PROTECTED]> writes:
OT: is that your actual email address or did somebody's mail
client/server muck things up. ('cuz I just looked in the passwd file
at work and you don't have an account ther
"William L. (Bill) Barth" wrote:
> Assuming I understand your suggestion, the problem with trying to do
> it that way is that I'm not allowed to connect directly to or open
> ports on the firewall itself. All connections to the ssh port (22) on
> the work firewall are forwarded (transparently to
> "Ehud" == Ehud Karni <[EMAIL PROTECTED]> writes:
Ehud> On Fri, 5 Jan 2001 20:36:09 -0600 (CST), William L. (Bill) Barth
Ehud> <[EMAIL PROTECTED]> wrote:
>>
>> home$ ssh -t work ssh work1 /pathtovncserver/vncserver :2 ; ssh -g -R
5902:work1:5902 home
>>
>> (The
> "BJ" == BJ Blanchard <[EMAIL PROTECTED]> writes:
BJ> In order to avoid the multiple nested ssh's, use a port
BJ> redirector (eg. redir). On my firewall, I redirect port 24 to
BJ> port 22 on my Solaris box, so from home I do: ssh -p 24 ...
I assume that you mean that on firewal
In order to avoid the multiple nested ssh's, use a port redirector (eg. redir).
On my firewall, I redirect port 24 to port 22 on my Solaris box, so from home I do:
ssh -p 24 ...
This should increase your performance, as well as simplify your command line.
BJ.
>>
> Date: Fri, 5 Jan 20
On Fri, 5 Jan 2001 20:36:09 -0600 (CST), William L. (Bill) Barth
<[EMAIL PROTECTED]> wrote:
>
> home$ ssh -t work ssh work1 /pathtovncserver/vncserver :2 ; ssh -g -R
>5902:work1:5902 home
>
> (The reverse connection is necessary since the firewalls don't allow
> any ports but the SSH ports
