In-Reply-To: <[EMAIL PROTECTED]>
I don't profess to be an expert but if you set up the NT server to log
failed attempts to log in and the client is set up to do the same then if
you examine the logs after the user get's locked out again you will be
able to discern weather it's the (L)user. If it's not the user then you
should be able to determine where the failed attempt is coming from.
getting a new machine is pretty lame. I know that wasn't your decision
but please forward this to whom ever is in control of making that
decision, so they know what the rest of the knowledgeable world thinks.
You folks must have a lot of money to throw away or that person is
invaluable to your organization that they can't be without him/her for too
long.
Check to see if the client machine is set up with a static IP or DHCP. If
static, insure that the IP of the machine does not match any other
machine. If you have a DHCP check for any rouge servers. Although this
in it self will not lock out a users it is always good to check your
configuration.
Insure that the user is attempting to log on to the NT server and not to
the machine locally.
If you find out that the (L)user is fat fingering the password or is just
too shallow (probably a high level manager) to remember their password you
might want to find other suitable employment with someone more compentent
or just ask for more pay to deal with the insanity.
