Moving to AD/LDS from ADAM

I guess I forgot to say, it just seems that the connection between my environment and the ldap just hangs or drops. We get either profile error upon trying to log in and can't log in at all, or we get logged in and then when you go to a screen and hit inquire, you get "Status 500: The server encountered an unexpected condition that prevented it from fulfilling the request".

Does this always happen after a period of inactivity?=

I had to move back to ADAM and off of Windows 2008. We had the same problem with having sockets drop out to AD LDS and having to restart security. Lawson is aware of it but doesn't know how to fix it. They are aware of six clients (we were one of them) having the same problem with one client figuring it out,  but they won't tell Lawson how to fix it. They gave us three options.

1) Use LPS and have them move AD LDS to Tivolli
2) Open a ticket with Microsoft and include Lawson on the ticket.
3) Move back to ADAM from AD LDS.

I did the third option and moved off of Windows 2008 back to 2003 in addition.

The security connection hasn't dropped out since and that was a month ago.

Our envirnoment
Environment: 9.0.1.8, apps 9.0.1.6, WAS 7.0.0.17, AIX 6.1, Oracle 10.2.0.4

I've been using Windows 2008 ADLDS for my production server for years... and my Windows 2008 R2 ADLDS for my development server been rock solid.

Jimmy,
Do you have user access control disabled.  My windows admin suggested trying that.

Lisa,

For troubleshooting, I would disable UAC + Windows Firewall + any anti-virus you are running on the ADLDS server. Does the password has special characters? IE: $ # @... etc.

I would also look into IBM's Redbooks Integrating AIX into Heterogeneous LDAP Environments for references. http://www.redbooks.ibm.c...tracts/sg247165.html

This sounds crazy, but check the 'power settings' on the LDS server. Windows Server 2008 changed the default so that the server will go into power saving mode when idle. Change it to maximum performance.

Thanks for the suggestions, I will look into them. Also this is a virtual server, so I am not sure if that has anything to do with it. When I tested moving back to adam, I used a virtual server for that and it seemed fine. I really appreciate the suggestions and will update with my findings.

And Jimmy to answer your questions... no special characters in the password.

And Jimmy to answer your question... no special characters in the password.

I did check the power settings and changed them to maximum performance and still saw the same behavior. It seems to be happening less, so I think maybe people have been using it more. My boss would like to try and stay on server 2008 if possible, so I opened a ticket with Lawson. The support person suggested turning off the Windows Firewall and changing the ldap port from 389 to 3268??? Not sure why that number. So I was curious, since yours is working Jimmy, can you tell me which port you are using?

i think the support person is confusing you with ldap port and ldapbind port.

If you are ldapbind to AD(active directory), the suggested DC to bind to is GC(global catalog server) which runs on port 3268.

Your ldap (ADLDS) port can be anything you like, 389 or whatever port that's valid.