Open directory

Question

I know that this is discussed in more threads but have not found anything that helped me. I have set up a server name Home.private and managed to connect my macbook air with the server and have a green light. I have set up DNS on client and server so this is right (I have done som reading). When I log in, I see the "network account not available". I've read around and tried everything. The last I found was to look in the password log on OD and sure enough, I see something strange there.
6 2014 19:08:55 792872us Registration is finished error: (10, -72 000).
6 Jul 2014 20:51:34 432090us Registration is finished error: (10, -72 000).
6 Jul 2014 20:51:35 174808us Registration is finished error: (10, -72 000).
6 Jul 2014 23:42:01 408301us Registration is finished error: (10, -72 000).
6 Jul 2014 23:42:01 408459us Registration is finished error: (10, -72 000).
7 Jul 2014 20:01:27 693907us Registration is finished error: (10, -72 000).
7 Jul 2014 20:01:27 786271us Registration is finished error: (10, -72 000).
What does this mean and can it be the problem?

Answer 1

Many 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. As a last resort, export all OD users. In the Open Directory pane of Server, delete the OD server. Then recreate it and import the users. Ensure that the UID's are in the 1001+ range.