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
> E
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
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 a
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 cli
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
co
