I ran this command and could get it to work with RealVNC Open/Free edition viewer. Ensure that on the client, the color level is set to Full Options-Colour & Encoding-Colour Level sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -activate -configure -access -off -restart -agent -privs -all -allowAccessFor -allUsers -clientopts -setvncpw -vncpw secret -setvnclegacy -vnclegacy yes This method works via the command line (local terminal and remote ssh session too). A few years later, the 'world has changed', so The free version of RealVNC (v. 6.17.1113, Nov 2017, x64) works smoothly for me. In particular from Windows 7 Professional to OS X Yosemite (10.11) and to OS X High Sierra (10.13 w/ latest updates), the 'OS X Authentication' that Mac OS builtin VNC requires, with username and password and no tweaks to the VNC server side, posed no problem. These are security types 30 and 35: see Although performance was clearly lacking. It's using ZRLE compression; perhaps JPEG or something else is superior, and perhaps professional RealVNC is optimized.
Jump to Does TightVNC work on Mac OS X? - Currently, we do not offer a version for Mac OS X. It's very likely that TightVNC will include one in. Read reviews, compare customer ratings, see screenshots, and learn more about Remote Desktop - VNC. Download Remote Desktop - VNC for macOS 10.7 or later and enjoy it on your Mac.
TightVNC and TigerVNC both fail complaining those are unknown codes. And do everything over a VPN for heaven's sake if going through the Internet. Any VNC client I've tried works. On your Mac. Go to System Preferences - Sharing - Enable Screen Sharing.
Click the Computer Settings. Button. In the drop-down sheet, check both boxes for Anyone may request permission to control screen and VNC viewers may control screen with password:. Enter a password. Click OK button. Leave system preferences Once you've done that, be sure not to use 256 colors. Then, when connecting from your other computer you should be prompted for a normal VNC password, followed by the OsX login screen, where you can choose the user you'd like to log in as.
I use a Mac Mini as Home Entertainment System (no keyboard or mouse connected). To access the Mac Mini from my Windows 7 PC I use VNC (note the Windows 7 PC has a German keyboard). My problem is that I can't get the Mac 'Option-Key' to work. Googling the internet brought up the following tips (which did not olve the problem):. switching the keyboard to US.
using KeyRemap 4 for Mac. Change the VNC Viewer (Ultra VNC, Tight VNC) So I found the special keys configuration in the Mac system preferences keyboard special keys. Here I don't manage to make any settings since the remote keyboard (= VNC connection) is not recognised - the system state is 'no keyboard connected'. Does anyone know a virtual keyboard I could install?. Do you know any alternatives on how I can get the options-key to work (using a VNC-viewer)?
I found nearly the same problems with Mac-Mini (late 2012), with Italian keyboard. I've performed some tests with Event Viewer tool found into KeyRemap4MacBook software, by comparing events with the local keyboard and the VNC connected keyboard. I suggest to use it to find what is happening for keyboard related problems. I've tried with the native VNC server installed in OS X 10.8.4 Mountain Lion, the one installed in OS X 10.6.8, with VineVNC server (v4.01) and RealVNC server (v5.0.6).
Here my most interesting findings:. Leave native language keyboard on the remote Mac, but set 'US Keyboard' on the local PC. Use VineVNC server, because I found this is the only VNC server that generates complete Mac keyboard events. For strange reasons, with TightVNC both the native OSX server and the RealVNC server treats both the Win/Alt keys as Command.
Use RealVNC or TightVNC (2.7.10 or above see ) clients to have 'Option' key enabled: TightVNC prior to 2.7.10 and UltraVNC viewers do not send the 'Windows' key (which will be mapped to 'Option' mac key). In my tests the real events that are received by the server are always different from the local events of an attached keyboard. For example there is no distinction between left and right buttons when you are connected with VNC (for every client I've tested). RealVNC client version used is '5.0.5 Windows 64bit' on Windows 7 Professional. About the 'no keyboard connected' error, I've not tried nothing but connecting a keyboard to the MacMini (when I'm remotely connected I need to have a real keyboard connected to the Mac Mini!).