[cpac]

So my lawschool just upgraded their exchange servers to 2003, which is nice because it allows iSync to actually work with exchange in the way it's supposed to (at least it seems to be working).

However, this broke the LDAP setup I had in Address Book from before the upgrade. I used to connect on Port 400, and things worked, but it doesn't work now.

Anybody know what the best way get an LDAP connection to an Exchange 2003 server is?

[Art Vandelay]

You'll need to check with your admins for the appropriate info. However, the standard port for LDAP is 389 and is what our Exchange servers are set to.

[gorickey]

I used this:

AddressX 1.1

[cpac]

ok thanks - i've sent them an email, but they tend to be a little windows-centric.

I did do a port scan on the exchange server, and the only open ports between 300 and 600 were 443 (https) and 464 (kpasswd) - anybody know what this second one is?

[cpac]

Originally posted by gorickey:
I used this:

AddressX 1.1

Thanks - looks somewhat interesting but I really don't need everybody in the school's email address in my own Add book. I just want to be able to have it auto-complete, etc. (and I can always drag names from the ldap search into the address book itself to create a new card).

[Art Vandelay]

Originally posted by cpac:
ok thanks - i've sent them an email, but they tend to be a little windows-centric.

I did do a port scan on the exchange server, and the only open ports between 300 and 600 were 443 (https) and 464 (kpasswd) - anybody know what this second one is?

You can also check port 636. That is the port for LDAP over SSL. Also check to see if you need to authenticate. The userid might be of this format:

username@fully_qualified_domain_name

[cpac]

Ok it looks like Port 636 is open.

So I check the little SSL thing and entered my user id (tried both fully qualified and not) along with my password.

Still no dice--I get 0 results when searching in that directory for "c." (or anything else for that matter)

Since they just changed the server, is there any chance this is just something that has not yet been converted/set up on their end? -- i.e. is there any way for me to check whether the problem is in communicating with their server, or if it's just that the server is giving me no results?

[gorickey]

Originally posted by cpac:
Thanks - looks somewhat interesting but I really don't need everybody in the school's email address in my own Add book. I just want to be able to have it auto-complete, etc. (and I can always drag names from the ldap search into the address book itself to create a new card).

Yeah, I just created a new Group in Address Book and called it good...doesn't interfere with my personal set-up at all and allows me to have auto-complete. Plus, I can just delete the ones I don't want...

[Art Vandelay]

Originally posted by cpac:
Ok it looks like Port 636 is open.

So I check the little SSL thing and entered my user id (tried both fully qualified and not) along with my password.

Still no dice--I get 0 results when searching in that directory for "c." (or anything else for that matter)

Since they just changed the server, is there any chance this is just something that has not yet been converted/set up on their end? -- i.e. is there any way for me to check whether the problem is in communicating with their server, or if it's just that the server is giving me no results?

You really need to get the info from them. There are too many variables to try to guess it. If the server is live and being used for Exchange, then LDAP is setup too since it's the same database. The best thing to do to avoid confusing them with a Mac issue, is just request the necessary info for an LDAP client to connect to the GAL (global address list). This eliminates any Mac-isms from the issue which many admins freak out over. Namely, you need the server address, port number, search base, and authentication scheme for LDAP connections.

[cpac]

ok, sounds good. I just have to wait on them, then.

Thanks for all your help (both Art & gorickey)