Security log problems Please Help!!

From: Dezignin (mthomason_at_progresstank.com)
Date: 05/29/03 

Date: Thu, 29 May 2003 09:44:38 -0500

My security log is only showing
Object access 562 and privileged use 578
562 pops up every minute so my long is now useless
I know it's something I've done, but I don't know where to change this. I
know it isn't in the filter so could someone point me in the direct of where
to set what gets logged and what doesn't. I've been getting a lot of failed
log on attempts on my TermSrv lately and know I can't see what is going on.
Thanks for any help

Relevant Pages

  • Re: Event ID 560 Problem
    ... >Error 560s usually refer to object access. ... >whenever a user makes a connection to something out on ... >> this repeated event in my security log that I can't ... Whenever someone log off their workstation, ...
    (microsoft.public.win2000.security)
  • Re: Help!Am I being hacked?
    ... That is entirely normal to be seen in the security log for access to the local sam by ... NT AUTHORITY\SYSTEM when object access is enabled. ... for the administrator account. ... account can not be locked out to console logon. ...
    (microsoft.public.win2000.security)
  • Re: Data access and security permissions
    ... protection" to "low" and see if this continues. ... >Category: Object Access ... Access databases ... security log to fill up ...
    (microsoft.public.inetserver.iis.security)
  • auditing question - single file object access creates duplicate security log messages
    ... The multiple entries are a pain. ... >I would like to audit file access on my server. ... >get a multitude of messages in the security log every ... >I have enabled auditing of object access in the Local ...
    (microsoft.public.win2000.security)
  • Re: Event Viewer Getting Full
    ... auditing of object access must be enabled. ... http://www.sysinternals.com/ntw2k/freeware/psloglist.shtml -- PsLogList to dump lof ... You can increase the size of the security log and by default it ... >> audit for only specific files and avoid using the users and everyone group to ...
    (microsoft.public.win2000.security)