I have seen that with 6.3 and AD. After the first set of results were returned successfully, the plug-in server would hang on any queries after that. I had to restart ARS or it did appear to work again if I let it sit for a while.
I did not have this problem if I used the AD global catalog. To use the GC add :3268 after your ldap server's FQDN. The problem I then had was the attribute I wanted was not listed in the GC. I currently have ARS 7.0.01 p001 pulling data from a non AD LDAP directory (not really sure what vendor it is) and have not see this issue. Example: ldap://DC.domain.com:3268/DC=domain,DC=com??sub?(objectclass=user) From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eli Schilling Sent: Wednesday, May 09, 2007 1:31 PM To: [email protected] Subject: Querying Active Directory ** Hi Listers, I'm running AR 7.01 with patch 02. I recently configured the system to talk to AD (same config as is currently utilized in our 6.3 production environment) and I keep getting tmeout errors. I have the plug-in server timeout currently set to 10 minutes (600 seconds) and it continues to fail. Has anyone encountered and then resolved this type of issue? Thanks much! Eli __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
