• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 190
  • Last Modified:

Security Log

I noticed in the security logs, I will sometimes see an error code 681 with the (Logon to account: anonymous)
What does the anonymous mean in this case and why does it show up instead of a user account name.

Thanks
0
vivo123
Asked:
vivo123
  • 7
  • 4
  • 2
  • +1
1 Solution
 
Zaheer IqbalTechnical Assurance & ImplementationCommented:
Is this an IIS server or FTP..
This is why u are getting them Anonymous user logs into to FTP etc..
They are being Audited so that why ther are there..
0
 
vivo123Author Commented:
No on either..  These are showing up on individual workstations.  But I can not figure out why the anonymous user ID.

Event ID 681
The logon to account: anonymous
by: Microsoft_Authentication_Package_V1_0
from workstation: test1
failed
The error code was 3221225572
0
 
AlexdelenCommented:
http://support.microsoft.com/kb/q305822/

there you go

Greets

Alex
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
vivo123Author Commented:
I still don't see an explanation for the anonymous logon.  These are workstations that are user assigned nobody else logs in.  They are running XP Pro SP1 completely patched.

0
 
Zaheer IqbalTechnical Assurance & ImplementationCommented:
Are you sure they are not running the FTP service??
0
 
AlexdelenCommented:
yeah the only thing I see is that you have an FTP running too.

Check your services for any ftp like service.
0
 
vivo123Author Commented:
Thanks I will take a look
0
 
Dave_DietzCommented:
I would guess that this is someone trying to access a file share on the target machine that they don't have access to.  They will be prompted for credentials - in this case it looks like they are typing in 'anonymous' in hopes of gaining access.

The specific error code you see resolves to the following: 3221225572 - User logon with misspelled or bad user account

If test1 is a machine on your domain you may want to speak to the assigned user to see what they are up to. If the machine is *not* on your domain you either have a rogue/non-domain machine attached to your network or you may have NetBIOS ports open somewhere that someone is poking through on a fishing expedition.

This is different than 'NT AUTHORITY/ANONYMOUS' which is a machine trying to make a connection to another machine with *no* credentials.  It also almost certainly has nothing to do with IIS since the 'Anonymous' account is actually IUSR_<machinename> by default.

Dave Dietz

0
 
vivo123Author Commented:
Thanks Dave for the explanantion..  I am going to check further.  Is there any other type auditing that could be set to help break this down farther.
0
 
Dave_DietzCommented:
Without specific knowledge of where the requests are coming from, short of a network trace I can't think of any additional logging that would really help.

It appears that the culprit is not able to access the machines so auditing file access would be pointless, and if you don't know what machine is launching the requests you're going to have a *lot* of data to dig through if you enable any kind of domain wide auditing of user activity.

Dave Dietz
0
 
vivo123Author Commented:
FrontPage is installed on the suspected machines.  Do you think this could be a possiblility??  I am reaching..

Thanks again..

0
 
Dave_DietzCommented:
Not likely but not impossible.

How many 'suspected' machine are there?

If there are just a few it may be feasible to perform some network tracing to see what they are doing.....

Dave Dietz
0
 
vivo123Author Commented:
3 suspected machines...

Can you explain further on the network tracing?  
0
 
Dave_DietzCommented:
You could set up a network sniffer and configure it to only listen for traffic to and from the suspected machines.

Once you see the suspect bahavior on a target machine you can go through the netmon trace and see what exactly the machine has been doing on the network.

You could also set up File and Object Auditing and/or Logon/Logoff Auditing on the suspect machines to see who is on the boxes and what they are accessing while they are on it.  A slightly more readicla approach would be to install a keylogger/screen capture type utility and see exactly what the machines are doing.

Dave Dietz
0
 
vivo123Author Commented:
Thanks for the info
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 7
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now