Alexander:
The "auto-reconnect-unless-bad-password" is by design, yes. It's
interesting, though, that the echoServer would assertively transmit a
"failed password" message when it recovered from sleep. I'll see if
I can reproduce that here.
Can you provide the .log files from the client side, and the echoserver
side? That could be useful too.
thanks,
Scott
On Feb 9, 2006, at 8:32 PM, Alexander Alekseev wrote:
I had two clients using echovnc and realvnc server connected to my
echoserver.
The machine running echo server went to sleep, and upon waking up,
both connections were deleted due to traffic loss.
Then the logs show the clients attempting to connect to echoserver,
the username shows fine, but then the log says user/pass invalid
and disconnects the clients.
At this point the clients don’t seem to try to reconnect anymore.
I’m not sure if this is an issue with echovnc or with echoserver,
and whether echoserver can handle multiple standy/resume by design.
If it can’t I’ll have to move echoserver to an always on machine,
but that may not be my best option.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
