Heya Scott: One (sort of) minor point:
There are duplicate entries in the startvnc connection userlist combobox dropdown. Anytime you type something in the combobox, then either a) hit enter or b) click to start the connection(not sure which of these or both) even if the name exists already, it adds it again. I remember a similar problem in kaboodle, with the getengaged usernames. I don't think this is a major problem, I don't think it causes any functional difficulty, but I think it would be better if echovnc checked for the name before adding it. Also, is the echoserver case sensitive for usernames and passwords? If so, then echovnc should be case sensitive as well, right? Thanks, David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 11:14 PM To: [email protected] Subject: Echovnc-users digest, Vol 1 #8 - 3 msgs Send Echovnc-users mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/echovnc-users or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of Echovnc-users digest..." Today's Topics: 1. Didn't automatically reconnect after reboot (David Schlesinger) 2. Re: Echo Server (Scott C. Best) 3. Re: Didn't automatically reconnect after reboot (Scott C. Best) --__--__-- Message: 1 Reply-To: <[EMAIL PROTECTED]> From: "David Schlesinger" <[EMAIL PROTECTED]> To: <[email protected]> Date: Wed, 6 Apr 2005 11:49:27 -0400 Subject: [Echovnc-users] Didn't automatically reconnect after reboot Hey Scott: Today I am back to echovnc version 132a with my client, connected no problem. Then, went to install a program for them which required a reboot. After reboot, I could not reconnect automatically. Conditions: 1) I have echovnc in the the clients startup folder - so it starts automatically 2) I connected back successfully to them with pcanywhere - but I want pcanywhere out of the loop 3) says that it was connected to phyliss-prestige 4) echoserver showed '3 clients connected' (should have been 2) 5) I stopped echoserver, restarted it, then deleted echoserver entry from customer's pc - then readded it 6) now i had '2 clients connected' 7) now i was able to connect again 8) however, it was not seamless, seems to me I have problems when the 'connection count' gets out of whack' It seems as if echovnc isn't handling a reboot gracefully? Any thoughts? Thanks, David ps-will be trying to get back up to 152a as soon as possible, hopefully that will help? --__--__-- Message: 2 Date: Wed, 6 Apr 2005 21:31:35 +0000 (GMT) From: "Scott C. Best" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject: [Echovnc-users] Re: Echo Server Robin: Hello! I've CC'd your message to the EchoVNC Users email suport list; you can join it here: https://lists.sourceforge.net/lists/listinfo/echovnc-users That's the best place to go for support first. As for your situation...how did the echoServer appear to "not operate" on Monday? In the EchoVNC GUI, did your echoServer appear as "connected", or does it read something else? thanks, Scott > Hi, > I was able to get a connection between my computer which has a Linksys BEFSR41 router > with a similar computer with the same router at my church last Saturday. I purchased your > license to maintain the Echo Server and it worked great Saturday and Sunday. On Monday > night, I tried again to connect with the church's computer but failed because the Echo > Server was not operating. Again today, Tuesday, I tried again both at home and at the > church to activate the remote server without success. What am I doing wrong, or do I have > to go though a complete rebuild of the system every time I want to connect to the other > computer? > Robin K. Durkee > [EMAIL PROTECTED] --__--__-- Message: 3 Date: Wed, 6 Apr 2005 22:26:56 +0000 (GMT) From: "Scott C. Best" <[EMAIL PROTECTED]> To: David Schlesinger <[EMAIL PROTECTED]> cc: [email protected] Subject: Re: [Echovnc-users] Didn't automatically reconnect after reboot David: Interesting situation, I think I understand it... In general, an echoServer collects users into connection groups. It distinguishes those users within the group by the "partner ID" they assigned themselves when they connected (i.e., the "user id" provided during login). For better or worse, echoServer allows two or more users into the same connection group with the same "partner ID". To connect to one of these users, an EchoVNC user will have to ask the echoServer for a connection to the *IP address* their target user is connecting from. If they ask for a connection to the user based on "partner ID", the echoServer won't know which one they mean, and so it will report a "partner not found" error message. In your example, if there's more than 1 "phyliss-prestige" connected, the echoServer won't know which one to connect you with, so it will report failure (in the future it will report a more useful "non-unique" error). Which is all to say...I believe that the echoServer was telling the truth, and it had 3 connections, two of them to the "phyliss-prestige" machine. Perhaps the echoServer should be smarter: if it has 2 or more connections with the same "partner ID", connecting from the PC, for the same application, it shouldn't matter which one it connects with. But, for now, it's not that smart. Hope that helps! -Scott On Wed, 6 Apr 2005, David Schlesinger wrote: > > Hey Scott: > > Today I am back to echovnc version 132a with my client, connected no > problem. Then, went to install a program for them which required a reboot. > After reboot, I could not reconnect automatically. Conditions: > > 1) I have echovnc in the the clients startup folder - so it starts > automatically > 2) I connected back successfully to them with pcanywhere - but I want > pcanywhere out of the loop > 3) says that it was connected to phyliss-prestige > 4) echoserver showed '3 clients connected' (should have been 2) > 5) I stopped echoserver, restarted it, then deleted echoserver entry from > customer's pc - then readded it > 6) now i had '2 clients connected' > 7) now i was able to connect again > 8) however, it was not seamless, seems to me I have problems when the > 'connection count' gets out of whack' > > It seems as if echovnc isn't handling a reboot gracefully? > > Any thoughts? > > Thanks, > David > > ps-will be trying to get back up to 152a as soon as possible, hopefully that > will help? --__--__-- _______________________________________________ Echovnc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/echovnc-users End of Echovnc-users Digest ------------------------------------------------------- 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
