Robert:
The "Could not connect to Server!" message is a VNC one.
Is it possible that the VNC Server on that machine is setup to not
allow loopback connections? I believe that's still an option in
UltraVNC that can be turned off and on.
-Scott
On Jun 27, 2005, at 6:44 AM, rjburdge.ks wrote:
I have successfully set-up connections between two remote PC and my
Home PC, so far. A third machine is being very stubborn. I am using
the same versions of EchoVNC and UltraVNC on all machines. My Home PC
is running XP Pro, as is the machine I cannot connect to. The remote
machine in question connects to the Demo EchoServer without problem.
When I initiate a VNC connection from EchoVNC, I get a message saying
that the partner ID has been found and then the UltraVNC pop-up window
shows "connecting ..". At this point a error pop-up is displayed that
either says "Could not connect to Server!" or "Connection closed
unexpectedly". Is this a problem with EchoVNC or UltraVNC? I cannot
tell if the error pop-up is being generated by EchoVNC or UltraVNC.
Once the remote PC connects to the EchoServer is there any
Firewall/Router settings that could prevent a connection? Thank you.
Robert
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
