Dear Concern Person,

This is to inform you that I am not able to solve some the Event ID's can you please help here how to resolve the remediation it would be great help for me.

And also guide me if any further details are required.

Event ID : 4625,1008,1005,1006,2001

without more context (like the event source) an event ID is not very meaningfull

The only thing I can turn up with with your info is plausible guesses like:

4652 in security eventlog from source Windows-event-security-auditing is a failed user logon. Someone might have used a bad password.

Also other information in the event is crucial to understand the event and thus to help troubleshoot it's occurance. tackle them one by one to keep oversight.

Note that events as such are no issue, they are there to provide info on system behavior, including reported issues. Therefore you should not try to resolve an event, you should attempt to check if it is linked to an incident or issue and resolve the issue accord

Hi Thanks for responding,

We have issue with Event ID 4625 on Windows Server 2003 & Windows Server 2008

An account failed to log on.
Subject:
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:192.86.26.11
Source Port:55900
Detailed Authentication Information:
Logon Process:Kerberos
Authentication Package:Kerberos
Transited Services:-
Package Name (NTLM only):-
Key Length:0
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.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

Can you please guide where is the source information and how to remediate the issue.

Logon type 3 it's network logon, some device/workstation in your network tries to authenticate on DC. To have more information you can enable netlogon debug logging:

Start > Run > type in: nltest /dbflag:2080ffff > OK
After you restart Net Logon service, related activity may be logged to %windir%/debug/netlogon.log

I have already followed the above mentioned steps.

Please find the netlogon.log file and guide us further steps.

02/17 17:49:59 [MISC] DbFlag is set to 2080ffff
02/17 17:49:59 [CRITICAL] NlMainLoop: Registry changed
02/17 17:49:59 [INIT] Group Policy is not defined for Netlogon
02/17 17:49:59 [INIT] Following are the effective values after parsing
02/17 17:50:01 [MISC] DsGetDcName function called: Dom:boaibmadc1.IBM.BOA.COM Acct:(null) Flags: WRITABLE LDAPONLY DNS RET_DNS
02/17 17:50:01 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1
02/17 17:50:01 [CRITICAL] NetpDcGetNameIp: boaibmadc1.IBM.BOA.COM: No data returned from DnsQuery.
02/17 17:50:01 [MISC] NetpDcGetName: NetpDcGetNameIp returned 1355
02/17 17:50:01 [CRITICAL] NetpDcGetName: boaibmadc1.IBM.BOA.COM: IP and Netbios are both done.
02/17 17:50:01 [MISC] DsGetDcName function returns 1355: Dom:boaibmadc1.IBM.BOA.COM Acct:(null) Flags: WRITABLE LDAPONLY DNS RET_DNS
02/17 17:50:01 [MISC] DsGetDcName function called: Dom:BOAIBMPDC.IBM.BOA.COM Acct:(null) Flags: WRITABLE LDAPONLY DNS RET_DNS
02/17 17:50:01 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1
02/17 17:50:01 [CRITICAL] NetpDcGetNameIp: BOAIBMPDC.IBM.BOA.COM: No data returned from DnsQuery.
02/17 17:50:01 [MISC] NetpDcGetName: NetpDcGetNameIp returned 1355
02/17 17:50:01 [CRITICAL] NetpDcGetName: BOAIBMPDC.IBM.BOA.COM: IP and Netbios are both done.
02/17 17:50:01 [MISC] DsGetDcName function returns 1355: Dom:BOAIBMPDC.IBM.BOA.COM Acct:(null) Flags: WRITABLE LDAPONLY DNS RET_DNS
02/17 17:50:01 [MISC] DsGetDcName function called: Dom:BOAIBMPDC.IBM.BOA.COM Acct:(null) Flags: WRITABLE LDAPONLY DNS RET_DNS
02/17 17:50:01 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1
02/17 17:50:01 [MISC] NetpDcGetName: BOAIBMPDC.IBM.BOA.COM similar query failed recently 63
02/17 17:50:01 [MISC] DsGetDcName function returns 1355: Dom:BOAIBMPDC.IBM.BOA.COM Acct:(null) Flags: WRITABLE LDAPONLY DNS RET_DNS
02/17 17:50:01 [MISC] DsGetDcName function called: Dom:boaibmadc1.IBM.BOA.COM Acct:(null) Flags: WRITABLE LDAPONLY DNS RET_DNS
02/17 17:50:01 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1
02/17 17:50:01 [MISC] NetpDcGetName: boaibmadc1.IBM.BOA.COM similar query failed recently 63
02/17 17:50:01 [MISC] DsGetDcName function returns 1355: Dom:boaibmadc1.IBM.BOA.COM Acct:(null) Flags: WRITABLE LDAPONLY DNS RET_DNS
02/17 17:50:01 [MISC] DsGetDcName function called: Dom:BOAIBMPDC.IBM.BOA.COM Acct:(null) Flags: WRITABLE LDAPONLY DNS RET_DNS
02/17 17:50:01 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1
02/17 17:50:01 [MISC] NetpDcGetName: BOAIBMPDC.IBM.BOA.COM similar query failed recently 94
02/17 17:50:01 [MISC] DsGetDcName function returns 1355: Dom:BOAIBMPDC.IBM.BOA.COM Acct:(null) Flags: WRITABLE LDAPONLY DNS RET_DNS
02/17 17:50:01 [MISC] DsGetDcName function called: Dom: Acct:(null) Flags: DS RET_DNS
02/17 17:50:01 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1
02/17 17:50:01 [MISC] NetpDcGetName: IBM.BOA.COM. using cached information
02/17 17:50:01 [MISC] DsGetDcName function returns 0: Dom: Acct:(null) Flags: DS RET_DNS
02/17 17:50:01 [MISC] DsGetDcName function called: Dom: Acct:(null) Flags: DS RET_DNS
02/17 17:50:01 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1
02/17 17:50:01 [MISC] NetpDcGetName: IBM.BOA.COM. using cached information
02/17 17:50:01 [MISC] DsGetDcName function returns 0: Dom: Acct:(null) Flags: DS RET_DNS
02/17 17:50:13 [LOGON] SamLogon: Network logon of IBM\boahydsys from BOAIBMADC1 Entered
02/17 17:50:13 [LOGON] SamLogon: Network logon of IBM\boahydsys from BOAIBMADC1 Returns 0x0
02/17 17:50:34 [MISC] DsGetDcName function called: Dom:(null) Acct:(null) Flags: LDAPONLY RET_DNS
02/17 17:50:34 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1
02/17 17:50:34 [MISC] NetpDcGetName: IBM.BOA.COM. using cached information
02/17 17:50:34 [MISC] DsGetDcName function returns 0: Dom:(null) Acct:(null) Flags: LDAPONLY RET_DNS
02/17 17:50:46 [MISC] In control handler (Opcode: 4)
02/17 17:50:47 [MISC] In control handler (Opcode: 4)
02/17 17:50:55 [MISC] In control handler (Opcode: 4)
02/17 17:51:55 [MISC] In control handler (Opcode: 4)

Can you please check any one and guide.

I don't see any messages related to failed auth here, could you please confirm that Event ID 4625 is logged at the timeframe of provided netlogon.log?

can u guide me is there any other way to upload the log file .. because I am not able to share total log file here.