This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
According to this c0000413 means STATUS_AUTHENTICATION_FIREWALL_FAILED - "Logon Failure: The machine you are logging onto is protected by an authentication firewall. The specified account is not allowed to authenticate to the machine" - this link seems to have some causes for this error
Windows Authentication and Multiple Domains
Here is some additional info:
- I've add DOMAIN A\Domain Users to the Permissions on the website and gave it Full Control -- just to see if I could get around this but it doesn't work.
- Whenever there is a login failure from a user in Domain A, I notice that Event Log logs a Error Event ID 4625 giving the details of the account, domainA, Status: 0xc0000413
- App Pool - Process Model is set to NetworkService
To resolve the issue, I had to open up AD Users and Computers --> enable Advanced Features --> Select the Computer Object --> Properties --> Security --> Add the Group I want to allow access to the computer (in this case, DomainA\Domain users) and allow "Allowed to Authenticate
Make sure the user is a member of this group
I've a similar problem with an exchange-servern - but everytime i add this group as mentioned above it disappears after 1 hour....
ReplyDeleteAny ideas?
does it get overwritten by another AD server?
ReplyDeleteThank you bro,
ReplyDeleteit solved my issue