LDAP Bind issue

 1 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Joe O'Toole
Veteran Member
Posts: 314
Veteran Member

    After performing our LDAP bind for our LSF9 system, certain users are failing the smoketest (most importantly the Lawson account). Some of our Windows accounts including Lawson are quite old and were migrated into AD from our old NT user repository. It seems that the newer accounts smoketest ok so we're wondering if this is the common denominator. Has anyone experienced this and could there be some indexing issue with the older records that is causing the authentication / AD lookup request to fail? If this is the cause we're thinking that deleting and re-adding the account will update the index in AD properly. We are not at liberty to try this with the Lawson account as the risk is too great. It is also in use by our production 8.03 system and we do not know if either the the 8.03 or LSF 9 instances have some internal tie to the orignial Lawson accounts SAM. If it does the newly created account might stop functioning properly with obvious repercussions. Thanks for any suggestions.

    John Henley
    Posts: 3353
      That sounds a little drastic, and I'd expect that you'd be having other AD-related problems.
      Are you binding on sAMAccountName?
      Are the old and new accounts are in different trees/branches?
      Are you sure the AD query user you specified in ldapbind has access to query those accounts?
      Are you sure you used the correct "search base"?
      Thanks for using the LawsonGuru.com forums!
      John