Best way for security

[Scott C. Best]

Len:

 	Heya. Here's a suggested solution: install EchoVNC
on your RealVNC Server PC. Use EchoVNC to establish a secure
connection with an echoServer that's running on a "public IP";
i.e., somewhere you can access from anywhere (e.g., the one
at demo.echovnc.com). Then while you're away, use EchoVNC on
the Viewer side to login a second time to the same echoServer.
You can then initiate a "relayed" VNC connection back to your
office, simply by using your 1st login's "user-id".

 	By doing it this way, you don't need to leave any
TCP ports "open" on your business computer LAN's firewall.
Also, the logins to the echoServer are password-protected, and
"anonymous" to other users, making it nearly impossible for
someone else to establish an unwelcome VNC connection. Lastly,
if you have the OpenSSL software installed, the entire data
connection is128-bit AES encrypted end-to-end, so it is
"content secure" even from whoever's running the relay
server.

 	More info here: "http://www.echovnc.com". It's free,
open-source, Windows-only, and works with any flavor of VNC
(Real, Tight, Ultra, etc). You can freely use the either the
demo echoServer, or run your own (it's a shareware app
available for both Windows and Linux).

 	I hope it helps!

cheers,
Scott

> I need to access my business computer from another location over periods
> of several days duration, during which no one will be available to
> physically use my computer to start the server. It seems I need to run
> VNC server the entire time, leaving the computer open to potential
> unintentional access.
> Is there a better, meaning safer, way to do this? Is there a way to
> reverse the process and run the server on the remote computer, the
> viewer on my office computer, but reverse the control so I can see the
> office computer not the remote? Even if this is possible, which I doubt,
> is this any more secure? Any suggestions are appreciated.