mhamer
asked on
Account Lockout
HI, AD2003
I recently changed the Admin password. and i know notice that badpassword attempts are happerning ever few seconds
I know which server is casuing the lockout due to event manager, but no idea how to find out whats causing it.
no MIS staff use this acocunt. no services are used with it, no scheduled tasks etc
how do you go about tracing the source thats locking the account out?
putthe password back to its old one and it stops logging bad passwords. I do have trusts setup they dont hold passwod info (or do they?)
backup exec, and Symantec AV are also in use but no links to Admin password (that i know of)
I recently changed the Admin password. and i know notice that badpassword attempts are happerning ever few seconds
I know which server is casuing the lockout due to event manager, but no idea how to find out whats causing it.
no MIS staff use this acocunt. no services are used with it, no scheduled tasks etc
how do you go about tracing the source thats locking the account out?
putthe password back to its old one and it stops logging bad passwords. I do have trusts setup they dont hold passwod info (or do they?)
backup exec, and Symantec AV are also in use but no links to Admin password (that i know of)
It does sound like you've got a service running using the Admin account. Are you sure that you've checked all of them? Also, make sure that the admin account isn't logged onto the desktop of the server causing the problem.
I guess you used this local admin account to install Symantic AV.
I use Sophos which actually asked during setup which local admin account to use. I should have converted it to a domain account but decided to leave it local.
The service is not running as that user but authenticating in behalf of a computer account for there access to the service.
You can increase event logons from gpedit.msc
computer config/windows settings/local policies/Audit policies:
this may assist in resolving
I use Sophos which actually asked during setup which local admin account to use. I should have converted it to a domain account but decided to leave it local.
The service is not running as that user but authenticating in behalf of a computer account for there access to the service.
You can increase event logons from gpedit.msc
computer config/windows settings/local policies/Audit policies:
this may assist in resolving
ASKER
Valrog only two services use domain account neither are the one in question
they log out any one not active after 30 mins, but yes checked and not logged on
Neopro2.
auditing is already on :-(
no local accounts as such on DC's it would have been intalled under this account, but i would have thought that as long as the user name has a working password that should not matter?
The service is not running as that user but authenticating in behalf of a computer account for there access to the service
dont follow
they log out any one not active after 30 mins, but yes checked and not logged on
Neopro2.
auditing is already on :-(
no local accounts as such on DC's it would have been intalled under this account, but i would have thought that as long as the user name has a working password that should not matter?
The service is not running as that user but authenticating in behalf of a computer account for there access to the service
dont follow
My antivirus Manager runs the service "local System"
But it was configured as a local admin account to allow connections from workstations in the domain.
eg:
the workstation loads the pre msi install with a local user account access. This way the users who are not in the domain but are allowed network access can be managed from this account.
Now if the workstations who have installed this application this way with the username and password defined, and i change that password bad password and it will be locked out. I hope i explained that correctly. But this does not mean Symanitc has that option. just something as a possiblity.
But it was configured as a local admin account to allow connections from workstations in the domain.
eg:
the workstation loads the pre msi install with a local user account access. This way the users who are not in the domain but are allowed network access can be managed from this account.
Now if the workstations who have installed this application this way with the username and password defined, and i change that password bad password and it will be locked out. I hope i explained that correctly. But this does not mean Symanitc has that option. just something as a possiblity.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.