Enterprise Manager generates failed security audit every 10 seconds

From: Rob Lewis (roblewis963@hotmail.com)
Date: 09/30/02


From: "Rob Lewis" <roblewis963@hotmail.com>
Date: Mon, 30 Sep 2002 09:08:48 -0500


I have a SQL 2000 Server that is set up as a stand alone server, using SQL
and Integrated Security. I have failed logon auditing enabled.

If from a remote computer I open SQL Enterprise Manager and add a new
registration and successfully logon to the SQL server with a SQL account.
The remote server records failed logon security events.

If I just register the new server, but don't connect and instead select the
"prompt for logon credentials" I still get the failed security audits.

If I create a seperate SQL group and register the server in this group, as
long as I don't open the group it does NOT register failed logon attempts,
but as soon as I open the group the logon attempts start up again.

This is driving me crazy and makes it very difficult to audit failed logon
attempts when trying to do remote administration of the server. If anyone
can shed some light on this problem I would greatly appreciate it.

-R



Relevant Pages

  • Re: Borland is neglecting Delphi for Win32 badly
    ... Today in SQL ... Server 2000 you can write server extensions as COM objects and call them via ... SQLCLR allows CLR ... The security benefits are also tremendous and we could discuss for a long ...
    (borland.public.delphi.non-technical)
  • Re: SQL Permissions
    ... In advanced security the site server machine account has to be a member ... of the site server to sql connection group. ...
    (microsoft.public.sms.setup)
  • RE: Users Logins
    ... On the sql ... server machine, go to start, programs, SQL Server, then choose the icon for ... For information about the Microsoft Strategic Technology ... Protection Program and to order your FREE Security Tool Kit, ...
    (microsoft.public.sqlserver.security)
  • Re: SQL permission problem when installing SMS2003 in 2003 network
    ... Scenarios and Procedures for SMS 2003: Security ... >> I may need to put this post in an SQL newsgroup, ... >> install SMS2003 on ServerB. ... >> "Either the SQL Server is in a Windows NT 4 domain or this computer's ...
    (microsoft.public.sms.setup)
  • Re: Web and SQL Security
    ... If SQL server is the same box of IIS, you may consider disable TCP and ... named pipes protocals so that it is not possible to access SQL server from ... | Thread-Topic: Web and SQL Security ...
    (microsoft.public.sqlserver.security)