account lockout fails

From: chris (csheehan_at_seaviewseward.org)
Date: 05/27/03 

Date: Tue, 27 May 2003 11:12:32 -0800

Has anyone seen strings of logon attempts from a workstation in a domain
where the lockout policy does not take effect?

I have strings of Event 676, always in sets of 24 (12 reference the
workstation IP and 12 reference the DC IP) that occur when the workstation
is sitting idle and no one has physical access.

If I sit at the workstation and type in the wrong password, the policy does
take effect.
I haven't found any documentation specific to Win2K for something like this.
Thanks!

Relevant Pages

  • Re: Group Policy Need help !!
    ... You didn't find the settings in the GPO called "Small Business Server ... on a workstation go to Start -> Run and type ... I need change the lockout policy for the system, ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Also, Logon type of 3 is a network logon, this is considered a ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Also, Logon type of 3 is a network logon, this is considered a ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Users cannot access remote web workplace without admin access
    ... RWW site logon issue ... When we create the user accounts by using the SBS add users ... workstation through the RWW-RDP connection? ... For the RDP access issue, it could be an expected behavior. ...
    (microsoft.public.windows.server.sbs)
  • Re: How list all current logon NT domain users?
    ... > last logon time, but not give the logoff time. ... required to exist while the user remains logged on to a workstation or TS ... "agent" on every single workstation, ...
    (microsoft.public.win32.programmer.kernel)