Connection failed to the directory server. (2100)

Hello,

although it is an old discussion and many answers have been provided, I stumbled on the exact same problem under Server 3 (under Mavericks) and solved in a way that hasn't be illustrated here (?).

I realized that the IP address indicated under the servername in the Open Directory tab in Server was wrong. I checked with the following command line:

# sudo serveradmin settings dirserv

....

dirserv:treeConfiguration:odTree:_array_index:0:IPaddresses:_array_index:0 = "192.168.1.53"

....

whereas the correct ip address is 192.168.1.30. I then executed the following command:

# sudo changeip 192.168.1.53 192.168.1.30

checked that it worked:

# sudo serveradmin settings dirserv

....

dirserv:treeConfiguration:odTree:_array_index:0:IPaddresses:_array_index:0 = "192.168.1.30"

....

And since then, no more 2100 error ;-)

Note that before doing this, the "sudo changeip -checkhostname" command *was* successful. So even if it is for you, you may still try the "sudo changeip <old_ip> <new_ip>" trick.

Good luck.

This helped me with this same error.

Check your Keychains and the SERVER CERTIFICATE for the server you are trying to connect to ON the client side machines to make sure they have not expired...AND make sure the SERVER Certificate on the SERVER is selected for ALL services.

Check the System Prefs/Network - DNS entries of each of the connections like VPN or ETHERNET or WIFI and make sure they have the STATIC IP of the server and the server name.

In USERS and GROUPS / Join Network / Directory Utility / You MUST also add the SERVER to the Search Policy/ Authentication / Custom Path..and add your server... once you have added it to the LDAPv3 Service.

This all helped me with finally "binding of the directory" issues.

I had this issue for a while and finally fixed it. I think the issue started because I updated the certificate for my server and the network computers wouldn't grab the new server certificate. Here is all that I did and it fixed the issue.

1. On your server, open up the server app and turn off DNS services for a minute and turn them back on.

2. On the DNS settings tab I removed the name server record that wasn't working and readded it.

After about 5 minutes I was able to connect to the server and it's been working fine ever since!

Hope that helps some of you!

I came across the same issue today.

The issue on my mac was that the clock was more then 5 minutes ahead of the domain controllers clock.

I changed the ntp server of my mac from the apple server to my domain controller. This solved the issue for me