Discussion Locked

Administrator Account Frequently Locked

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have been noticing recently in my NT 4.0 Security logs that my Administrator account is constantly being locked out. It appears from the security event log that repeated failed login attempts from a domain and workstation unknown to me is occuringfrequently. This is not a service on one of my servers causing this. This is occurring frequently enough that I am concerned this is a hacker playing guess the password. It's also frequent eoungh that the account might be locked when I need to use it.
My questions are: can I block login attempts from other domains/workstations somehow? Are there other suggestions that I might try?

2 replies

by lordinfidel

here are some basic security tips to help you.

1. all passwords should be in muliples of 7 characters. (7/14/21) This is back from the lm authent days. With that in mind...

2. When installing a machine, such as a server. You want to first,after installation is over and sp's and hf's are applied.

a. rename the administrator account.
b. Copy the admin description, then delete the
description
c. rename guest to administrator, remove the
guest descr, and paste in the admin descr
d. set the guest password to 21 indecipharable
charcaters and make sure that it is disabled.
e. Create any user accounts that are essential
to the machine. Write down their passwords
and the user accounts function on that
machine. Use the 7/14 character rule.
f. The very last account that you should make
is a copy of the admin account. Set it's
password to 14 characters. This is the
account that you will use to administer the machine. There is a reason why this account is last, and is due to sid enumeration by hackers. I am going to be looking for low numbererd sids becaause of the tendency to create admin accounts first.
g. Finally, set the original admin password to 21 characters. Write it down! This admin account is for emergency use only and should never be used.
h. Log off and log back on as your everday use admin account.
i. Delete the original admins profile.

Additional....Obvioulsy you have logging turned on. What time of day is the account being tried. If it is a regular occurence, then at those times run a packet capture and find out what IP it's coming from. From there you can determine what machine it is from. If it is aIP in your dchp range, check your dhcp admin to see who owns the lease.

by robert w. smith

I identified the machine and reported it to an administrator in that domain. That machine was infected with something. Once the machine was disenfected and rebuilt, attempted logins to my server stopped.

This discussion is closed to new replies.