Question Locked

Event ID 529

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm constantly getting this error from our SBS 2003:

Source Event ID Last Occurrence Total Occurrences
Security
529 22-06-2007 03:51 62 *
Logon Failure:
Reason: Unknown user name or bad password
User Name: ?Username?
Domain: ?Domain?
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: ?Computer name?
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: 192.168.1.40
Source Port: 3122

Is someone trying to do a dictionary attack on our network or?

3 replies

by cg it

is this a XP machine? if so is it SP2?

also do you have the latest SP and hotfixes for W2003?

local logon with an incorrect user name or password will generate a 529 error in the logs.

for instance a user that forgets to make sure that they are logging on to the domain and not the local machine, have the local machine as where to log on to, then try their domain user account. An event 529 is then logged.

A dictionary attack, you will see 1000s of bad user name or password events in the event log in a very short period of time. further, your perimeter firewall had to have been breached [unless its being done on the lan]. So if your monitoring your perimeter firewall, you'll see heavy inbound traffic .

by rwright142

I'm getting these too, but thousands a day. They try hitting us very early and they use names that are not on our domain. Here's an example:
Logon Failure:
Reason: Unknown user name or bad password User Name: stephen
Domain: (ourdoamin)
Logon Type: 8 Logon Process: IIS Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 Workstation Name: (one of our DCs)
Caller User Name: (one of our DCs computername)$
Caller Domain: (our domain)
Caller Logon ID: (0x0,0x3E7)
Caller Process ID: 1864
Transited Services: -
Source Network Address: -
Source Port: -

How can I prevent these? It's a dictionary attack but how can I find out where it is coming from so I can block it?

This discussion is closed to new replies.