L-Space Design Forums

I also bought LDAP, but having problems.

SERVER.DOMAIN.LOCAL/DC=domain,DC=local

I am inputting svr1.mydomain.com/DC=mydomain,DC=com

But I don’t get anything

If I put

svr1/DC=mydomain,DC=local

Then I get User not authenticated: A referral was returned from the server

But my domain is mydomain.com not mydomain.local

AD/LDAP entry is CN=svr1 DC=mydomain and DC=com – I have a few other devices (prints and phones) using LDAP fine.

The Webserver is not on a Domain controller but on same subnet / network

I am using mydomain\username and password.

When i put svr1/DC=mydomain,DC=com with out username and password, i get User not authenticated: The parameter is incorrect

Then if i use the same thing and put username and password, i get There were no results returned.

Ok.

With the username and password options, you have a valid connection.

Have you added any entries into 'Groups'?

Glad to hear it.

One tip if you are adding users.  It can be very difficult to identify 'real' people as opposed to server accounts as they both are 'user' and 'person' in the Active Directory.

One good method is to add (sn=*) to the group query, that eliminates any accounts where the surname has not been added.

Have to amend this.  I've now found circumstances where even though a user object has a valid sn attribute, they are still not returned when filtering by (sn=*).  A shame that.

Hi Ed.

So you have put in a server, user name and password.

When you press 'Test', you don't get an error message, but do see

'No results were returned'

The details you indicate above should work.

Possible causes are:

• User name should be abc\user  not abc/user
• Use just the server name (w2k3srv1) instead of including the DC syntax
• The user account you have specified does not have read permission for the objects

If changing the server name works, it indicates that the LDAP node you are requesting by including the DC syntax either does not exist, or that there are no users within it.  You will need to use something like the Softerra LDAP Browser or Active Directory Users And Computers tool to look up the distinguished name of the root node.

If changing the user account to an Administrative account works, it indicates that the account you were using does not have read privileges in the AD, and you will need to use another (hopefully non-administrative) account.

If it works with

Hmm, haven't seen that error before.

Could you take a screen shot and post it for me?

Thanks.

Roger

Thanks Ed.

Hope we're all sorted now.