Prev
Next
Forums S3 Systems Administration

LDAP Bind to AD Breaks With New Domain Controller

Sort:
You are not authorized to post a reply.
Author
Messages
Bil
New Member
Posts: 2
New Member
2/17/2011 5:10 PM
    We are using LSF 9 on Windows with ADAM as our LDAP provider. We have the LDAPBIND set up (to Active Directory) and working correctly for Lawson single sign-on.  Our network team is currently updating our Active Directory infrastructure with new hardware that will eventually be able to run AD 2008.  In Lawson, I can successfully change the LDAPBIND to use one of the new domain controllers.  However, when we power off the old domain controller that was specified in our LDAPBIND, users are unable to log into Lawson.  They get an "incorrect user name/password" error. Does anyone know where the old domain controller information would be stored other than in the ldapbind?

    Thanks.
    Jimmy Chiu
    Veteran Member
    Posts: 641
    Veteran Member
    2/17/2011 5:18 PM
      Are you binding to the new GC via port 3268

      post your xml backup file it created when you run ldapbind also. Blank out the sensitive data.
      Bil
      New Member
      Posts: 2
      New Member
      2/17/2011 5:38 PM
        We are specifying port 389.  I hope the fix is that simple...  File attched.  Thanks.
        Attachments
        John Henley
        Senior Member
        Posts: 3348
        Senior Member
        2/17/2011 6:01 PM
          After you change the ldapbind, make sure you reboot before trying your test. =
          Thanks for using the LawsonGuru.com forums!
          John
          Jimmy Chiu
          Veteran Member
          Posts: 641
          Veteran Member
          2/18/2011 4:48 PM
            Bind to the new GC via 3268 should solve the problem assuming your AD team did their job correctly.
            You are not authorized to post a reply.