Gordon Steven-QSG001 wrote:
>
> Some time ago I asked about VNC through a firewall that only allows port 80
> to pass through. The following articles were suggested:
>
> http://www.uk.research.att.com/vnc/archives/2000-04/0205.html
> http://www.uk.research.att.com/vnc/archives/2000-04/0294.html
> http://www.uk.research.att.com/vnc/archives/2000-04/0313.html
>
> They imply that if you change the registry for "PortNumber" to a -5720
> (5800-5720=80), you can talk through a firewall that only allows port 80.
> This only seems to change the port number that the authentication uses (the
> initial contact to the VNC host from the VNC client via web browser). My
> understanding is that once the authentication completes, that VNC then
> switches to 5900 for the rest of the connection (It may be called RFB). Is
> this correct? If so, how do you get the rest of the connection that
> switches to 5900 to be on port 80?
580x: http port for receiving the applet-code (including authentication
panel)
590x: rfb port for actual VNC (including actual authentication).
With a native viewer you can do without the 580x-port.
There are patches that allow use of just 1 port for both rfb and http.
http://home.earthlink.net/~jknapka/vncpatch.html
There's also another solution, that doesn't require adjusting the ports
your vnc-server listens to, but I admit it's a bit complicated, and
often not the best solution available.
http://www.workspot.net/~harmen/vnc/readme.html
You could also use a port forwarder. Best to set up ssh-tunnels, if your
going down that road.
You must however be sure that you are behind a packet-filtering
firewall, and not some kind of proxy-firewall (that allows you only to
connect out through a proxy, probably http).
--
Harmen
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
