do I understand you right - you can`t reach the server directly but have to
use a http proxy ? then, ssh won`t help here...
Well, I think that's the case... My IE web browser at work has all the
proxy server settings in it, and we have to go through a certain proxy
server along with the
Kyle Yamnitz wrote:
I have my own LAN at home behind a LinkSys firewall + router (both
machines are 2 GHz run Win XP). Here are the problems I'm having with
Jim's VNC HTTP Tunneling:
1. When having a friend try to access my system remotely, he gets either
of the following messages
192.168.1.160 is meaningless outside your home network. If you really want to
expose your VNC server to the Internet, you must use your external address
and tell your Linksys router to forward the relevant ports to the machine
where the VNC server runs.
I realize that. The 192.168.1.160
Kyle Yamnitz wrote:
On the other hand, I *can* use SSH software at work to connect to my web
server without a problem, so maybe I would be okay?
Yes. Everything that SSH tunnels is passed through the same TCP connection as
the SSH session itself, so if you can connect with SSH then you can
use SSH :)
you can tunnel vnc through that. this is the most secure solution, too.
I would reccomend doing this.
ssh can run on ANY tcp port and tunnel tcp connections through a single ssh
connection.
see for a first start: http://www.uk.research.att.com/vnc/sshvnc.html
You don`t need an extra
use SSH :)
you can tunnel vnc through that. this is the most secure solution, too.
I would reccomend doing this.
ssh can run on ANY tcp port and tunnel tcp connections through a single ssh
connection.
see for a first start: http://www.uk.research.att.com/vnc/sshvnc.html
You don`t need an
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, March 24, 2003 3:37 AM
Subject: Re: VNC HTTP Tunneling problems...
use SSH :)
you can tunnel vnc through that. this is the most secure solution, too.
I would reccomend doing this.
ssh can run on ANY tcp port and tunnel tcp connections
