OK...I'll find out from my sys admins which one that is...

 

Thanks,

Lisa

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of ARSList
Sent: Thursday, January 25, 2007 10:54 AM
To: [email protected]
Subject: Re: Login problems using AREA LDAP Authentication

 

I believe you want to go after a Domain Controller that has the Global
Catalog (GC).

 

 

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Estrella, Lisa
Sent: Thursday, January 25, 2007 8:51 AM
To: [email protected]
Subject: Re: Login problems using AREA LDAP Authentication

 

Hi,

 

Yep...It's the same.  I did notice that the users account is on a
different AD server (HQDC2)...so maybe it's something with that.  It
shouldn't make a difference since it should be replicating...but, you
never know....

 

Thanks,

Lisa

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of patrick zandi
Sent: Thursday, January 25, 2007 10:24 AM
To: [email protected]
Subject: Re: Login problems using AREA LDAP Authentication

 

** 

Open Hyena, and go to your users directory, 

fine a customer, and double click / or right mouse properties

.. now under the customer there is an ObjectTab.. 

Select it .. and look at the field : Full object Direcotry Path.

Now:: copy and paste to a note pad..

REMOVE  ldap:// blah blah/Username / 

you will be left with ou=_somthing,ou=Somethingelse,dc=whatever..

That is what you want in that field...

Check to see if they are the same.. 

 

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

** 

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___ 




-- 
Patrick Zandi __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___

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

Reply via email to