Lisa,
is it possible to narrow this by adding in an ou ?
like


ou=rrs all users,ou=rm    Would be for me..   Then all lthe stuff you have..
Can you narrow this.. it would be a little better I would think..


On 1/25/07, Estrella, Lisa <[EMAIL PROTECTED]> wrote:

**

Hi,



I'm using the following:



Host name:  hqdc1.ad.navteq.com

User base:  DC=ad,DC=navteq,DC=com

User Search:  samaccountname=$\USER$



I haven't noticed any problems like you are describing…it's just some
people aren't able to log into remedy after changing their password.  I have
had them try to use their old password and that doesn't work either.  That
is why I initially had the helpdesk reset their password again and then it
works.  So, I'm not sure what is going on.  Just to clarify…it only happens
every once in a while and not for everyone.  ???



Thanks,

Lisa
 ------------------------------

*From:* Action Request System discussion list(ARSList) [mailto:
[EMAIL PROTECTED] *On Behalf Of *ARSList
*Sent:* Wednesday, January 24, 2007 3:52 PM
*To:* [email protected]
*Subject:* Re: Login problems using AREA LDAP Authentication



What Host name, User Base, and User Search Filter settings?



I have noticed AREA (somehow) uses a cached password on our system for
about an hour. I am not sure how this happens though.  It seems pretty
weird. If I change my LDAP password, I can still use my old password for
around an hour, along with the new password.



Be sure your Distinguished Name logon account can see all the OUs below
wherever the users are.




  ------------------------------

*From:* Action Request System discussion list(ARSList) [mailto:
[EMAIL PROTECTED] *On Behalf Of *Estrella, Lisa
*Sent:* Wednesday, January 24, 2007 11:38 AM
*To:* [email protected]
*Subject:* Login problems using AREA LDAP Authentication



Good afternoon,



Has anyone who is using AREA LDAP authentication experienced the following
problem?  And if so, were you able to fix it?



Sometimes when a user is prompted to change their network password (and
they change it) they are no longer able to log into the midtier.  They
receive the standard authentication error.  If our helpdesk resets the
password for them, then they are able to login just fine.  I know that
sometimes it can take up to 15 minutes to replicate between AD servers, but
I still don't understand why this is happening with some of my users when
they manually change their password.



I just wanted to see if anyone else has experienced this.



Thanks,

Lisa



ARS 6.3 patch 18

HD 6.0

CM 6.0

SQL

Win Server 2003
__20060125_______________________This posting was submitted with HTML in
it___ __20060125_______________________This posting was submitted with HTML
in it___ __20060125_______________________This posting was submitted with
HTML in it___




--
Patrick Zandi

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers 
Are"

Reply via email to