Lawson Portal and AD (Windows 2008)

Welcome to LawsonTalk. We hope you enjoy your visit.

You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free. After registration, please check your e-mail within 24 hours for an message from us, read it, and reply to it.

Join our community!

If you're already a member please log in to your account to access all of our features:

Lawson Portal and AD (Windows 2008); Active Directory
Topic Started: Dec 7 2009, 06:09 AM (141 Views)
mh53j_fe	Dec 7 2009, 06:09 AM Post #1
Newbie Posts: 6 Group: Members Member #10,810 Joined: October 1, 2008	We are at Lawson version 9.0.0.4.584 Users authenticate against Active Directory to access Lawson portal. Last week, our Operations group updated our Active Directory servers to Windows 2008. With the upgrade, the AD server name has changed from actdir1 to itad1. Now, when our users logon to the portal, Lawson hangs up for over 5 minutes before authenticating the user and opening the Portal Administration Home page. We are using LAUA security for LID, and I tried logging in via LID and have not experienced any problems. Has anybody else been experiencing problems with authentication when they switched to Win2008 AD on a new server? When our Lawson consultant installed Lawson 9, did he have to hard code the AD server name? What can I do to troubleshoot this problem. Any help will be highly appreciated. Thanks in advance for your help.



jecraton	Feb 9 2010, 05:29 AM Post #2
Member Posts: 14 Group: Members Member #14,788 Joined: April 27, 2009	Did your system administrator run an LDAP BIND to Active Directory, and if so, what server and port is LAWSON bound to? LDAP queries can travel in one of two ways. If you're bound to port 389 on active directory, that could take a while. The second way is to do an LDAP bind to the global catalog server on port 3268. This is generally a lot faster than queries against port 389, which seem to drag on forever. Try binding your LAWSON environment to the global catalog and you will see a significant boost in your authentication times. Make sure the service is running first (nmap is your friend). Edited by jecraton, Feb 9 2010, 05:29 AM.


« Previous Topic · System Admin · Next Topic »