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

mavericks network accounts unavailable

I've set up a brand new OD on a mac mini and all seems fine but I tried adding a new imac to it and while it says it's bound to OD network accounts do not work.


I've done a destroy and recreate of OD and a rebind with no luck both machines on 10.9 latest mini running server 3.1.1


Mini uses ethernet attached to apple airport extreme and imac is wifi.


Any ideas here as it says in the login preference pane on the imac a green light and active.


Thanks

Mac mini (Late 2012), OS X Mavericks (10.9), Mavericks Server

Posted on Mar 27, 2014 5:14 PM

Reply
Question marked as Best reply

Posted on Mar 27, 2014 6:08 PM

Many, if not most, OD 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. 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.

3. Verify that the master's hostname matches its domain name by running the shell command

sudo changeip -checkhostname

The name must not be in the ".local" top-level domain, which is reserved for Bonjour.

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.

4 replies
Question marked as Best reply

Mar 27, 2014 6:08 PM in response to mattd25

Many, if not most, OD 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. 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.

3. Verify that the master's hostname matches its domain name by running the shell command

sudo changeip -checkhostname

The name must not be in the ".local" top-level domain, which is reserved for Bonjour.

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.

Mar 28, 2014 12:49 AM in response to Linc Davis

The network is set to use the local network and appends the .local to the hostname automatically during the setup process, the DNS service remains turned off too.


Also if I set the master to just 127.0.0.1 then it loses the internet connection.


My server is setup as the following :-


IP 10.0.1.3

subnet 255.255.255.0

Router 10.0.1.1

DNS 127.0.0.1 10.0.1.1

search domain cable.virginemedia.net


Primary address = 10.0.1.3


Current HostName = mini-server.local


The DNS hostname is not available, please repair DNS and re-run this tool.


dirserv:success = "success"



When I installed the server 3.1.1 and ran the setup for OD it never asked me for DNS or enabled it, is this a bug since there are no configuration zone files in there either etc where as I remember vesion 3 did this without an issue and I would have thought that on a clean setup like this both from scratchthis would be standard ?



Client setup :-


Dynamic IP 10.0.0.*

Subnet 255.255.25..0

Router 10.0.1.1

DNS 10.0.1.1

search domain cable.virginemedia.net


The iMac says that the OD server is running and gives a green light showing all connetions are functioning too.

Mar 28, 2014 10:56 AM in response to Linc Davis

Would you believe that this is actually what I thought all along but what i didnt realise is that in server 3 this is not automated where as it was in previous versions so assumed it wasnt meant to be used :/


Thanks Apple lol ... well it seems to be working now although there are a few DNS issues now which I have opened a new threat for many thanks for the tip Linc !

mavericks network accounts unavailable

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