I think you mixed up the use of VNC viewer and VNC listener. Use VNC
viewer instead since you've already open the necessary port in your router.
Since you've renewed your IP address (not your DHCP, actually), it
might have been changed. Don't forget to adapt any change of IP address
From your discussion, I can see there's a confusion or misunderstanding
in command line options. As far as I can see, some options to winvnc4 are
mutually exclusive. For example, when you use -start, PortNumber is
ignored. In other words,
winvnc4 -start PortNumber=12345
only starts winvnc4
John:
Heya. Please try this:
1. Download EchoVNC 2.31 and install it on the PC you want to
take remote control of (eg, your work PC). The startup Wizard
will automatically detect your RealVNC server and configure
itself to work with it correctly.
2. During the Startup Wizard
Thanks all,
Especially Scott,
I installed easyvnc server and all of a sudden all my problems are solved!
I can now vnc to my hearts content.
Next job is to get an ssh tunnel set up and encrypt the lot.
Thanks again
John
On Dec 11, 2007 6:17 PM, Scott C. Best [EMAIL PROTECTED] wrote:
John:
John:
Heya; glad it works! Please note that echoWare (used
by EchoVNC) utilizes the same OpenSSL toolkit that many SSH
platforms are based on; content is end-to-end encrypted with
128-bit AES. EchoWare is all open-source, so you're welcome
to look around it:
