Allen:
Heya. Yes, the situation you describe is exactly what EchoVNC
is good at. Some specific answers below:
1. Yes, EchoVNC will allow you to do that. In general, EchoVNC relies
on an echoServer to act as a "relay point" between a VNC Viewer
and a VNC Server. By relaying the data like this, all of the
VNC traffic appears to be "outbound connections" from the point
of view of any firewalls or routers on either the VNC Viewer
or VNC Server side of the connection. Pretty soon, we'll have it
working with web proxies as well.
2. You need exactly one echoServer to make an EchoVNC connection.
Simply "log onto" this echoServer with EchoVNC on both the VNC
Viewer and VNC Server side of the connections and you're ready
to go.
3. The "demo.echovnc.com" isn't necessary, it's just a demo echoServer.
Unlike many other (all other?) relay servers for remote access, an
echoServer is meant to be run by someone in the end-user's community
of users, not by me. The demo server is really just meant for "proof
of concept" (and stress testing) purposes. You can download your own
echoServer software here:
http://echovnc.sourceforge.net/fom-serve/cache/6.html
Ideally, you should setup that server to run somewhere where you can
readily access it from both home or work.
4. When you setup your echoServer, some of this will become more clear.
In general, you create "connection groups" on your echoServer, and
you assign them connection passwords. When you connect to an echoServer
with EchoVNC, you provide a connection identifier (eg, "AllenHomePC"
or "AllenWorkPC") and the connection password. Once connected, you
can initiate connections from one side to the other, using just
the connection identifier (eg, from the "AllenWorkPC", you can start
a VNC connection to "AllenHomePC").
Lastly, the "10 minute" limit just refers to a shareware limit
of the echoServer software itself. When you start a VNC connection, an
unregistered echoServer will disconnect the VNC session after about 10
minutes, requiring you to reconnect. Once you've registered the software,
this time limit goes away.
Hope that helps!
cheers,
Scott
On Wed, 3 Aug 2005, Henderson, Allen wrote:
Hi,
Problem description: At work we are behind a firewall and at home I've
Verizon home DSL via a Westell wireless router bridge connected to 2
wireless PCs and 1 LAN "hard-wired" PC. I'd like to periodically connect
to one of my "wireless" home computer desktops during the day and use
it. Likewise, in the evenings and weekends, I'd like to connect to my
work computer and use it. All run XP and the two I want to use in this
arrangement run XP professional.
Questions: 1. Will echovnc allow me to do what I want to do? 2. Can I,
or do I need to configure both PCs as servers to do this? 3. In
connection to question two, is a 3rd server such as demo.echovnc.com
necessary, or for some reason desirable and 4. Do I have to be "logged
in" on both machines for this to work and, if yes, what will logged in
mean in this case (I read on the list about a 10 minute time out, or
something)? Thanks.
-A-
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
