Wild. :) Still, a Guinness! All of my bugs should be so enjoyable.cheers, Scott On Aug 7, 2008, at 7:20 AM, DG wrote: > In conclusion... > > The remote PC suddenly accepted the connection (no changes made > anywhere > - honest) so I hurriedly installed InstantVNC and created an > EchoServer > account for it. I connected to the temporary session, uninstalled 2.34 > and installed 2.35 and then connected to it. It all works fine now but > what the problem was I shall probably never know. > > Thanks for the InstantVNC tip Scott. > > It's good job I cracked it as it's a 90 minute drive to Holyhead > followed by a 2 hour ferry crossing across the infamous Irish Sea, a > drive through Dublin's labyrinth and a 3 hour drive south to get to > the > site in, of all places, Tipperary. Excellent Guinness though ;-) > > Regards > > David > > Scott Best wrote: >> Weird...it sounds as if the DSM plugin option got enabled, either >> on the Viewer or Server side. Haven't heard of that happening before, >> without the user actually activating it, of course. What flavor of >> Windows >> are you running on the side showing the problem? >> Also, FWIW, your client can run InstantVNC and EchoVNC at the >> same time, so you can debug one while connected with the other. :) >> >> cheers, >> Scott >> >> >> On Aug 6, 2008, at 1:46 PM, DG wrote: >> >> >>> I have been using 2.34 for some time with no problems. I upgraded my >>> system to 2.35 today (took all the defaults) and it worked ok with >>> all >>> of my clients; some of which are on my EchoServer and some direct >>> using >>> TightVNC. >>> >>> I then got one of my clients to run the 2.35 upgrade and now I >>> cannot >>> connect due to "DSM issues.. and Invalid Protocol". We never used >>> DSM >>> although it was usually installed by default so why is it a problem >>> now? >>> >>> As it is the upgraded server that is causing the grief then either >>> something went wrong with the install or the 2.35 server has a >>> problem. >>> >>> The only things I can think of are; that 2.35 might have been >>> installed >>> over 2.34 (ie 2.34 non uninstalled) but upgrading like this before >>> seemed ok. Or the 2,35 upgrade was done whilst 2.34 EchoServer was >>> still >>> running and this has caused some problems in the configuration >>> >>> Whatever the cause, I now have to decide whether to go back to >>> 2.34 on >>> both sites or try a complete uninstall/re-install at the client >>> site - >>> over the telephone... ;-) >>> >>> Any other ideas? >>> >>> David Goadby >>> >> ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Echovnc-users mailing list Echovnc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/echovnc-users
