LDAP, Netscape Messaging Server And Outlook 2000?

acantu asks: "We are running a Netscape Messaging Server, most of our users are using Netscape Messaging to retrieve their e-mail, but I have a select few that would like to use Outlook 2000, they can receive their e-mail with no problem. However we can configure Directory Service to point to LDAP and when we search for names it does not return anything, even when wild cards are used. I would like some tips if possible." What pitfalls are there when trying to use Outlook with LDAP? Is the problem here in Outlook's implementation, Netscape's, or is this just a simple configuration error?

Schema's

[AliasTheRoot]

I know Exchange 5.5 had a *horrible* LDAP schema, and i'm guessing that this is still the case with Exchange 2k, Netscape's schema is a lot more flexible & pretty much leaves you in charge of how it looks (except for all the config stuff in NetscapeRoot).

As an aside, Outlook Express has no difficulties handling the Schema in Exchange 5.5, but the last time I tried Communicator it wasn't so happy. Not sure about the reciprical situation.

These observations apply to Exchange 5.5 only, I've never used 2000

Re:Schema's

[AliasTheRoot]

doh! you were talking about Outlook 2000 not Exchange... Still, I think the schema issues still apply - does it work in Outlook Express?

see openldap faq

[malice95]

Check out this openldap faq entry [openldap.org] which should give you a lot of detail on what attributes outlook recognizes and netscape recognizes. As normal.. outlook tends to do its own thing instead of following standards closely.

Malice95

Possible

[raymondlowe]

Sure this is possible.

Go to Tool / Services / Add / Microsoft LDAP Directory. Set the properties. The key one is Search Base - depends upon your schema. The default is "c=us". But you might needs to change it, talk to your LDAP administrator

I think this is case sensitive??

R.

Config Problem

[big_groo]

Outlook:
Tools -> Accounts-> Add -> Directory Service

You should see Internet directory (LDAP) server:
now, if you don't know it, go to Netscape (I use 4.5), open you address book, select the directory to want to add to Outlook2k, right click to get the properties. This is the info you'll use to congigure Outlook.

So, for the LDAP: ab1c23.on.company.ca
next:
in Outlook: Tools, Accounts, Directory Service (a tab..), then select the properties.
Click on the Advanced tab. You need to fill out your search base here. You can get the info from your configured Netscape.

So, in the Search base (in outlook2k) type in the info.
eg. ou=ORGANIZATION, ou=people, o=Company, c=ca

Once you've done that, open your address book in Outlook, Edit ->find people, select the new directory that you've added, and voila!

BTW, this is MUCH easier to configure in Netscape. Welcome to Micro$oft.

If anyone has an easier way, let me know.

Re:Config Problem

[big_groo]

Nice spelling. *sheesh*

Re:Schema's

[Carey]

Exchange 5.5 does not have an LDAP schema.

Exchange 5.5 SP3 implements the ADSI (Active Directory Interface), which allows Exchange to be queried by LDAP-compliant clients.

The schema is only the set of attributes in the Exchange database of objects that are exposed through the ADSI.

Regardless (and although the MS implementation is a little weird) it is well documented and you can query Exchange with LDAP clients to support addressing for Exchange server users without an Outlook MAPI client.

You can also use a meta-directory to synchronize from an LDAP server to the Exchange server. It is especially useful for custom recipients.

Check your logs

[Carey]

You should check your LDAP server access log to ensure that your Outlook clients are actually querying the directory server.

There should either be an access code or an error code. The LDAP error code you can debug if there is an issue, but most likely you have the base distinguished name (DN) misconfigured or something like that.

Are your Outlook 2000 clients running on Windows 2000 or something else? I've heard a couple things that may be issues with the way Outlook 2000 running on Windows 2000 handles LDAP lookups vs an older Windows platform.

Just doing simple searches is easy

[anacron]

The real trick is using LDAP to do single signon for both workstations, email accounts, corporate websites, etc. The breakdown occurs because the windows domain doesn't really want to sync with LDAP unless you install active directory and make it the de facto LDAP server. Of course when you install active directory for this, it also wants to be your DNS/DHCP/etc servers. Muck Ficrosoft.

If you want to run Netscape LDAP server or some Linux servers to do basic network services, you're going to need to find a utility that pushes data (on change) to the microsoft domain.

We've gotten single sign-on to work here, but it took a bit of effort and some really dedicated sys admins. So now we can use the same login/password for our desktops, our email account, and our corporate websites, all without having to manage more than one LDAP tree. I highly suggest this method as it can both cut administrative costs (by reducing the sheer amount of information), remove the microsoft takeover of your network, and increase job security (by making sure that you're the only one who knows how to maintain everything. ;)

anacron

Re:Just doing simple searches is easy

[rmerrill11]

Anacron,
Are you interested in doing some consulting about setting up a similar system at anotehr company?
Please contact me at
r m e r r i l l@ NoSPAM cal.net