![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi. I made an alert that will email me whenever someone causes error 18456 to be raised... My thinking behind this is that if anyones trying to access my server and FAILS, then they are probably up to no good. So anyway... This alert was created... I verified that SQL Server Agent Mail is running, as is SQL Mail... so thats not the point of failure. I just attempted to log in with sa and a fake password. It predictably did not give me access to the databases, but the event was NOT logged to the application log. I checked in enterprise manager, and the checkbox that says "Always write to Windows eventlog" is checked. I also verified that the SQL Server Agent is running under a local and domain admin, and this is the case. Does anybody have any ideas? Thanks in advance, -- Jason |
#3
| |||
| |||
|
|
I assume that this error number is failed login. If so, you handle this in a special way. EM, right-click your server, security. -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "Jeigh" <folkens.jason (AT) acd (DOT) net> wrote Hi. I made an alert that will email me whenever someone causes error 18456 to be raised... My thinking behind this is that if anyones trying to access my server and FAILS, then they are probably up to no good. So anyway... This alert was created... I verified that SQL Server Agent Mail is running, as is SQL Mail... so thats not the point of failure. I just attempted to log in with sa and a fake password. It predictably did not give me access to the databases, but the event was NOT logged to the application log. I checked in enterprise manager, and the checkbox that says "Always write to Windows eventlog" is checked. I also verified that the SQL Server Agent is running under a local and domain admin, and this is the case. Does anybody have any ideas? Thanks in advance, -- Jason |
#4
| |||
| |||
|
|
Are you referring to the "Audit Level" raido buttons? Changing it from "None" to "Failure" didnt seem to make that much of a difference. Am I looking at the right thing? Thanks, -- Jason "Tibor Karaszi" <tibor_please.no.email_karaszi (AT) hotmail (DOT) nomail.com> wrote in message news:O6NBB4STEHA.2416 (AT) TK2MSFTNGP09 (DOT) phx.gbl... I assume that this error number is failed login. If so, you handle this in a special way. EM, right-click your server, security. -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "Jeigh" <folkens.jason (AT) acd (DOT) net> wrote in message news:CoydnaIo9LfTcVndRVn-gw (AT) giganews (DOT) com... Hi. I made an alert that will email me whenever someone causes error 18456 to be raised... My thinking behind this is that if anyones trying to access my server and FAILS, then they are probably up to no good. So anyway... This alert was created... I verified that SQL Server Agent Mail is running, as is SQL Mail... so thats not the point of failure. I just attempted to log in with sa and a fake password. It predictably did not give me access to the databases, but the event was NOT logged to the application log. I checked in enterprise manager, and the checkbox that says "Always write to Windows eventlog" is checked. I also verified that the SQL Server Agent is running under a local and domain admin, and this is the case. Does anybody have any ideas? Thanks in advance, -- Jason |
![]() |
| Thread Tools | |
| Display Modes | |
| |