‘Network Accounts Unavailable’ after successfully binding and rebooting.

[joshvogelgesang]

First off, I’ve tried to do my homework, but as of yet, I haven’t found any articles that answer this hopefully simple question.

Here is the situation: I have a created master image that I’ve stripped the LKDC from that I’ve mass duplicated on 32 MacBooks. On their first boot, the machine gets renamed to its new network name, a new LKDC is setup, and it reboots. Then, it is joined to one of the Open Directory server at its destination site, and bound. Everything is green across the board. It reboots, I test each one to make sure network accounts are working, and its sent off to the user.

Its been working pretty decently. But, one machine (jm-cart21-31) had a hiccup, and once it reboots after being bound, you cannot log in under a network account (Network Accounts Unavailable). The Directory Utility says that there is no response from the server, but I can ping it just fine and other computers still are happy as clams.

So, I decided I’d start over on that one, deleted its OpenDirectory entry, and started over. Same results – UNTIL I renamed it and joined as something else (jm-cart21-32) and bound. And it works without a hitch. So, I take another one, follow the whole procedure over again, and still, I can bind as jm-cart21-31, but once rebooted, it just shows the Network Accounts Unavailable.

I looked at the logs, and nothing is really telling, save for an entry that keeps coming up ‘Couldn’t find KerberosClient config record’. I can guess what that is, but I don’t know how to solve it – or if its related to my problem.

Thanks in advance!

– Josh

[joshvogelgesang]

I have it set to Enable authenticated directory binding, but the option to Require authenticated binding between directory and clients is not active.

When I bind the machine to the directory, I’m entering the diradmin account… Am I following you correctly?

– Josh

[Author]

Posts