Going through a firewall
William Hooper
whooper@freeshell.org
Wed Feb 12 01:08:01 2003
----- Original Message -----
From: "Damian Skeeles" <dskeeles@yahoo.com>
> Hi,
>
[snip]
> I'd guess this is a straightforward block by the firewall based on the
traffic type (the fact I can get something on :21 and :80 implies the ports
themselves are open, and I can establish an FTP connection to elsewhere on
:21). Command line pings don't work, probably because they're unaware of the
firewall - hence the reason I tried the HTTP method (using the proxy server
settings in IE5). I'm guessing that the firewall (proxy:8080) is filtering
out the VNC data packets, even though they're being handled through port 80.
No they aren't. The viewer needs to talk on the port 100 above the HTTP
server to work. For example by default the HTTP server runs at 5800 and the
viewer (Java or otherwise) runs on port 5900. VNC also doesn't work by
default over a proxy.
> Just wondering if anyone has had this situation, and found a way through?
Is there a tunneling protocol that can 'disguise' itself as standard web
browser packets, for example (excuse my ignorance!)?
>
> Many thanks,
>
> Damian
The best way through is to talk to the firewall/proxy administrators and
give them A GOOD REASON to let your traffic through. Anything else is
asking to be reprimanded for misuse of company resources.
--
William Hooper
To err is human, but to moo is bovine.