Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
LDAP Bind to AD Breaks With New Domain Controller
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
56
Members:
0
Total:
56
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Infor / Lawson Platforms
S3 Systems Administration
LDAP Bind to AD Breaks With New Domain Controller
Please
login
to post a reply.
4 Replies
0
Subscribed to this topic
29 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Bil
New Member
Posts: 2
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
New Poster
Congrats on posting!
2/17/2011 5:18 PM
Split
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
2/17/2011 5:38 PM
Split
We are specifying port 389. I hope the fix is that simple... File attched. Thanks.
Attachments
LoginService.txt
John Henley
Posts: 3366
New Poster
Congrats on posting!
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader art thou!
2/17/2011 6:01 PM
Split
After you change the ldapbind, make sure you reboot before trying your test. =
Jimmy Chiu
Veteran Member
Posts: 641
New Poster
Congrats on posting!
2/18/2011 4:48 PM
Split
Bind to the new GC via 3268 should solve the problem assuming your AD team did their job correctly.
Please
login
to post a reply.