"Scott C. Best" wrote:
>
> Gerard:
> Heya. I'd suggest not trying to work-around the
> corporate firewall and SOCKS proxy, but rather to use them.
That kind of use of a proxy could be excactly what a work-around
the corporate firewall is! Of course it all depends on how the
proxy is configured. But if it's a Socks proxy, and it only does
ports 20, 80, 443 (like in the OP's case) you can expect that
you're not supposed to use it for VNC. Same goes for packet
filtering firewalls, and using a HTTP proxy for other protocols
(Not that I'm 100% innocent myself in that respect.)
> It's not optimal but...grab a copy of httptunnel, and setup
> one side at work, and another side at home:
>
> http://freshmeat.net/projects/httptunnel/
>
AFAIK httptunnel does not support Socks, what the OP seems to be
using. But it is a great tool for use with HTTP proxies.
> I had to do this to get SSH support, which my
> company's IT staff refused to authorize. If you're not
> adverse to compiling the application, it works rather
> well.
<...>
Good for you!
--
Harmen
http://www.xs4all.nl/~harmwal/
---------------------------------------------------------------------
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
---------------------------------------------------------------------
