Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

dscl returns eDSInvalidSession

I am trying to setup Open Directory so the Macs on the network can authenticate centrally. It was working for a while, but now it doesn't.


When I run the dscl command with the authonly flag it returns "Authentication for the node failed. DS Error: -14477 (eDSInvalidSession).


Here's the command:

dscl /LDAPv3/(nodename) -authonly diradmin


The error message is:

Authentication for node /LDAPv3/(nodename) failed. (-14477, eDSInvalidSession)

<dscl_cmd> DS Error: -14477 (eDSInvalidSession)


I have searched for a solution on the Internet, but have not found anything relating to this.


Any ideas?


-Ken

Mac mini, OS X Mavericks (10.9.2)

Posted on Apr 15, 2014 7:34 AM

Reply
8 replies

Apr 17, 2014 11:14 AM in response to k_knowles

Many, if not most, Open Directory problems can be resolved by taking the following steps. Test after each one, and back up all data before making any changes.

1. The OD master must have a static IP address on the local network, not a dynamic address.

2. You must have a working DNS service, and the master's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. On the Accessing your Server sheet, change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour.

3. The primary DNS server used by the master must be 127.0.0.1 (that is, itself) unless you're using another server for internal DNS. The only DNS server set on the clients should be the internal one, which they should get from DHCP if applicable.

4. Follow these instructions to rebuild the Kerberos configuration on the master.

5. If you use authenticated binding, check the validity of the master's certificate. The common name must match the hostname and domain name. Deselecting and then reselecting the certificate in Server.app has been reported to have an effect in some cases.

6. Unbind and then rebind the clients in the Users & Groups preference pane. Use the fully-qualified domain name of the master.

7. Reboot the master and the clients.

8. Don't log in to the server with a network user's account.

9. Export all OD users, delete them, turn off OD, turn it back on, and import. Ensure that the UID's are in the 1001+ range.

dscl returns eDSInvalidSession

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.