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?
------------------------------------------------------- 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
