On Mon, 02 Apr 2001 17:25:55 -0600, you wrote:
>Of course, if you don't have access to the firewall, or the
>administrator perversely refuses to allow SSH connections, you
>are SOL. But I would argue that, since you *must* open some
>port, all other things being equal, the SSH port (22) is the
>best candidate from a security perspective (and I assume
>you are security conscious, given the existing firewall setup).
Any other port is out of the question. I was pleased to be able to keep a
pcAnywhere port open long enough to do the bulk of the development, but I
had to give in to political pressures and conform to security policy. I
couldn't remain an exception for ever.
I got vnc working here on my network using standard ports, but need to
configure the server to operate on something else than the standard.
I could stop the smtp service temporarily I suppose. I can't individually
stop port 80 OR 81 with a "net stop w3svc" as I'd then lose my lifeline.
Question is, how do I configure the vnc server to listen on 25?
I can then issue a command over http to run a batch file to stop the smtp
service then start vnc. I can then use a vnc session over port 25, then
when finished, issue another command over http to stop vnc then restart
smtp.
I can update the vnc settings with a registry set over http, but I cannot
see how to set the listen port for it.
On my system here, the GUI won't allow me to enter -5875!
Cheers,
Andy.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Haveland-Robinson Associates Tel. +36 30 223 2158
Budapest 1015, Donati u.17 fszt.1, Hungary Web: www.haveland.com
---------------------------------------------------------------------
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
---------------------------------------------------------------------
