In VNC Enterprise Edition 4.5, it is intended that a VNC Viewer user should be able to press any key or key combination and the expected result will manifest itself seamlessly on the computer running VNC Server. If you are connecting to a Mac from a Windows or Linux PC, or vice versa, the two computers are likely to have different keyboards.
May 14, 2007 - Apple includes a VNC server in every edition of Mac OS X 10.4 and later. You can start the server through a discrete check box in the Sharing. A little-known fact about Mac versions 10.4 (Tiger) and over, is that they come with a built-in VNC server. This feature is included in a couple of the “Sharing” options and can be accessed with a regular VNC viewer/client. However, when connecting from a Windows machine (particularly when.
![Vnc viewer for mac host refused connection Vnc viewer for mac host refused connection](/uploads/1/2/5/5/125501642/169585566.png)
Some keys will be unique, and some keys with the same name perform will perform different functions. For example, the key marked 'Alt' on modern Macs (also known as the 'Option' key) performs a different function to the 'Alt' key on PC keyboards. (It is most similar to the 'AltGr' key on non-US PC keyboards.) Consequently, in version 4.5, the Mac's 'Option/Alt' key is not mapped to the 'Alt' keysyms over the RFB protocol. (This is a change from version 4.4.) This page summarizes the keys and key combinations you need to press in order to achieve the result you expect if at least one computer is running Mac OS X. Definitions: On this page, the Mac's 'Option/Alt' key is referred to as Opt.
Suffixes L and R refer to the left and right variants of keys. Alt refers to the 'Alt' key on a PC, Win to the 'Windows' key (represented by the Super keysyms over the RFB protocol), and Cmd to the 'Command' key on the Mac. In addition, a host computer is the computer to be controlled, running VNC Server.
A client computer is a computer to connect from, running VNC Viewer. Contents.
Controlling a Mac host computer from a Windows or Linux client computer To emulate on a Mac host. On a US PC keyboard, press. On a non-US PC keyboard, press. Cmd AltL or Win AltL or Win Opt AltR AltGr Opt+Cmd AltR+Win or AltL+Win AltL+Win From a US PC keyboard, AltR+char key will be interpreted on the Mac to give extended characters. From a non-US PC keyboard, AltGr+char key will be interpreted on the PC where possible, so some Mac extended characters may be unavailable.
A similar restriction occurs across other VNC Servers - the solution is to either switch to a keyboard layout on the client computer that is capable of producing the required character, or to use the Mac's 'special characters' dialog. If you need to specifically press the left or right Cmd key, AltL maps to CmdL on the host computer, Win ( L or R) maps to CmdR. OptR can only be produced by changing the parameters from their defaults. Controlling a Windows or Linux host computer from a Mac client computer To emulate on a Windows or Linux host.
On a Mac keyboard, press. AltL CmdL WinL CmdR AltR and WinR can only be produced by changing the parameters from their defaults. Opt on the client computer will be interpreted locally to produce extended characters, but will also send the ISOLevel3Shift keysym for OptL, and Modeswitch for OptR.
These keysyms are typically bound to the AltGr key in the X Window system. ISOLevel3Shift is typically used by newer X installations, Modeswitch by older ones. Controlling a VNC 4.4 Mac host computer from a VNC 4.5 Mac client computer To emulate on a 4.4 Mac host. On a 4.5 Mac keyboard, press. CmdL CmdR OptL CmdL Opt+Cmd CmdR+CmdL CmdR and OptR can only be produced by changing the parameters from their defaults.
Controlling a VNC 4.5 Mac host computer from a VNC 4.4 Mac client computer To emulate on a 4.5 Mac host. On a 4.4 Mac keyboard, press. CmdL Cmd or OptL OptL OptR (with SendExtendedCharacters option off) OptL+CmdL CmdL+CmdR (but see caveat below) CmdR and OptR can only be produced by changing the parameters from their defaults. Pressing CmdL+ CmdR on the client computer will send keysym presses that the host interprets as Opt+ Cmd. However, because of a VNC Viewer issue one of the CmdL or CmdR keys will be left 'stuck' down. You will need to press and release this key before continuing. Mac parameters for Cmd and Opt keys Parameter name Default value LeftCmdKey AltL LeftOptKey ExtendedChars RightCmdKey SuperL RightOptKey ExtendedChars The parameters are the same on the client and host computers.
Each parameter specifies which keysym should be generated (client) or interpreted (host) for the given key on the Mac keyboard. The value ExtendedChars means that the key should be used to generate extended characters, and will also send the ISOLevel3Shift keysym (or the Modeswitch keysym for OptR).
Screen sharing sharing is an excellent tool to allow remote use of your Mac OS X server. The issue is you may occasionally run into the situation where you receive “The Black Screen”, a white screen, or screen sharing just locks up all together. After struggling with this issue for a while I have finally discovered the solution!
We are going to kill the window UI that is currently logged in (or not). This will NOT affect any applications that your currently have running on your server. You will need to be sure that your server has SSH enabled. On your client open up Terminal (OS X or Linux) or use PuTTy (Windows), login to your server and perform the following commands: ps auxwww grep loginwindow This should give you an an output like this: root 777 0.0 0.1 25??
Us 3:15AM 0:00.08 /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow console jc 953 0.0 0.0 2425708 276 s000 R+ 3:15AM 0:00.00 grep loginwindow You may have a few different lines, but essentially you’re looking for the root line, the process id in my case is 777. Now that we have the process ID we will want to issue the kill -9 command and it would look like this: sudo kill -9 777 After killing the process your server will automatically restart the login. You should now be able to start screen sharing and login!
“the process id in my case is 925” is incorrect. The process ID as shown is 777. This is confusing. You should also add that this requires one to SSH into their remote machine to issue the command. You mention SSH being enabled but not the process of connecting to their remote machine and issuing these commands to it, from their local machine. Local Machine Remote Machine (locked out), so you use Local machine to SSH into Remote Machine (SSH via Local Machine Terminal) and then issue the commands. I looked for “console” at the end of my user string and it worked.
With those caveats, this worked well for me.