"sa" is not a Windows account. It wouldn't show up in Windows Security event logs
Cheers Ken From: David W. McSpadden [mailto:[EMAIL PROTECTED] Sent: Friday, 16 May 2008 3:20 AM To: NT System Admin Issues Subject: Re: account lockout Hard to say. I had the SA account failing log in's every time a user got into an app. didn't show in the DC event or the workstation event just the Error log of SQL. So I ran the SQL Profiler and found the computer that was failing the log in. Mostly because I thought I might have a mouse in my pudding but found it was just a bad ODBC settings. Dropped and add the ODBC connection and magically the app started worked (Not reported as an issue from the user) and the login failures stopped. ----- Original Message ----- From: Tim Evans<mailto:[EMAIL PROTECTED]> To: NT System Admin Issues<mailto:[email protected]> Sent: Thursday, May 15, 2008 1:14 PM Subject: RE: account lockout Thanks, I'll have our DBA give that a try and let you know how it goes. Is it correct that these failed logons wouldn't show up in the DC's security logs if I'm auditing logon failures? ...Tim From: David W. McSpadden [mailto:[EMAIL PROTECTED] Sent: Thursday, May 15, 2008 9:55 AM To: NT System Admin Issues Subject: Re: account lockout Run a SQL profiler trace and audit log on's for that account. You can even audit log on failures. This should give you the process that is screwing you up. ----- Original Message ----- From: Tim Evans<mailto:[EMAIL PROTECTED]> To: NT System Admin Issues<mailto:[email protected]> Sent: Thursday, May 15, 2008 12:49 PM Subject: RE: account lockout BTW, Its Windows 2003 server Forest and Domain functional level ...Tim ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
