Re: AD account - weird problem

[RichardMcClary]

Thanks to all...

May never know the reason, but this morning (in the agent's absence) I 
reset the password yet again.  This time I got on (as her) with no issues 
at all...

Too bad she'll need her supervisor to tell her the new password (and how 
to change it again).

Other than that, it is fixed.

Again, thanks to all!
--
Richard D. McClary
Systems Administrator, Information Technology Group 
ASPCA®
1717 S. Philo Rd, Ste 36
Urbana, IL  61802
 
richardmccl...@aspca.org
 
P: 217-337-9761
C: 217-417-1182
F: 217-337-9761
www.aspca.org
 
The information contained in this e-mail, and any attachments hereto, is 
from The American Society for the Prevention of Cruelty to Animals® (ASPCA
®) and is intended only for use by the addressee(s) named herein and may 
contain legally privileged and/or confidential information. If you are not 
the intended recipient of this e-mail, you are hereby notified that any 
dissemination, distribution, copying or use of the contents of this 
e-mail, and any attachments hereto, is strictly prohibited. If you have 
received this e-mail in error, please immediately notify me by reply email 
and permanently delete the original and any copy of this e-mail and any 
printout thereof.
 

"Bob Hartung"  wrote on 06/01/2010 08:19:19 AM:

> Richard, you said "She was unable to log into any workstations on 
> our network." This would rule out any local issues on her workstation.
> 
> You did not mention if you had tried to log on as her. I've seen 
> situations with users who only have to enter the password when 
> logging in because no one else ever logs on to their PC. Over time 
> the forget their login name and enter a wrong one when trying to log
> in. Alternatively, if someone logged into her PC as a local admin 
> before her next login, she may not even know that she needs to 
> change from a local to domain login.
> 
> Try logging in as her yourself to eliminate user error.
> 
> --
> 
> Bob Hartung
> Wisco Industries, Inc.
> 736 Janesville St.
> Oregon, WI 53575
> Tel: (608) 835-3106 x215
> Fax: (608) 835-7399
> e-mail: bhartung(at)wiscoind.com
> From: James Rankin [mailto:kz2...@googlemail.com]
> To: NT System Admin Issues 
[mailto:ntsysad...@lyris.sunbelt-software.com]
> Sent: Tue, 01 Jun 2010 08:01:31 -0500
> Subject: Re: AD account - weird problem
> 
> Keyboard got a stuck key? That happens a lot here

> On 1 June 2010 13:53,  wrote:
> 
> Greetings! 
> 
> I got an emergency call MON regarding one of my users (a poison 
> center agent).  She was unable to log into any of the workstations 
> in our network.  Other agents were able to log into her primary 
> workstation.  She was getting the "usual error" that the password 
> was incorrect (and to check the CapsLock key). 
> 
> I used ADUC from my workstation to reset her password.  Still no 
access... 
> 
> I tried ADUC from two different domain controllers, and tried 
> setting different passwords.  Still no access... 
> 
> I also checked her account properties.  The "login hours" were set 
> to full access, 168 hours per week.  The account is not locked. 
> 
> Domain is Windows 2003 "Native" (not R2).  Workstations are all WinXP 
Pro SP3.
> 
> Before I bring out the big artillery (delete her account, re-create 
> it, and then re-assign permissions to all her files, shares, etc), 
> what else to check? 
> 
> Thanks...
> -- 
> Richard D. McClary 
> Systems Administrator, Information Technology Group 
> ASPCA® 
> 1717 S. Philo Rd, Ste 36 
> Urbana, IL  61802 
> 
> richardmccl...@aspca.org 
> 
> P: 217-337-9761 
> C: 217-417-1182 
> F: 217-337-9761 
> www.aspca.org 
> 
> The information contained in this e-mail, and any attachments 
> hereto, is from The American Society for the Prevention of Cruelty to 
Animals®
> (ASPCA®) and is intended only for use by the addressee(s) named 
> herein and may contain legally privileged and/or confidential 
> information. If you are not the intended recipient of this e-mail, 
> you are hereby notified that any dissemination, distribution, 
> copying or use of the contents of this e-mail, and any attachments 
> hereto, is strictly prohibited. If you have received this e-mail in 
> error, please immediately notify me by reply email and permanently 
> delete the original and any copy of this e-mail and any printout 
thereof. 
> 
> 
> 
> 
> 
> 
> -- 
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put
> into the machine wrong figures, will the right answers come out?' I 
> am not able rightly to apprehend the kind of confusion of ideas that
> could provoke such a question."

> 
> 
> 
> 
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Re: AD account - weird problem

[Bob Hartung]

Richard, you said "She was unable to log into any workstations on our network." 
This would rule out any local issues on her workstation.

You did not mention if you had tried to log on as her. I've seen situations 
with users who only have to enter the password when logging in because no one 
else ever logs on to their PC. Over time the forget their login name and enter 
a wrong one when trying to log in. Alternatively, if someone logged into her PC 
as a local admin before her next login, she may not even know that she needs to 
change from a local to domain login.

Try logging in as her yourself to eliminate user error.

--

Bob Hartung
Wisco Industries, Inc.
736 Janesville St.
Oregon, WI 53575
Tel: (608) 835-3106 x215
Fax: (608) 835-7399
e-mail: bhartung(at)wiscoind.com
  _  

From: James Rankin [mailto:kz2...@googlemail.com]
To: NT System Admin Issues [mailto:ntsysad...@lyris.sunbelt-software.com]
Sent: Tue, 01 Jun 2010 08:01:31 -0500
Subject: Re: AD account - weird problem

Keyboard got a stuck key? That happens a lot here


On 1 June 2010 13:53,   wrote:

Greetings!  
  
I got an emergency call MON regarding  one of my users (a poison center agent). 
 She was unable to log into  any of the workstations in our network.  Other 
agents were able to  log into her primary workstation.  She was getting the 
"usual  error" that the password was incorrect (and to check the CapsLock  
key).  
  
I used ADUC from my workstation to reset  her password.  Still no access...  
  
I tried ADUC from two different domain  controllers, and tried setting 
different passwords.  Still no access...  
  
I also checked her account properties.   The "login hours" were set to full 
access, 168 hours per  week.  The account is not locked.  
  
Domain is Windows 2003 "Native"  (not R2).  Workstations are all WinXP Pro SP3. 
 
  
Before I bring out the big artillery  (delete her account, re-create it, and 
then re-assign permissions to all  her files, shares, etc), what else to check? 
 
  
Thanks...
  --  
Richard D. McClary  
Systems Administrator,  Information Technology Group
ASPCA®  
1717 S. Philo Rd, Ste  36  
Urbana, IL  61802  
   
richardmccl...@aspca.org  
   
P: 217-337-9761  
C: 217-417-1182  
F: 217-337-9761  
www.aspca.org  
   

The information contained  in this e-mail, and any attachments hereto, is from 
The American Society  for the Prevention of Cruelty to Animals® (ASPCA®)  and 
is intended only for use by the addressee(s) named herein and may contain  
legally privileged and/or confidential information. If you are not the  
intended recipient of this e-mail, you are hereby notified that any 
dissemination,  distribution, copying or use of the contents of this e-mail, 
and any attachments  hereto, is strictly prohibited. If you have received this 
e-mail in error,  please immediately notify me by reply email and permanently 
delete the  original and any copy of this e-mail and any printout thereof.  
   

   

  

   


-- 
"On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into the 
machine wrong figures, will the right answers come out?' I am not able rightly 
to apprehend the kind of confusion of ideas that could provoke such a question."
  


   

  

   

  
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Re: AD account - weird problem

[Andrew Levicki]

Hi Richard,

Unless she insisted on taking her keyboard with her to all the other
workstations, I think we can rule out a sticky or bad keyboard!

Have you tried logging on as the user yourself after having reset her
password, rather than relying on her saying it does or doesn't work? I would
be inclined to try that.

Also, although it should explicitly say that the account has expired if it
has, you should check that the account hasn't expired.

Let us know how you get on, I'd be interested to find out what it was when
you know...

Cheers,

Andrew

On 1 June 2010 22:07, Maglinger, Paul  wrote:

>  Bad keyboard?
>
>
>
> *From:* richardmccl...@aspca.org [mailto:richardmccl...@aspca.org]
> *Sent:* Tuesday, June 01, 2010 7:54 AM
> *To:* NT System Admin Issues
> *Subject:* AD account - weird problem
>
>
>
>
> Greetings!
>
> I got an emergency call MON regarding one of my users (a poison center
> agent).  She was unable to log into any of the workstations in our network.
>  Other agents were able to log into her primary workstation.  She was
> getting the "usual error" that the password was incorrect (and to check the
> CapsLock key).
>
> I used ADUC from my workstation to reset her password.  Still no access...
>
> I tried ADUC from two different domain controllers, and tried setting
> different passwords.  Still no access...
>
> I also checked her account properties.  The "login hours" were set to full
> access, 168 hours per week.  The account is not locked.
>
> Domain is Windows 2003 "Native" (not R2).  Workstations are all WinXP Pro
> SP3.
>
> Before I bring out the big artillery (delete her account, re-create it, and
> then re-assign permissions to all her files, shares, etc), what else to
> check?
>
> Thanks...
> --
> Richard D. McClary
> Systems Administrator, Information Technology Group
> *ASPCA®*
> 1717 S. Philo Rd, Ste 36
> Urbana, IL  61802
>
> richardmccl...@aspca.org
>
> P: 217-337-9761
> C: 217-417-1182
> F: 217-337-9761
> www.aspca.org
>
>
> The information contained in this e-mail, and any attachments hereto, is
> from The American Society for the Prevention of Cruelty to Animals® (ASPCA
> ®) and is intended only for use by the addressee(s) named herein and may
> contain legally privileged and/or confidential information. If you are not
> the intended recipient of this e-mail, you are hereby notified that any
> dissemination, distribution, copying or use of the contents of this e-mail,
> and any attachments hereto, is strictly prohibited. If you have received
> this e-mail in error, please immediately notify me by reply email and
> permanently delete the original and any copy of this e-mail and any printout
> thereof.
>
>
>
>
>
>
>
>
>
>
>


-- 
Kind regards,

Andrew Levicki
MCITP:EDST7/EMA/EA,MCSE,MCSA,MCP,CCNA,ITIL

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

RE: AD account - weird problem

[Kennedy, Jim]

Disable the account, get coffee...then re-enable it. I have had a few here and 
there do what you describe and that fixes it.



From: richardmccl...@aspca.org [mailto:richardmccl...@aspca.org]
Sent: Tuesday, June 01, 2010 7:54 AM
To: NT System Admin Issues
Subject: AD account - weird problem


Greetings!

I got an emergency call MON regarding one of my users (a poison center agent).  
She was unable to log into any of the workstations in our network.  Other 
agents were able to log into her primary workstation.  She was getting the 
"usual error" that the password was incorrect (and to check the CapsLock key).

I used ADUC from my workstation to reset her password.  Still no access...

I tried ADUC from two different domain controllers, and tried setting different 
passwords.  Still no access...

I also checked her account properties.  The "login hours" were set to full 
access, 168 hours per week.  The account is not locked.

Domain is Windows 2003 "Native" (not R2).  Workstations are all WinXP Pro SP3.

Before I bring out the big artillery (delete her account, re-create it, and 
then re-assign permissions to all her files, shares, etc), what else to check?

Thanks...
--
Richard D. McClary
Systems Administrator, Information Technology Group
ASPCA(r)
1717 S. Philo Rd, Ste 36
Urbana, IL  61802

richardmccl...@aspca.org

P: 217-337-9761
C: 217-417-1182
F: 217-337-9761
www.aspca.org


The information contained in this e-mail, and any attachments hereto, is from 
The American Society for the Prevention of Cruelty to Animals(r) (ASPCA(r)) and 
is intended only for use by the addressee(s) named herein and may contain 
legally privileged and/or confidential information. If you are not the intended 
recipient of this e-mail, you are hereby notified that any dissemination, 
distribution, copying or use of the contents of this e-mail, and any 
attachments hereto, is strictly prohibited. If you have received this e-mail in 
error, please immediately notify me by reply email and permanently delete the 
original and any copy of this e-mail and any printout thereof.










~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

RE: AD account - weird problem

[Maglinger, Paul]

Bad keyboard?

 

From: richardmccl...@aspca.org [mailto:richardmccl...@aspca.org] 
Sent: Tuesday, June 01, 2010 7:54 AM
To: NT System Admin Issues
Subject: AD account - weird problem

 


Greetings! 

I got an emergency call MON regarding one of my users (a poison center
agent).  She was unable to log into any of the workstations in our
network.  Other agents were able to log into her primary workstation.
She was getting the "usual error" that the password was incorrect (and
to check the CapsLock key). 

I used ADUC from my workstation to reset her password.  Still no
access... 

I tried ADUC from two different domain controllers, and tried setting
different passwords.  Still no access... 

I also checked her account properties.  The "login hours" were set to
full access, 168 hours per week.  The account is not locked. 

Domain is Windows 2003 "Native" (not R2).  Workstations are all WinXP
Pro SP3. 

Before I bring out the big artillery (delete her account, re-create it,
and then re-assign permissions to all her files, shares, etc), what else
to check? 

Thanks...
-- 
Richard D. McClary 
Systems Administrator, Information Technology Group 
ASPCA(r) 
1717 S. Philo Rd, Ste 36 
Urbana, IL  61802 
  
richardmccl...@aspca.org 
  
P: 217-337-9761 
C: 217-417-1182 
F: 217-337-9761 
www.aspca.org   
  

The information contained in this e-mail, and any attachments hereto, is
from The American Society for the Prevention of Cruelty to Animals(r)
(ASPCA(r)) and is intended only for use by the addressee(s) named herein
and may contain legally privileged and/or confidential information. If
you are not the intended recipient of this e-mail, you are hereby
notified that any dissemination, distribution, copying or use of the
contents of this e-mail, and any attachments hereto, is strictly
prohibited. If you have received this e-mail in error, please
immediately notify me by reply email and permanently delete the original
and any copy of this e-mail and any printout thereof. 
  

 

 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

Re: AD account - weird problem

[James Rankin]

Keyboard got a stuck key? That happens a lot here

On 1 June 2010 13:53,  wrote:

>
> Greetings!
>
> I got an emergency call MON regarding one of my users (a poison center
> agent).  She was unable to log into any of the workstations in our network.
>  Other agents were able to log into her primary workstation.  She was
> getting the "usual error" that the password was incorrect (and to check the
> CapsLock key).
>
> I used ADUC from my workstation to reset her password.  Still no access...
>
> I tried ADUC from two different domain controllers, and tried setting
> different passwords.  Still no access...
>
> I also checked her account properties.  The "login hours" were set to full
> access, 168 hours per week.  The account is not locked.
>
> Domain is Windows 2003 "Native" (not R2).  Workstations are all WinXP Pro
> SP3.
>
> Before I bring out the big artillery (delete her account, re-create it, and
> then re-assign permissions to all her files, shares, etc), what else to
> check?
>
> Thanks...
> --
> Richard D. McClary
> Systems Administrator, Information Technology Group
> *ASPCA®*
> 1717 S. Philo Rd, Ste 36
> Urbana, IL  61802
>
> richardmccl...@aspca.org
>
> P: 217-337-9761
> C: 217-417-1182
> F: 217-337-9761
> *www.aspca.org* 
>
>
> The information contained in this e-mail, and any attachments hereto, is
> from The American Society for the Prevention of Cruelty to Animals® (ASPCA
> ®) and is intended only for use by the addressee(s) named herein and may
> contain legally privileged and/or confidential information. If you are not
> the intended recipient of this e-mail, you are hereby notified that any
> dissemination, distribution, copying or use of the contents of this e-mail,
> and any attachments hereto, is strictly prohibited. If you have received
> this e-mail in error, please immediately notify me by reply email and
> permanently delete the original and any copy of this e-mail and any printout
> thereof.
>
>
>
>
>
>
>


-- 
"On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
the machine wrong figures, will the right answers come out?' I am not able
rightly to apprehend the kind of confusion of ideas that could provoke such
a question."

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

RE: AD account - weird problem

[Jeff Cain]

Are you able to test her access? IE: Log in as her and verify that the problem 
is not user related?

Thanks,
Jeff Cain
Technical Support Analyst
Sunbelt Software
Email: supp...@sunbeltsoftware.com
Voice: 1-877-673-1153
Fax:   1-727-562-5199
Web: >
Physical Address:
33 N Garden Ave
Suite 1200
Clearwater, FL  33755
United States

If you do not want further email from us, please forward
this message to 
listmana...@sunbelt-software.com with
the word 'unsubscribe' in the subject of your email.

Helpful Sunbelt Software Links:

Knowledge Base
Open a New Support Ticket
Sunbelt Software Product Support 
Communities

From: richardmccl...@aspca.org [mailto:richardmccl...@aspca.org]
Sent: Tuesday, June 01, 2010 8:54 AM
To: NT System Admin Issues
Subject: AD account - weird problem


Greetings!

I got an emergency call MON regarding one of my users (a poison center agent).  
She was unable to log into any of the workstations in our network.  Other 
agents were able to log into her primary workstation.  She was getting the 
"usual error" that the password was incorrect (and to check the CapsLock key).

I used ADUC from my workstation to reset her password.  Still no access...

I tried ADUC from two different domain controllers, and tried setting different 
passwords.  Still no access...

I also checked her account properties.  The "login hours" were set to full 
access, 168 hours per week.  The account is not locked.

Domain is Windows 2003 "Native" (not R2).  Workstations are all WinXP Pro SP3.

Before I bring out the big artillery (delete her account, re-create it, and 
then re-assign permissions to all her files, shares, etc), what else to check?

Thanks...
--
Richard D. McClary
Systems Administrator, Information Technology Group
ASPCA(r)
1717 S. Philo Rd, Ste 36
Urbana, IL  61802

richardmccl...@aspca.org

P: 217-337-9761
C: 217-417-1182
F: 217-337-9761
www.aspca.org


The information contained in this e-mail, and any attachments hereto, is from 
The American Society for the Prevention of Cruelty to Animals(r) (ASPCA(r)) and 
is intended only for use by the addressee(s) named herein and may contain 
legally privileged and/or confidential information. If you are not the intended 
recipient of this e-mail, you are hereby notified that any dissemination, 
distribution, copying or use of the contents of this e-mail, and any 
attachments hereto, is strictly prohibited. If you have received this e-mail in 
error, please immediately notify me by reply email and permanently delete the 
original and any copy of this e-mail and any printout thereof.






~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

RE: AD account - weird problem

[Andy Shook]

The event logs on the workstation(s) and DCs for one...

Shook

From: richardmccl...@aspca.org [mailto:richardmccl...@aspca.org]
Sent: Tuesday, June 01, 2010 8:54 AM
To: NT System Admin Issues
Subject: AD account - weird problem


Greetings!

I got an emergency call MON regarding one of my users (a poison center agent).  
She was unable to log into any of the workstations in our network.  Other 
agents were able to log into her primary workstation.  She was getting the 
"usual error" that the password was incorrect (and to check the CapsLock key).

I used ADUC from my workstation to reset her password.  Still no access...

I tried ADUC from two different domain controllers, and tried setting different 
passwords.  Still no access...

I also checked her account properties.  The "login hours" were set to full 
access, 168 hours per week.  The account is not locked.

Domain is Windows 2003 "Native" (not R2).  Workstations are all WinXP Pro SP3.

Before I bring out the big artillery (delete her account, re-create it, and 
then re-assign permissions to all her files, shares, etc), what else to check?

Thanks...
--
Richard D. McClary
Systems Administrator, Information Technology Group
ASPCA(r)
1717 S. Philo Rd, Ste 36
Urbana, IL  61802

richardmccl...@aspca.org

P: 217-337-9761
C: 217-417-1182
F: 217-337-9761
www.aspca.org


The information contained in this e-mail, and any attachments hereto, is from 
The American Society for the Prevention of Cruelty to Animals(r) (ASPCA(r)) and 
is intended only for use by the addressee(s) named herein and may contain 
legally privileged and/or confidential information. If you are not the intended 
recipient of this e-mail, you are hereby notified that any dissemination, 
distribution, copying or use of the contents of this e-mail, and any 
attachments hereto, is strictly prohibited. If you have received this e-mail in 
error, please immediately notify me by reply email and permanently delete the 
original and any copy of this e-mail and any printout thereof.






~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~