I'll have to wait until someone can restart the clients during business hours to get the logs.
-----Original Message----- From: Scott Best [mailto:[EMAIL PROTECTED] Sent: Friday, February 10, 2006 12:20 AM To: Alexander Alekseev Cc: [email protected] Subject: Re: [Echovnc-users] Clients deleted after echoserver goes into standby 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&kid=103432&bid=230486&dat=121642 _______________________________________________ Echovnc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/echovnc-users
