Chuck:
Hello! What you're suggesting is also known as a "server initiated"
connection.
VNC has had that for years. :) When you have a VNC Server running,
you can right
click on the icon in the service tray, and "Add a Client". That will
cause the VNC
Server to connect with a VNC Viewer (by default, on TCP 5500). So, as
you describe,
the user running the VNC Viewer (who is the more technical one in the
relationship)
can handle all of the details of port-forwarding, and you don't need
an echoServer
at all.
As said, this has been part of VNC for years. The problem that
EchoVNC and
echoServer set out to solve was a different one -- when the support
provider wants
to connect to a *number* of target PC's with maximum reliability and
zero router
manipulation on both sides (not just one side). I've been offering
support advice on
VNC mailing list for many years now, and it's simply amazing how
often the same
questions about port forwarding, firewall exceptions, proxy bypassing
and dynamic
IP addresses keeps coming up.
If you always provide support from the same PC, behind the same
router, with
the same static IP address, and you only need to connect to one user
at a time who
is in front of their PC and comfortable keying in an IP
address...then you're right: you
don't need EchoVNC. Me, I need it. :)
cheers,
Scott
On Mar 4, 2007, at 3:38 PM, Chuck Mongillo wrote:
> Hello all,
>
> I am new to how this method of communication works, so I am hopeing
> it is recieved by people in development for the EchoVNC server and
> the EchoVNC viewer. The archives on SourceForge create and error so
> I can not read that which you have already discussed. (HTTP 500
> Internal Server Error) Please advise if their is another means to
> offer input for this product.
>
> Currently I can not find a way to connect to my EchoVNC server with
> my EchoVNC viewer program without using an EchoServer or using Port
> Forwarding on the EchoVNC server machine. The EchoServer solution
> would be great for non-technical users I understand as the server
> or the viewer application would not require them to deal with port
> forwarding.
>
> My situation:
> I am trying to develop remote desktop control software so I can
> provide tech-support to my clients. I am capable of port-forwarding
> to my machine but my clients would not know how to set this up. The
> problem the way all VNC connections are set up is that the non-
> technical person is the one with the server, and the one that needs
> to be able to do the port forwarding.
>
> My Suggestion:
> Add a connect button on the server side of the EchoVNC software to
> connect to the EchoViewer software.
>
> Now we can bypass having an EchoServer all together. The client
> (Person who needs computer to be controlled) doesnt need to know
> how to port forward as he is making the Outgoing request.
>
> Once connected to my EchoVNC viewer application I should be able to
> take control of their computer over the same connection.
>
> --------- Example Situation ---------------------------------
> (A) -- Person A is a computer expert with the ability to port
> forward to his computer.
> (B) -- Person B is a non-Technical person who simply wants person
> (A) to fix his computer.
>
> (B) calls person (A) and asks for help. Person (A) gives person (B)
> an IP number to begin the connection to person (A)'s computer. Once
> a connection is established, person (A) takes control of persons
> (B)'s computer.
>
> I would not mind offering my time to help create this function if
> it is an option.
>
> Chuck Mongillo
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Echovnc-users mailing list
Echovnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/echovnc-users
