To install and configure EchoVNC: Go back to Tevlin Links
On both machines, Go to
http://www.tevlin.org/links.htm#Web_Tools_ for the latest version, download and run: EchoVNC
After installation, a wizard runs. It may ask if you have a profile to load, answer No.
You can allow it to connect to
Here are the settings for fill in:
EchoServer: tevlin.servehttp.com
Machine Name (connect as): Something unique for each machine, one word (no spaces). This is the Partner ID you fill in the box when the “Client” (there) clicks “Start a VNC Connection” on the Main (1st) tab.
Password: ask Pete
Register EchoVNC Server as a system service and Start or Restart EchoVNC Service and (if desired) Create EchoVNC desktop icons and Next and Install.
A screen appears saying you need to set a password. Click OK and a : Default Local System Properties screen appears. Type in a password and OK. Leave the other settings as they are set (defaults).
You can get back to this screen later by right-clicking on the new EchoVNC icon (like the CBS eyeball) in your system tray and choosing Admin Properties. Here you can also choose to check Display Query Window if you want to be prompted to “approve” an incoming connection.
Then, give the Partner ID and your password to the Client. He clicks “Start a VNC Connection” on the Main (1st) tab, fills in your Partner ID and chooses Connect via EchoServer. You will not be able to connect unless both machines display “Connected” under Status on the EchoServer Properties [rightclick on blue icon in system tray] (3rd) tab. If all goes well he is prompted for your password. He fills it in and the session begins.
If he has also installed EchoVNC, the top (blue) title bar contains icons for him to go full screen, change color depth, send Ctrl+Al+Delete, Start button, etc. If he hasn’t, he can right-click in the title bar for (most of) these options. I believe both must have EchoVNC installed to initiate a chat between you two, if needed; and it would also be required for you to be the “Client”.
Notes:
There is a newer version of EchoVNC available (v2.0) that has incorporated the EchoVNC capabilities. I’ve tried it and would rather recommend it but I just can’t get it to be reliable and it is not fully compliant with the VNC spec, so other local (intranet) things that worked fine for me were broken after its install.
The 1.40 EchoVNC is pretty stable but also has (at least) one quirk. I’ll describe that here so you’re not pulling your hair out late one night and blaming me for getting you into this remote access mess...
All seems fine in EchoVNC and it reports connected but you cannot see (failed to connect to partner) the other guy who also reports connected. You right click on the black EV system tray icon and choose Exit EchoVNC. It disappears. The problem is it is still in memory and you have to kill it in Task Manager (Ctrl+Shift+Escape, Process tab). Then you can run it again and all should be well. But, as we discussed, I had to fully re-install EchoVNC recently to get it to work. In retrospect, this may have been because I had tried and then uninstalled the 2.0 EchoVNC without uninstalling EchoVNC first so some overlap of services or components probably occurred (v2.0 knew my password without prompting me, for example).
My most recent/favorite remote connection method is EchoVNC SingleClick because the person whose screen you are trying to take control of doesn't have to do all of the above to let you do it. They just run this app and I'm on their desktop in an instant. I just have them click the yellow connector link on my Links page, run the download, doubleclick the "Connect to Pete line" and presto, I'm in!