How to keep TightVNC client on Windows XP alive when connected to OS X?
- by craibuc
I'm using TightVNC on my Windows XP workstations to connect to a remote OS X box (10.5.x) using OS X's VNC support.
I've noticed that the TightVNC will become unresponsive after a period of inactivity. Is this a common issue? Restarting TightVNC solves the problem, but can be a bit annoying. Is there a solution to this?
I don't suppose copy & paste between the two systems can be made to work?