Changes

Jump to: navigation, search

ReleaseEngineering/How To/Access Machines via VNC

266 bytes added, 15:08, 15 July 2015
no edit summary
'''NOTE: This is a draft.'''<br />'''NOTE2: From these notes we should create steps to setup {{Release Engineering How To|Access Machines via VNC for developers'''<br />}}= Password =It lives in slave-passwords.txt.gpg__TOC__
= Windows For developers =It works right away.
When a machine is moved to a loaner_ou (organizational unit) it sets a default password for the loan== Windows loaners =="It should just work."™
= Linux (Ubuntu ) loaners =
VNC is not running by default.
ssh as root and run this:
start x11vnc
 == Mac OS X === How to connect loaners ===== From Connecting from a Mac client ==='''NOTE* Use [http: Do not use //sourceforge.net/projects/chicken/ Chicken of the VNC (CotVNC)]. This is preferred over other clients (and even over Apple's Remote Desktop unless necessary; Use Chicken) because it'''* Use Chickens known to work.
* Use the FQDN, e.g: vnc://talos-r4-snow-001.build.mozilla.org
=== From 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.
* [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)
**
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.
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.
=== From Connecting from a Windows client ===
TightVNC has been tested by Honza to work to connect from Windows to a Mountain Lion releng machine.
Honza has determined that real VNC free is faulty.
== VNC status asOS X version-is specific notes ==
Each of our Mac versions have slight differences with regards as to which user to login with once you have VNC'ed into the machine.
=== Mac OS X 10.10 - Yosemite ===
Use the Builder user from the account selection screen. Because of the password change that happens as part of the loaner process, you may see keychain verification dialogs unless the person on buildduty clears these for you before handing over the loan.
 
= For releng =
 
== Password ==
It lives in slave-passwords.txt.gpg
== Setup for loaning ==
'''NOTE: Please add notes once you figure it out.'''
 
=== Windows ===
Moving the machine to the loaner OU takes care of everything.
 
=== Linux ===
Just change the connection password in /etc/vnc_passwdfile, as per the [[ReleaseEngineering/How_To/Loan_a_Slave|slave loan instructions]].
=== Mac OS X 10.6 - Snow Leopard ===
</pre>
== FAQ ==
Q: I'm trying to connect from Linux with Remmina Desktop to a Mac machine but when I connect I get kicked out immediately (I see a window pop up for a second and then goes away) <br />
A: Try changing the color setings (256 colors was causing this for armenzg) <br /><br />
Canmove, confirm
2,850
edits

Navigation menu