Solved

MS SQL Enterprise Manager Generates MANY Windows LOGON Failure Events

Posted on 2004-10-14
12
453 Views
Last Modified: 2013-12-03
Hi All:

We reciently turned up a syslog server that is logging Windows Events.  For security reasons, we have turned on Logon Failuers on our Windows Servers.  Once this was done, we noticed that any user using the SQL Enterprise Manager is generating Windows NT Logon Failiuers, many (about 10+ per minute per user per database).  We are in a No-Windows-Domain environment and most if not all of the databases have Database User Security.  

Is there anyway to get Enterprise Manager to stop trying to login the Windows Side and simply connect directly to the database.  

Yes, the Enterprise manager connections are set to Windows and Database Security (Mixed Mode).

The username of the Failures is the currently logged in Windows username on the Client.


Thanks in advance.

============================================================
Deleted with 125 points refunded
12/05/2004 02:29AM PST
modulo
Community Support Moderator
============================================================
0
Comment
Question by:ort11
  • 5
  • 3
12 Comments
 
LVL 6

Expert Comment

by:JaffaKREE
ID: 12308859
What platform is EM running on ?
0
 
LVL 15

Expert Comment

by:jdlambert1
ID: 12308897
Try this:
On each user's machine, open EM, right-click on a server name and choose "Edit SQL Server Registration properties..."
Set it to "Use SQL Server authentication" and clear the "Always prompt for login name and password" box.
0
 
LVL 1

Author Comment

by:ort11
ID: 12309041
Thanks for the info, allready been checked.  This is set as described in the previous message.  Logins are still failing.  For some reason Enterprise Manager is tryng the Windows Login, over and over.

Thanks
0
 
LVL 15

Expert Comment

by:jdlambert1
ID: 12309131
Hmm. Try turning off the SQL Server Agent service for a few minutes, just as a test. Do the login attempts stop?

Does each client have up-to-date anti-virus doing full scans regularly? If so, when was the last?
0
Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

 
LVL 1

Author Comment

by:ort11
ID: 12309505
Ok, we might be able to do this, but I have pretty much seen that when the user closes the enterprise manager on their client, the logging stops.

What are we looking for if we stop the agent?   Logging to stop?
Thanks
0
 
LVL 15

Expert Comment

by:jdlambert1
ID: 12310431
I haven't been able to find or think of any reason why all those logins attempts should be occuring, and the first thing I think of when I here something like "a lot of unexplained login attempts", I think of malware. If you have malware, it could be on your workstations or the SQL Server. If it's on the server, it could be making use of the Agent, which you could rule out if you turn it off a few minutes and the logon attempts continue. Involvement of Agent is unlikely, but it's easy to rule it out.

Also, spyware and adware haven't been guarded against by most anti-virus programs, but many of them are getting far more aggressive, and some of them are already using virus-like actions to make it hard to remove from the system.

These may be long-shots, but any time there is suspicous activity (and yours is suspicous), systems should be double-checked to see if they may have been compromised.

You might also have your network guys audit your firewall logs for suspcious activity.
0
 
LVL 1

Author Comment

by:ort11
ID: 12446729
Thanks all, this is still happening with no resolution in site.

Thanks
Jeff O
0
 
LVL 1

Author Comment

by:ort11
ID: 12725864
Hi:  I would like to try and keep tihs one open.  Here are some of the events that we are seeing...

2004-12-01 00:00:03      Daemon.Error      DWSQL      Security: NT AUTHORITY\SYSTEM: The logon to account: someuser by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 from workstation: syslog-pc failed. The error code was: 3221225572
2004-12-01 00:00:03      Daemon.Error      DWSQL      Security: NT AUTHORITY\SYSTEM: The logon to account: someuser by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 from workstation: syslog-pc failed. The error code was: 3221225572
2004-12-01 00:00:03      Daemon.Error      DWSQL      Security: NT AUTHORITY\SYSTEM: Logon Failure: Reason: Unknown user name or bad password User Name: someuser Domain: syslog-pc Logon Type: 3 Logon Process: NtLmSsp Authentication Package: NTLM Workstation Name: syslog-pc
2004-12-01 00:00:03      Daemon.Error      DWSQL      Security: NT AUTHORITY\SYSTEM: Logon Failure: Reason: Unknown user name or bad password User Name: someuser Domain: syslog-pc Logon Type: 3 Logon Process: NtLmSsp Authentication Package: NTLM Workstation Name: syslog-pc
2004-12-01 00:00:03      Daemon.Error      DWSQL      Security: NT AUTHORITY\SYSTEM: Logon Failure: Reason: Unknown user name or bad password User Name: someuser Domain: syslog-pc Logon Type: 3 Logon Process: NtLmSsp Authentication Package: NTLM Workstation Name: syslog-pc
2004-12-01 00:00:08      Daemon.Error      DWSQL      Security: NT AUTHORITY\SYSTEM: The logon to account: someuser by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 from workstation: syslog-pc failed. The error code was: 3221225572
2004-12-01 00:00:08      Daemon.Error      DWSQL      Security: NT AUTHORITY\SYSTEM: The logon to account: someuser by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 from workstation: syslog-pc failed. The error code was: 3221225572
2004-12-01 00:00:08      Daemon.Error      DWSQL      Security: NT AUTHORITY\SYSTEM: Logon Failure: Reason: Unknown user name or bad password User Name: someuser Domain: syslog-pc Logon Type: 3 Logon Process: NtLmSsp Authentication Package: NTLM Workstation Name: syslog-pc
2004-12-01 00:00:08      Daemon.Error      DWSQL      Security: NT AUTHORITY\SYSTEM: Logon Failure: Reason: Unknown user name or bad password User Name: someuser Domain: syslog-pc Logon Type: 3 Logon Process: NtLmSsp Authentication Package: NTLM Workstation Name: syslog-pc
2004-12-01 00:00:08      Daemon.Error      DWSQL      Security: NT AUTHORITY\SYSTEM: Logon Failure: Reason: Unknown user name or bad password User Name: someuser Domain: syslog-pc Logon Type: 3 Logon Process: NtLmSsp Authentication Package: NTLM Workstation Name: syslog-pc


This is happening every 5 mins from any machine that has Enterprise Manager with an Database Authentication to any SQL machine that does not have a matching Windows Username / Password.

0
 
LVL 1

Accepted Solution

by:
ort11 earned 0 total points
ID: 12845515
In every enterprise manager turn off polling via tools / options.

This fixes the issue.

0

Featured Post

Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

Join & Write a Comment

Suggested Solutions

This article describes some very basic things about SQL Server filegroups.
Using SQL Scripts we can save all the SQL queries as files that we use very frequently on our database later point of time. This is one of the feature present under SQL Workshop in Oracle Application Express.
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

759 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now