I wasn't the one who had compared the configs. One of my coworkers had missed that the config was actually different and I could see the difference quite easily in the logs (and would have seen it if I had double checked the form as well).
Anne Ramey *********************************** E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jason Miller Sent: Thursday, January 20, 2011 4:43 PM To: arslist@ARSLIST.ORG Subject: Re: User login issue ** Hi Anne, Do you mind sharing what the problem was? Jason On Jan 20, 2011 10:25 AM, "Ramey, Anne" <anne.ra...@nc.gov<mailto:anne.ra...@nc.gov>> wrote: > That did allow me to spot the issue. I had forgotten that was so easy to > change. Thanks for the reminder. > > Anne Ramey > *********************************** > E-mail correspondence to and from this address may be subject to the North > Carolina Public Records Law and may be disclosed to third parties only by an > authorized State Official. > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Danny > Kellett > Sent: Thursday, January 20, 2011 12:58 PM > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > Subject: Re: User login issue > > If you set the plugin log level to ALL then you can see the ldap reply > codes that will tell you exactly whats wrong > >> We are running a server group (ARS 7.1 ITSM 7.0.03 p 9) and are seeing a >> strange issue. We use LDAP authentication and have exactly the same LDAP >> settings on both servers in the server group...they point to the same >> server and use the same user to bind and the same settings to authenticate >> users. We have a series of newly created users that can login to one >> server in the server group, but not the other. When they can't login >> successfully, we see >> 20 2011 08:43:36.8357 */ LOGIN FAILED <accountname> (user) >> In the user log, with a matching >> C: 390695> /* Thu Jan 20 2011 08:43:36.8285 */+VL >> AREAVerifyLoginCallback -- user <accountname> >> C: 390695> /* Thu Jan 20 2011 08:43:36.8306 */-VL >> FAIL >> In the arplugin log. >> But if the same user logs in on the other server, it all works perfectly. >> If this was happening to all users on the problem server, I could >> understand that, but it seems to just be those created in the last month >> or so. We are working with our AD admins to see if they can see a >> problem, but since the working server is using the same AD server, I can't >> see how it can be their problem. Any ideas are appreciated. >> >> Anne Ramey >> >> *********************************** >> E-mail correspondence to and from this address may be subject to the North >> Carolina Public Records Law and may be disclosed to third parties only by >> an authorized State Official. >> >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at >> www.arslist.org<http://www.arslist.org> >> attend wwrug11 www.wwrug.com<http://www.wwrug.com> ARSList: "Where the >> Answers Are" >> > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at > www.arslist.org<http://www.arslist.org> > attend wwrug11 www.wwrug.com<http://www.wwrug.com> ARSList: "Where the > Answers Are" > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at > www.arslist.org<http://www.arslist.org> > attend wwrug11 www.wwrug.com<http://www.wwrug.com> ARSList: "Where the > Answers Are" _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
