[marcelborsten]

The client will first look in the local NetInfo database to find the user. As you can see in Directory Access, it will always first look local. So when you try an account thats on the server and local, the client finds the account local first, then tries to authenticate and fails with that because its the wrong password. Its will not keep looking on in OD, because it had already found the account in NetInfo.
Try to use different shortnames on the server, or backup and remove the account from the client.

[marcelborsten]

I’ve gotten a bit furder: the binding doesnt seem to break, it just takes a lot longer. After a restart it takes about 10 minutes before the server can read in the AD datatbase.

As for your reply; yes, the AD is in the search path (at the top) in Directory Acces.

I dont mind the server taking 10 minutes before being able to authenticate (let hope that server reboots will be a rare thing), but if i want the clients to start Authenticating with AD those 10 minutes will be very long for all the users

[Author]

Posts