Logon failure every day from SID s-1-0-0 which refers to a nobody account What is causing it?

Posted on 2009-12-18
Last Modified: 2013-11-30
I get this event on both DC's in my network every day at about 4 hr intervals.
I can't seem to find the cause. obviously there isnt an account named Nobody on the workstation that is making the failed network logon attempt. Port 3732 isnt a well known port. Can anyone help?
Thank You in advance.

Event Log:  Security Event Source:  Microsoft-Windows-Security-Auditing Event ID:  4625 Research  
Severity: Failure Audit
Details: An account failed to log on.

       Security ID:              S-1-0-0
       Account Name:              -
       Account Domain:              -
       Logon ID:              0x0

Logon Type:                     3

Account For Which Logon Failed:
       Security ID:              S-1-0-0
       Account Name:              
       Account Domain:              

Failure Information:
       Failure Reason:              An Error occured during Logon.
       Status:                     0xc000006d
       Sub Status:              0xc0000133

Process Information:
       Caller Process ID:       0x0
       Caller Process Name:       -

Network Information:
       Workstation Name:       -
       Source Network Address:
       Source Port:              3732

Detailed Authentication Information:
       Logon Process:              Kerberos
       Authentication Package:       Kerberos
       Transited Services:       -
       Package Name (NTLM only):       -
       Key Length:              0
Question by:conlin
    LVL 16

    Expert Comment

    by:Ady Foot
    According to the following Microsoft knowledgebase article, the SID S-1-0-0 means 'Nobody' which is interesting....

    This could be a problem with the computer account on the domain.  Try removing the machine from the domain and then re-adding it; this could help.  Also make sure that the time service on the workstation is set to receive its time updates from your domain controller.  This can cause kerberos authentication issues.



    Accepted Solution

    The logon failure comes from different machines at different times of the day.  Time service is fine. and some of the machines have been removed and rejoined to the domain some haven't, Still the same issue. Added logon as a service to the quickbooksDB user, and logon failures stopped for that machine.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Highfive Gives IT Their Time Back

    Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

    Transferring data across the virtual world became simpler but protecting it is becoming a real security challenge.  How to approach cyber security  in today's business world!
    Envision that you are chipping away at another e-business site with a team of pundit developers and designers. Everything seems, by all accounts, to be going easily.
    After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
    Here's a very brief overview of the methods PRTG Network Monitor ( offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

    758 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

    11 Experts available now in Live!

    Get 1:1 Help Now