Hi Scott, This has now happened on two sites. I managed to recover the one site by completely uninstalling EchoVNC and re-installing it again - with the DSM enabled.
The actual error message says "protocol error" and only suggests that DSM might be the problem. Is there a log file I can look at which might be more detailed? I have now re-run the install/upgrade sequence using my laptop. I have tried upgrading from 2.10A to 2.35 and 2.34 to 2.35 but the problem has not recurred. I am going to get the problem site to uninstall the current version (2.10A) and re-install 2.35 from scratch and see how that goes. I did think about InstantVNC but the bandwidth to this site is very variable at best and one VNC channel is a challenge sometimes! BTW, all of our sites are fully patched XP-Pro. 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 > > > > ------------------------------------------------------------------------- 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
