Topic: LDAP not working om 6b3

[Dennis]

I cant't get LDAP working on my sme 6 beta3.
In the server-manager i should see a line like dn=home,dn=com.
There is no line like that.

Is there a patch to resolve this?

A sad sme user

[Chris]

I too am having this problem also i cant  get the user manager to work. I keep getting
Authorization Required
This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.

Any ideas?

[Bob King]

The LDAP Server root settings do not show up in server-manager on my 6b3 test server either however the dc settings are only your server domain name.

example 1
If your domain is foobar.com then dc=foobar,dc=com

example 2
If your domain is foo.bar.net then dc=foo,dc-bar,dc=net

I just tested these settings using Outlook 2000 on a Win2K Pro machine against my SME 6b3 test server with the latest updates.

[Dennis]

I tried it but outlook (2003) can't access my sme server.
The message outlook gave is: Illigal Syntaxis from DN (34).

I have Windows XP SP1 with Office 2003.

My sme server domain name should be dc=dwsoft,dc=net.
In the example there is also cn=users mentioned.
Is this important or can i do without?

[Bob King]

It appears that Outlook 2003 is looking for a LDPAv3 server. I am not sure but believe that SME may be using LDPAv2. There are a lot of differences between v2 and v3. Maybe someone from Mitel can enlighten us as to what version of LDPA SME is using.

From http://www.faqs.org/rfcs/rfc3494.html RFC 3494 - Lightweight Directory Access Protocol version 2 (LDAPv2) to Historic Status (March 2003).

"Recommendations

Developers should not implement LDAPv2 per RFC 1777 , as such would result in an implementation that will not interoperate with existing LDAPv2 implementations. Developers should implement LDAPv3 instead. Deployers should recognize that significant interoperability issues exist between current LDAPv2 implementations. LDAPv3 is clearly technically superior to LDAPv2 and hence should be used instead."

Details about LDPAv3 can be found here: http://www.faqs.org/rfcs/rfc3377.html

From http://www.faqs.org/rfcs/rfc2251.html some LDPAv3 error codes.

"Most of the result codes are based on problem indications from X.511 error data types. Result ... codes 32, 33, 34 and 36 indicate a NameProblem, ...."