Re: VNC client/server combo doing VNC over HTTP
2 short infos to clarify :
1. VNC over http doesn´t exist
Is that strictly true? Both Ultra@VNC and RealVNC Personal Edition offer
a version that allows access through a web browser on the client side,
specifically to be more firewall-friendly; what are they doing if they
are not putting VNC over HTTP(S)?
2. Port-Numbers can be altered with any version
I do know that much, but that's only half the problem; the protocols
allowed by the corporate firewall are the other half...
Thanks for the suggestion, I'll try it right away, but I don't expect it
to work as I expect I'll find the firewall is not configured to allow
SSH going out of the network to the internet any more than it would
allow incoming SSH (we are talking about a multinational corporation
Solution would be : ssh on Port 443 ... with that you can trick most
proxies with the "connect" method to use any proxy-capable ssh-client
(putty for example)
-> after ssh-connection is ok .. you can do vnc-over-ssh (simple
more professional :
use SSL-VPN-software like ssl-explorer(
http://3sp.com/showSslExplorer.do?referrer=sslexplorer), which can do
port-forwarding in y very simple manner
Unless I am being inordinately stupid, in which case please have
patience with me and correct me, hard-core firewalls are filtering based
not only on port number but also on protocol. I am not sufficiently
senior in my organisation, nor is what I'm trying to do sufficiently
strategically important, to give me the power to influence my company's
internet facing firewall policy; so the only option left is to find a
way to tunnel this traffic over an existing open port/protocol combo.
The most reliably available is HTTP(S) over the usual HTTP(S) ports eg
80, 81, 443, etc...
On 3/10/06, *Mark Fletcher* <firstname.lastname@example.org
I'm looking for a VNC server to run on my home Debian setup that will
allow me to connect to it from work. Trouble is, work is behind a
(justly) paranoid corporate firewall which will allow me to
on HTTP/HTTPS on the usual web ports and not a lot else. So I'm
for a solution where the server can be Debian, the client can be
2000 and comms between the two can be HTTP or better HTTPS over
I stumbled over x11vnc which looks good but doesn't appear to support
communicating over HTTP(s). And my searches on sourceforge etc find me
products that do what I want but the server side has to be Windows.
Anyone got any alternative ideas?
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact