Dilwyn Jones wrote, On 22/10/08 19:50:
I would agree. I use LogMeIn regularly and it is very simple to set up.

On 22/10/2008 17:02, Dave Walker wrote:
You might want to look instead at the LogMeIn product as this does lot
require that kind of special network setup.  This is the latest
incarnation
of what many years ago was called "PC Anywhere" for those with long
memories.  The version of LogMeIn with basic remote control is free for
private use.   I have used it successfully with a number of friends who
want
remote support.   It is easy enough to talk a user through downloading
and
activating their end as it is basically a case of following on-screen
prompts.
OK, I downloaded it and installed it. Not straightforward - all sorts of
things went wrong, including my anti-virus taking a strong interest in
preventing it doing what it was trying to, which may have been the cause of
all the things which went wrong.

If I understand properly, it works as a full version for a month then reverts to a "receive-only" mode, which (maybe I misunderstood) isn't what I wanted.
Either way, it was extremely unclear what was happening half the time.

For family members, I should be able to get to their routers to set the
relevant access details and use standard remote assistance for that.

I'll give this a try, as it seems a logically simple solution (trying to offer computer assistance by definition it has to be simpler to use than the problem it's meant to solve) but I usually end up throwing away this kind of software after early problems like this, on the basis that if they can't be
bothered to make it a trouble free installation, the rest of the program
won't be up to much. It might be easy for a software pro to use, but first impressions are very poor and I certainly would not like to talk anyone through this installation after all the things which went wrong here.

I use tightvnc which is free and hassle free.

You get them to accept all the defaults - ie install server and launch server on boot.
They are then thrown into the server admin interface to set a password.

When the tightvnc icon is showing in systray, get them to hover the cursor over it and note the IP address. It will show all assigned IP addresses including internal network ones. It is the public one that is needed.

If the tightvnc client is then run from the remote machine it can log in using that IP address.
You are then seeing and using their machine.

Tony


--
QBBS (QL fido BBS 2:257/67) +44(0)1442-828255
[EMAIL PROTECTED] http://firshman.co.uk Voice: +44(0)1442-828254 Fax: +44(0)1442-828255 Skype: tonyfirshman
   TF Services, 29 Longfield Road, TRING, Herts, HP23 4DG

_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm

Reply via email to