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
Backup DC
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Chris Radcliffe
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5187
People Online:
Visitors:
364
Members:
0
Total:
364
Online Now:
New Topics
S3 Customization/Development
Cobol - Extract Current Time
4/24/2024 7:21 PM
How do you extract just the Current System Time in
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
Lawson Business Intelligence/Reporting/Crystal
Domain Name Change
3/5/2024 7:45 PM
Our domain name needs to change and was hoping I c
S3 Customization/Development
Cobol calling Shell Script
2/29/2024 1:27 PM
Has anyone created or modified a Lawson Cobol prog
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1351
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Systems Administration
Backup DC
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
MattD
Veteran Member
Posts: 94
9/1/2010 6:08 PM
Can the Lawson LDAP bind be configured to point at two domain controllers? We have a separate DC at our backup facility, but if the primary DC goes down we are out of luck because our system is bound to the one DC.
Any ideas?
Thanks.
Rod
Basic Member
Posts: 10
11/30/2010 10:56 PM
I know this is an older question and not sure if you have figured this out yet or not but what we did is bind to an alias name set up in DNS.
So when our directory server goes down, we just re-direct the alias in DNS to point to our other directory server.
This would only cause a minor service interruption.
Hope it helps.
John Henley
Senior Member
Posts: 3348
11/30/2010 11:55 PM
Actually, I discovered from a client that the trick is to bind to the domain name rather than a specific server. =
EricS
Veteran Member
Posts: 80
12/1/2010 12:31 PM
Depending on the versions of the various parts, binding to the domain name may not work out so well. We are on 9.0.0.4 and they just upgraded the domain servers to Win 2008 R2. That combination is not supported by Lawson, but does seem to work. We were, obviously, very concerned about adding in the new servers and getting them to work. That actually went rather smoothly. When we took the old ones out of service, however, SSO would not connect properly. We started having all sorts of errors. Same happened when one went down for an extended maintenance period. GSC recommended that you connect to only one domain server. We decided that the risk of one server being down and having authentication problems was less than the risk of any of 4 servers being down and having authentication problems. Just our opnion.
John Henley
Senior Member
Posts: 3348
12/1/2010 1:25 PM
Binding to the domain name does not provide any active failover. You do need to manage the DNS entries in AD if you take a domain controller out of service, as well as flush DNS on the Lawson server, and stop/start Lawson services. It's just a convenience.
Kwane McNeal
Veteran Member
Posts: 479
12/1/2010 2:44 PM
That's not entirely accurate. You DO get failover, IF you understand how AD server roles work.
IF you bind to the domain name ON THE STANDARD LDAP ports (389/636), then you do NOT get failover.
IF you bind to the Global Catalog ports (3268/3269), you not only get failover (so long as a server has the FSMO for the Global Catalog).
An additional advantage is if you have multiple domains, since a GC provides a readonly copy of the ENTIRE AD, you avoid referral/redirection calls, making authenticating much faster.
The downsides are this isn't possible in an AD forest with exactly ONE DC (and you SHOULD NEVER have that issue in ANY organization), and you can't control which DC gets hit, which can be an issue if the DC isn't in the same network segment as the lawson app server, due to latency.
Also, for anyone that knows AD, might consider binding to the pseudo group gc._msdcs.[
DnsForestName
]
. Don't think about it, UNLESS you are willing to disable DNS Caching (which SHOULD be done on ALL Windows-based Lawson servers, or none of this matters...)
Kwane
You are not authorized to post a reply.