I am still unfamiliar in configuring LDAP authentication. I read the manual about this but still I am confused. Can you give some hints about configuring LDAP authentication.Thanks!
-
-
Re: LDAP authentication
Yesterday I configured one machine model MP2501sp using LDAP. Entered LDAP server settings, do connection test and it was successul. When I go to scanning function, search the email of the user, it says "FAILED TO CONNECT WITH LDAP SERVER.Do you have any idea why it is happening? -
Re: LDAP authentication
I don't know if it applies, but the following is from the Global Knowledge Base. Hope it helps.
Device successfully connects to an LDAP server once but fails on subsequent attempts
Published 08/12/2011 02:58 AM | Updated 08/12/2011 02:58 AM
Answer ID 141140 | FAQ ID 140538 | Rank A0
The device successfully connects to an LDAP server once. All subsequent attempts will fail. Why is this happening?
The device is configured to use LDAP Authentication with "Authentication = High Security". The device will successfully establish a connection with the LDAP server once, but will not be able to do so again until rebooted.
This will only occur if all of the below conditions are met:
- Windows 2003 Server is being used as the LDAP server.
- User Authentication = LDAP
- The device's "LDAP > Authentication" setting = "High Security".
- The device has not been rebooted since the last connection attempt.
If the device's LDAP server setting is configured as "Authentication = High Security" and if the LDAP server supports it, SASL with a Digest-MD5 challenge/response will be used to authenticate the device when it connects to the LDAP server.
The problem is that the device stores the LDAP server's challenge. This is done to save time. It allows the device to connect by sending the response (without waiting for the challenge). This is called "subsequent authentication" and is valid as explained in RFC 2831.
Server's that don't support subsequent authentication are supposed to inform the device and resend the challenge. However Windows 2003 servers don't do this. Instead they just terminate the connection. This is the cause of the problem.
As this only affects older devices, a permanent fix is not going to be released. Newer devices have already been fixed.
As a workaround, configure "Authentication = On" with "SSL = On" instead of using "Authentication = High Security".
Doing this will provide a similar level of security but will use SSL instead of SASL.Comment
-
Re: LDAP authentication
The problem is solved. We just corrected the following settings as shown in the picture.I can sleep good now! Cheers!cn1 (1).jpgcn1 (2).jpgComment
Comment