There are literally thousands of computer problems that could be fixed remotely, thus saving your beleaguered helpdesk guy (or son… or husband) a long car trip just to click on a few icons. One of the main reasons why remote assistance hasn’t taken off even more than it has is due to a problem of access. Microsoft’s “Remote Desktop” would be an ideal solution to this problem, if not two significant issues: Remote Desktop is only available in Windows XP Professional, Windows Vista and Windows Server 2003, so if your client or loved ones run Windows 2000 or Windows 98, you’re out of luck. Remote Desktop also locks the console session (the session displayed on the monitor) as soon as someone logs in remotely. This isn’t a total deal-breaker, but it is sometimes convenient to have both the local and remote users looking at the same thing, so the helpdesk guy can see exactly what the end user is doing to get an error message.
Symantec sells a program called pcAnywhere that works on every Win32 platform and allows both users to see what’s going on. However, the program is a bit expensive, has a lengthy and non user-friendly setup process, and requires the end-user to make changes to his or her router configuration before someone from the outside can connect to the computer.
Enter VNC. It has all of the advantages of pcAnywhere but is completely free of charge. It also has all of pcAnywhere’s disadvantages too, but some enterprising folks on the ‘Net have come up with an interesting work-around: a way to “package” VNC so that all the end user has to do is click their mouse a couple of times to allow you to connect remotely. Although you’ll find complete instructions at the link below, the set up basically works like this:
Continue reading “Packaging VNC”