"Jan Hugo Prins" <(E-Mail Removed)> wrote in message
news

(E-Mail Removed)...
> On Thu, 16 Feb 2006 06:06:57 -0800, johndoe wrote:
>
>> Hi Everyone,
>>
>> Here is my setup, maybe someone cal help?
>>
>> I have a home network with 6 computers and a linksys router. On my Linux
>> box, I have reconfigured SSH to accept the connection on port 443, and I
>> have forwarded the port in the router. Also, I installed VNC Server on
>> my
>> Windows XP box.
>>
>>>From work, I can use SSH Secure Shell Client and connect to my Linux
>> box via port 443. So, that works. I cannot however, get to my Windows
>> box.
>>
>> Perhaps I have the tunneling set up improperly? Do I need to be running
>> some type of SSH on my Windows box? Do I need to forward ports 590x in
>> the router?
>>
>> Maybe someone can help by giving me some of their settings and I'd be
>> able
>> to duplicate those on my setup. I guess I need to know what changes, if
>> any, to make on the server side and any changes on the client
>> side.........
>>
>> Thanks.
>
> You should be able to do the following. When you make a SSH connection to
> your home box, just make a tunnel and tunnel port 5900 through that SSH
> tunnel. You do that the following way, when you use ssh on the box at
> work, you can do:
>
> ssh -L5900:<IP windows box>:5900 -p 443 <external ip at home>
>
> Now you can start vncviewer at work and connect to localhost port 5900.
> This way you should get the windows screen of your box at home.
>
> You have now tunneled VNC on a SSH connection.
>
> Succes.
>
> Jan Hugo
>
>
Jan,
I think you're half way there.... You have created a connection
from ssh (at work) to the home public IP, and are tunneling
port 5900 over tcp port 443, . But, where is the other end ?
Don't you need someone listening on the public IP at port
443 ? and that someone just happens to be sshd, so it
can decode the port : hostname : port, pull the data out
of the tunnel and forward it on to the correct client ?
I believe that the original poster was trying to create a
connection from work, through a Linksys router, to
a system behind the router. So.... I'm not sure how your
suggestion would work in his/her environment.
Perhaps if you had sshd running on the remote client, and
it was listening in port 443, and the Linksys was forwarding
tcp port 443 to that client, then the plumbing of 5900 localhost
(at work) would get delivered to the client's sshd, decrypted,
and directed to the client at TCP port 5900.
If you're going to all that trouble, you probably don't need
the -p 443, and could just use the default (22) and set the
Linksys to forward TCP 22, to the client that is running sshd :-)
Enjoy,
Postmaster.