Re: SSH & VNC discovery

Actually, I tried it all intranet first to take the router/firewall out of
the picture. Once that was working then I went Internet and setup the
router. Initially I was trying to forwar port 5900 but the error message
mentioned port 22 so that was a quick fix.

My first success was with Cygwin SSH becuase it assumed port 22. SSH32 &
Putty have a spot for port 22 on the GUI but did not work with the command
line.

I'll be posting all the settins for SSH32 in a bit.

Thanks again.
Carl

----- Original Message -----
From: "Mark Moriarty" <markmoriarty@earthlink.net>
To: <ssh-l@erdelynet.com>
Sent: Saturday, December 28, 2002 1:37 PM
Subject: RE: SSH & VNC discovery

> You have to love those standards :) -- I quickly learned I had to open
port
> 22 on my firewall, but it sounded like your ssh had been up and running,
> which meant 22 all set, just stuck on how to get VNC riding on it.
>
> (Now if only I could get work to open port 22... Always strikes me as
silly
> that I'm allowed to use FTP and HTTP (initiated by me from behind the work
> FW), but God forbid I be allowed to use a secure protocol for
> obtaining/sending things to the outside world :)

--
List Information: http://tech.erdelynet.com/mailman/listinfo/ssh-l/
List Archives:    http://erdelynet.com/archive/ssh-l/
To Unsubscribe: Go to http://tech.erdelynet.com/mailman/listinfo/ssh-l/ and enter your email address at the bottom to "Edit Options". If you don't know your password, have it emailed to you. Then unsubscribe.