No-input problem: solved!

[Mike R. <mik...@pr...>]

Now promise not to laugh :o) but was having problems with TightVNC
suddenly not registering any remote keyboard or mouse input :(  Turns
out the solution was staring me in the face..

I'd read the standard suggestions given to people with similar problem
(check "view only" & "block remote input events" settings, ensure
primary & view-only passwords are different) and these seemed OK. "block
remote input on local activity" was still checked on the server, but I
assumed(!) this couldn't be a factor for 2 reasons:

Firstly I know there is nobody on the remote machine. OK perhaps my
optical mouse is over-sensitive and detecting phantom movements or
something, however - and this is the thing that seems odd to me - the
problem *only* occurs when connecting with the TightVNC executable, not
the Java viewer or even the RealVNC client. Which would suggest a
problem with the client, not the server or any potential local input.

Turn "block remote input on local activity" setting off and everything
starts working again. Well duh! you may say..but I'm still intrigued why
the executable viewer seems to think there's local activity going on
whereas the Java viewer doesn't..

Hope this makes sense,
--

M.
# Tried to run, tried to hide.. Break on through, Michael Ironside!!


This message has been scanned for viruses by BlackSpider MailControl - www.=
blackspider.com