I just recently setup our Mac OS 10.2 server utilizing our Active Directory server. Here are some tips that may help.
1) Do not test with OS X Server. I used the Java LDAP browser, available at http://www.iit.edu/~gawojar/ldap/ to check for a proper connection. Once I got this to work where I could see the LDAP user data, I plugged those same settings (User/Password, search base, IP, etc) into Directory Access for OS X Server. OS X Server does not give as much diagnostic feedback when testing as the LDAP browser does.
2) Do not add a cn=Users to the search base. Yes it may be necessary, but OS X Server will do this for you. By adding it, you will have 2 cn=Users which breaks it. The search base should look something like dc=mydept,dc=mycompany,dc=com.
3) In Directory Access use the Active Directory template (not From Server, or Custom). In most cases this will work without any mappings making it a simple Directory Access setup.
Slashdot Mirror
I just recently setup our Mac OS 10.2 server utilizing our Active Directory server. Here are some tips that may help.
1) Do not test with OS X Server. I used the Java LDAP browser, available at http://www.iit.edu/~gawojar/ldap/ to check for a proper connection. Once I got this to work where I could see the LDAP user data, I plugged those same settings (User/Password, search base, IP, etc) into Directory Access for OS X Server. OS X Server does not give as much diagnostic feedback when testing as the LDAP browser does.
2) Do not add a cn=Users to the search base. Yes it may be necessary, but OS X Server will do this for you. By adding it, you will have 2 cn=Users which breaks it. The search base should look something like dc=mydept,dc=mycompany,dc=com.
3) In Directory Access use the Active Directory template (not From Server, or Custom). In most cases this will work without any mappings making it a simple Directory Access setup.
Hope this helps
Rik