We help IT Professionals succeed at work.

Windows Network logon (Type 3) failure internal to workstation by disabled "Guest" account.

Fred Marshall
I'm still chasing 4625 failed logons (Type 3) as in:

This is a slightly different instance of the reports I'm getting:
Reported Username is Guest on a computer where the Guest account is inactivated.
Reported "Remote Device" is the workstation itself - not another one.
Reported "Domain" is the same workstation name - not another one.

So, yes, attempts to logon with Guest should fail because Guest is inactivated.
But why would a workstation be having logon attempts unto itself when I think if Guest as being a Network logon attempt.
And, yes, these are "network logons" (Type 3, right?).
So why are they coming from within the workstation?

In this case, it happened on Friday starting around time for people to come to work at 8:30  and it persisted until 11:50.  There were over 400 events, some of which occurred within the same second - spaced variably with gaps up to an hour.

This is happening on a few workstations, although not to this degree.
In this case, it's not an "old credential".and yet the results are very similar to the earlier question's situation.

I still haven't found the smoking gun.
Watch Question

Kent WSr. Network / Systems Admin

On the event log entry, have you checked the Failure Information Status and Sub Status code?
That may give more of a clue. You can check the codes here:

Kent W:  Thanks for the suggestion!  While it didn't lead me to a fix, it did lead my research to this:

Running PsExec and then keymgr, displayed the hidden credentials and allowed them to be removed.
Kent WSr. Network / Systems Admin

That is awesome. I'm glad you were at least pointed in the right direction.


Thanks again!


I'm going to open the same question as what I found was about hidden credentials and NOT really to the point of this question which was about Guest attempts.