0
1
I have OS X Server installed on a mac mini. I've created several User accounts, one of which is
Account Name: Bob
Password: abc123
From the Mac Mini's login screen I can choose "Server" (main account) "Bob" (Bobs account) and "Other..." OS X Server Accounts, from "Other..." if I input Bobs credentials it will log me in.
I also have a macbook air, I would like to be able to select from the Login Screen "Other..." input Bobs credentials and have it login to Bobs account, or any other User Account for that matter.
My Server is setup as private with the server address: server.network.private
Following some googled instructions as well as apples very own instructions I have:
Setup an Open Directory with Username: diradmin Password: abc123
Then on the macbook air gone into
System Preferences > Users & Groups > Login Options
and clicked Join
next to Network Account Server, input my server (server.network.private) with diradmin credentials and its connected. Great.
I've also ticked Allow Network Users to Login and Login Window
and selected All Users.
I was assuming this would allow my macbook air to login to the "Bob" account by selecting "Other..." from the login window although there is no "Other..." option.
I then setup a VPN, basic credentials, logged into it on the macbook air and still not much has changed. I am able to share screens with the "Bob" account form my macbook air by logging in by clicking Share Screen...
from the Finder under Shared > Network Server
and then clicking Login In
but this obviously requires the macbook air to already be logged into an account before it can share screens which is not suitable.
Is there any way to simply login to the OS X Server User Account from the macbook air's login screen via the "Other..." like it does on the mac mini's login screen?
Thanks in advance.
Operating System: OS X 10.9 Mavericks
OS X Server: Version 3
I had same problem, and all works beside step 7. But after reading this page, https://wikispaces.psu.edu/display/clcmaclinuxwikipublic/Mountain+Lion+Authentication+Configuration, I found out with kinit that the client machine was using wrong hostname. After reboot of the server and the client, it worked again.
– Jesper Grann Laursen – 2013-11-08T10:45:06.593@Lauer: Interesting; I'm not sure why a Kerberos problem would interfere with password-server-based authentication... I'll add a Kerberos check step just in case. – Gordon Davisson – 2013-11-08T15:53:48.250