Hi luggies,
Can you please help out my friend who sent me this query?
Thanks.
-Girish
--------------------------------------------------------------
For remote control of PCs, we do the following :
Run VNC server on Remote end PC
Run VnCViewer on Engineer PC
Using the IP number of the Remote End and the password of Remote VNC
server,
we connect to remote end.
This is a tedious process. Maintenance of Password at remote end, Open
Port
of VNC server at remote end, etc. are big issues.
There is a different approach called "Reverse VNC". Here, the client
runs in
a "listen mode" and the remote server "reverse connects" to the client.
Since the connection is made by the remote server, the password of the
server is not required by the client. Further, the IP of the client
(engineer) alone is required for the Remote End. Thus it is the best for
remote control (7000 PCs across India)
If I use both server and client from Tight VNC, reverse vnc works fine.
Same
case with Ultra VNC.
There is a "stripped down" version of UltraVNC called Ultra VNC Single
Click. This is meant only for reverse connection. It is not a
full-fledged
server. Size-wise it is small, and very safe. It kiils the process
itself
after the use
1. If I use this "UltraVNC SC", as server, and the client as Ultra VNC
client, things work.
2. However, if I use "ultraVNC SC" as server and TightVNC as client,
negotiation of "codec" is not successful...
I can live with (1), but my Anti Spyware shouts if I use UltraVNC
client....It does not shout if I use (2)
Question : What is the default "codec" used by UltraVNC? Is there a
"common"
codec for UltraVNC and TightVNC ?
--------------------------------------------------------------
