LDAP NamingException

[rems]

Hi Dear community !

I'm facing this error message in my LDAPS log message   :

any ideas ?

Validation failed for CN=Dorothee XXXX,OU=Users,OU=YYYYY,OU=FFF,OU=Corp,DC=ZZZZZ,DC=net - NamingException 194.0.0.0:636

thanks in advance

[Bhavesh Jain1]

Is there any special character in the userID of the user ?

[rems]

No..

I opened also a ticket in HI, will keep this thread up to date with the info the gives me .

thx for your support

[rems · Accepted solution]

According to Hi,

This happend when LDAP server respond is too slow, due to performance reasons (especially with SSL LDAPs)

usually this message comes with 'LDAP read timeout' in the logs

[Ben Wilcox1]

I know this is an older post, but I came across this issues myself today and found a connection between the LDAP log error "Validation failed for..." and the status of the AD account.  In the case I reviewed today, the AD account that triggered this error was not locked or disabled or moved to a different OU.  The trouble was the user was 16 hours past the 90 day password age window for their AD account.  Until they reset their AD password, their AD account is useless for pretty much anything.  I use the free tool from Microsoft:  LockoutStatus.exe to quickly determine AD password age.  It's been a lifesaver many times in revealing this to be the cause of a number of login issues for ServiceNow.