Solved

Local account on Windows 2003 getting locked

Posted on 2011-03-14
5
331 Views
Last Modified: 2012-06-27
I have a windows 2003 server that runs a 3rd party application. This 3rd party application installs 2 local accounts on this server and sets a default password.

We recently had to change the password on these two local accounts.There are many appliances on the network that use these two accounts to interface with the 3rd party application.

Since the change, we are having problems with these two local accounts getting locked.
We have made password updates in several places but the passwords keep getting locked.

I see evidence of password failures in the security event log but how can I track down the devices that are still using the old password?
0
Comment
Question by:itplatoon
5 Comments
 
LVL 13

Expert Comment

by:AustinComputerLabs
ID: 35132579
Are any services relating to the SW using those accounts to authenticate?
0
 
LVL 1

Expert Comment

by:Emanhan
ID: 35132596
Use lockoutstatus tool to find out which DC accoutn was locked on. From the DC that the user account was locked search the security logs which will tell you the host.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=D1A5ED1D-CD55-4829-A189-99515B0E90F7
http://support.microsoft.com/kb/824209
0
 

Author Comment

by:itplatoon
ID: 35133511
There are no services that run on the server that use either of these 2 local accounts.

It appears that the lockoutstatus tool only works on AD accounts; when I try to query on a local computer account, where I point to the server (which is not a domain controller), the query fails to provides any information.
0
 
LVL 12

Accepted Solution

by:
Navdeep earned 500 total points
ID: 35136325
Hi,

check local account lockout policy, that affects the local system, [if this box is not on domain]
you can then disable the policy untill you find the root cause

generally the accounts get lockout if they throw bad passwords, so essentially you should be looking into the security logs and locate the events when bad password was used against those accounts and that caused them to lockout
0
 

Author Comment

by:itplatoon
ID: 35175890
I was able to resolve the issue by using the security event log and the system event log. I also checked the local account policy and it was set to 10 bad passwords and then it would lock out.
0

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Installing a printer using group policy preferences is not that hard let’s take a look at it. First lets open up your group policy console and edit the policy you want to add it to. I recommend creating a new policy for each printer makes it a l…
[b]Ok so now I will show you how to add a user name to the description at login. [/b] First connect to your DC (Domain Controller / Active Directory Server) SET PERMISSIONS FOR SCRIPT TO UPDATE COMPUTER DESCRIPTION TO USERNAME 1. Open Active …
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now