ReleaseEngineering/How To/Access Machines via VNC: Difference between revisions

← Older edit

ReleaseEngineering/How To/Access Machines via VNC (view source)

Revision as of 16:25, 6 August 2018

287 bytes added , 6 August 2018

noted that RealVNC can connect to standard apple vnc now without "legacy VNC" setting.

Dhouse

32

edits

@@ Line 25: / Line 25: @@
 === Connecting from a Linux client ===
-Remmina Desktop Client and xtightvncviewer have been tested as a Linux client that managed to connect to Mountain Lion. Other versions have not been tested.
+'''To Mountain-Lion:'''
+Remmina Desktop Client and xtightvncviewer have been tested as a Linux client that managed to connect to Mountain Lion.
 * [jmaher] - Remmina would connect and then terminate immediately for me, I ended up getting in with xtightvncviewer (the first try had a keychain issue, the second try worked)
+'''To Yosemite+:'''
+* [dhouse] - RealVNC is now able to connect to Apple's VNC without turning on the "legacy VNC" password only auth (See https://serverfault.com/a/897156). I was able to connect through the jumphosts (corp and rejh) with RealVNC 6.18, from linux 4.14.57, to OSX yosemite without problems.
-For Linux clients, you will have to enable "legacy VNC" instead of Mac's version before you can connect as well as setting the password.
+For other Linux clients, you will have to enable "legacy VNC", instead of Apple's authentication, as well as setting the password. See the section "Enable legacy VNC and set the password". Once you run those commands you will be able to VNC and you will have to use your cltbld credentials. You might have to connect a second time for the connection to stick.
-See the section "Enable legacy VNC and set the password".
-Once you run those commands you will be able to VNC and you will have to use your cltbld credentials. You might have to connect a second time for the connection to stick.
 === Connecting from a Windows client ===