If the arserver is having issues talking to your directory server, then it will tie up the fast threads used to authenticate users via LDAP or whatever, which will in turn lock up users trying to authenticate via remedy, I think.
It really sounds like your directory server is flaking out, or maybe you are having network problems in the middle. I think the arplugin log file will be very useful to you here. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Nick Hromyak Sent: Tuesday, January 23, 2007 10:00 AM To: arslist@ARSLIST.ORG Subject: Re: EXT AUTH - Authentication service not responding I will lookup how to do an ARPLUGIN debug. I did setup the logs, and it doesn't appear to be slowed down or hanging. Would the AREA / LDAP access affect or slowdown Remedy users (users with passwords)??? It seems like it wouldn't, but what do I know??? Thanks. I am just trying to think what this could be, I was beginning to think it's a SQL problem, as this holds the passwords (or NULLs) before REmedy will go after the LDAP / Directory server for passwords, correct? Nick ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
