Sorry, forgot a URL to the latest echoServer:
ftp://ftp.echogent.com/EchoWare/echoServer_1.31_Setup.exe
cheers, Scott
On Mon, 18 Apr 2005, Scott C. Best wrote:
Peter:
Heya. Some answers and suggestions below:
Hello,
Three items:
1) CAN'T FIND [email protected] signup on www.sourceforge.net
Ouch; sorry about that:
https://lists.sourceforge.net/lists/listinfo/echovnc-users
2) Observation: Must quit and restart all EchoVNC's if server stops then restarts.
This bug may be resolved with the 1.52 version of echoWare, which is part of the 1.1 release of EchoVNC. Please give that new version a try and see if it helps.
3) ERROR MESSAGES on attempt to "Start a VNC Connection": PC 1: Win XP Pro at 64.251.vv.xx, Running Echo Server 1.30 Running EchoVNC 1.0 Running RealVNC server Free 4.1.1 DLink Router with port 1328 forwarded
PC 2: Win XP Pro at 64.251.yy.zz Running EchoVNC 1.0 Running RealVNC server Free 4.1.1
EchoServer starts & stops correctly. Shows each EchoVNC client as it connects. Both EchoVNC's report connection with server.
On "Start a VNC Connection" the progress messages indicate finding partner, etc but no desktop window appears. (Once the desktop did appear for 1 second).
Tried starting EchoVNC on Win98 PC (PC3) on same DLink router as PC 1but got similar (same?) error when trying to connect to either PC1 or PC2.
Just confirming: you got the VNC password prompt, or not?
In EchoVNC 1.0, it repeatedly checkd for the presence of a VNC server by repeatedly connecting to the VNC server port (TCP 5900). In RealVNC 4.x, these repeated connections are seen as authentication failures, causing RealVNC to increase its "minimum re-attempt time" between connections. If you didn't get to the password prompt, this could be part of the problem. In EchoVNC 1.1, we decreased the frequency of checking so that it doesn't set off this added security feature of RealVNC. We also improved the connection-buffering at startup of the relay channels in version 1.31 of the echoServer for Windows. Please grab that latest version and see if it helps.
Thanks for the very detailed bug report. I'm very interested if our weekend updates to both EchoVNC and the echoServer for Windows helped your situation.
thanks, Scott
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Echovnc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/echovnc-users
