How to trace source of logon failure due to wrong password?

From: Panda Hung (panda@globalserve.net)
Date: 02/25/02 

From: "Panda Hung" <panda@globalserve.net>
Date: Mon, 25 Feb 2002 05:06:45 GMT

Is there a way to identify the originating computer that tries to log on to
a Win2K server with a wrong password? I have a server and one of the admin
accounts is always locked up because some computers are trying to map a
drive to that server. Unfortunately the password was recently changed (we
could not change it back due to company standard) and as a result, that
account is locked up everyday until it is unlocked by admin. (computer
standard again). We need to track down the originating computer and fix the
problem there.

Any help will be appreciated.

Panda Hung
panda@globalserve.net

Relevant Pages

  • Re: How to trace source of logon failure due to wrong password?
    ... Panda Hung wrote: ... > a Win2K server with a wrong password? ... > could not change it back due to company standard) and as a result, ... We need to track down the originating computer and fix the ...
    (comp.os.ms-windows.nt.admin.security)
  • Re: How to trace source of logon failure due to wrong password?
    ... tried the vent viewer, router logs etc. ... > a Win2K server with a wrong password? ... > could not change it back due to company standard) and as a result, ... We need to track down the originating computer and fix ...
    (comp.os.ms-windows.nt.admin.security)
  • Re: How to trace source of logon failure due to wrong password?
    ... The logon/logoff event shows up on the machine where the logon ... >> a Win2K server with a wrong password? ... >> account is locked up everyday until it is unlocked by admin. ... We need to track down the originating computer and fix ...
    (comp.os.ms-windows.nt.admin.security)