|
Re: Need to figure out the best way to confirm a VNC connection...
The source code might be useful, if one is trying to overmanipupulate.
VNC is a program that allows one to control a remote machine by presenting the desktop of the remote machine on the controller's machine, with associated mouse actions and commands being transmitted to the remote machine.
The nature of the beast is that the controlled machine sets itself up as a client while the controlling machine sets itself up as a server. This means that the controlled machine must initiate the contact, and that it will control access by means of a password.
What it is is a free application that performs (if controlled correctly) as a GoToMyPC.
The controlling machine must know the controlled machines IP address. This presents problems when the controlled machine has a dynamic IP, rather than a fixed IP. One solution to this is for both parties to agree to use a dyndns service to stabilize the situation.
I don't see the problem if control of the customer's machine is agreed upon. The client fires up VNC. You fire up VNC. The client gives you a password and their current IP address. You contact. You fix their problem. It's a done deal.
If the client needs help, and you aren't aware of it, perhaps you should check your email or your phone messages. If your client doesn't need help, and you're just trying to access their machine, shame on you.
|