If you use TightVNC, you probably noticed that whenever you access Services or Permission settings, the target machine stops responding to remote commands.
The problem lies within UAC. You have to disable UAC for VNC to run properly. Nothing to worry about: UAC does not replace a decent antivirus and Microsoft obviously failed to create Linux-like user permissions system. So UAC is nothing more than an added annoyance.