The title of this hint should be changed to:

Allow Address Book to connect to ActiveDirectory servers

[ Reply to This | # ]

That's weird... I have AD LDAP integration using port 389. For Search Base I have: cn=Users,dc=domain,dc=com and for username: jim@domain.com

It's been working fine for me that way for a long time.

[ Reply to This | # ]

Umm - actually there's a few subtleties in there. Port 389 will respond happily to LDAP queries, however, if you're working in a multi-domain forest port 3289 will respond to Global Catalog queries, thus including responses from other domains outside of your local domain. Port 389 will still work just fine in most instances.

And for the authentication, you can enter the ID in any case you like. I cringe to add this link here, but it's always better to have the right info. http://www.windowsitlibrary.com/Content/716/06/4.html

[ Reply to This | # ]

For those interested in getting LDAP runing on OSX and use it to share contact information take a look at AddressBook4LDAP. Address Book X LDAP transfers contact in the background to a central LDAP directory. The manual also contains instructions on getting LDAP (OpenLDAP) running and configured on OS X and OS X server. Currently you can still download the software for free :-)

[ Reply to This | # ]

From Address Book Help:

If your computer is set up to access directory services on your network, Address Book automatically searches the directory services for addresses.

So Address Book should see the contacts in Active Directory if you have the computer bound to the Active Directory domain by means of the Directory Access application, making sure to specify that the domain should be used for contacts.

[ Reply to This | # ]

How do I figure out where the directory server is? I can connect to the exchange server through entourage, but I've never figured out how to identify the directory server. Putting the exchange server's name in as the LDAP server just gives me a "cannot connect" error.

---
Everyone loves a clown, but no one will lend him money!

[ Reply to This | # ]

Typically LDAP service should be available on domain controller of your network; ask admin or windows co-workers how it's named.

And of course the login should be DOMAIN\USERNAME with backslash in the middle; it got lost in the original post somehow (((

[ Reply to This | # ]

okay, thanks.

---
Everyone loves a clown, but no one will lend him money!

[ Reply to This | # ]

Here is what I found to use in Leopard to connect to Windows 2003

Name: Anything as this is just a description

Server: The FQDN of the server i.e. myserver.depicus.com

Port: I used SSL so mine was 636, use the Port Scanner to check if this port is open

Use SSL: Ticked

Allow SS Cert: Ticked

Search Base: cn=Users,dc=depicus,dc=com

Scope: Subtree

Auth: Simple

Username: Domain name in CAPS \ username i.e. DOMAIN\Brian

Password: Your password

Hope this helps somebody.

[ Reply to This | # ]