> >If the firewall in question allows arbitrary
> >outgoing connections (which is not uncommon), then you could simply have
> >the service running on the server, run vncviewer in "listen mode" on your
> >machine (the install should have placed such a shortcut in your start
> >menu), and then issue a command to the server so that its WinVNC opens an
> >outbound connection to your vncviewer. This would make the port
> >irrelevant, and no services would have to be shut down, even temporarily.
> >
> >Which of course won't work if you are also behind a firewall or
masquerade,
> >unless you can configure your local firewall.
> It's a big IF... The client's firewall is unforgiving. 25/80/81. I don't
> even have outgoing http from the webserver to get upgrades!
>
> I got vnc locally working on port 25 on my network after a huge amount of
> research and piecing together incomplete advice from many sources.
This is a bad idea. The firewall is probably there to prevent outside
machines accessing things they shouldn't inside your network. Forcing VNC
to operate over one of the three open ports in the firewall is equivalent to
just taking the firewall down, or opening up the normal VNC port.
It's much better to get SSH installed and open the SSH port, then tunnel
whatever you like (VNC, telnet, FTP, etc) through that, instead.
Cheers,
James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
---------------------------------------------------------------------
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
---------------------------------------------------------------------
