- Joined
- Feb 27, 2008
- Messages
- 8,708 (1.48/day)
System Name | OrangeHaze / Silence |
---|---|
Processor | i7-13700KF / i5-10400 / |
Motherboard | ROG STRIX Z690-E / MSI Z490 A-Pro Motherboard |
Cooling | Corsair H75 / TT ToughAir 510 |
Memory | 64Gb GSkill Trident Z5 / 32GB Team Dark Za 3600 |
Video Card(s) | Palit GeForce RTX 2070 / Sapphire R9 290 Vapor-X 4Gb |
Storage | Hynix Plat P41 2Tb\Samsung MZVL21 1Tb / Samsung 980 Pro 1Tb |
Display(s) | 22" Dell Wide/24" Asus |
Case | Lian Li PC-101 ATX custom mod / Antec Lanboy Air Black & Blue |
Audio Device(s) | SB Audigy 7.1 |
Power Supply | Corsair Enthusiast TX750 |
Mouse | Logitech G502 Lightspeed Wireless / Logitech G502 Proteus Spectrum |
Keyboard | K68 RGB — CHERRY® MX Red |
Software | Win10 Pro \ RIP:Win 7 Ult 64 bit |
I wonder if we need a server section....
Anyway. I've got a series of error messages on one server (of two) in a location. This is a Terminal Services server, located in the same facility as its DC. There are error messages popping multiple times a second on one of my servers, and can't seem to tie it down specifically. These particular errors occurred 24 times in the same second, between the three of them, repeated.
Items in Blue italics are changed to spare the not-so-innocent, and also indicate what they represent, ie "SERVERNAME" is the actual server name, etc.
What appears significant to me is the $ after the server name in the first error message, but I don't know what it indicates.... By that I mean that it looks like it could be a share process, since the system generated shares can put a $ in the share name, but I'm not sure....Any M$ server geniuses have any ideas? Thanks for looking and tasking those big brains!!
Anyway. I've got a series of error messages on one server (of two) in a location. This is a Terminal Services server, located in the same facility as its DC. There are error messages popping multiple times a second on one of my servers, and can't seem to tie it down specifically. These particular errors occurred 24 times in the same second, between the three of them, repeated.
Items in Blue italics are changed to spare the not-so-innocent, and also indicate what they represent, ie "SERVERNAME" is the actual server name, etc.
What appears significant to me is the $ after the server name in the first error message, but I don't know what it indicates.... By that I mean that it looks like it could be a share process, since the system generated shares can put a $ in the share name, but I'm not sure....Any M$ server geniuses have any ideas? Thanks for looking and tasking those big brains!!
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 1/10/2017 3:06:19 PM
Event ID: 4771
Task Category: Kerberos Authentication Service
Level: Information
Keywords: Audit Failure
User: N/A
Computer: FULL.Server.Name
Description:
Kerberos pre-authentication failed.
Account Information:
Security ID: DOMAIN\SERVERNAME$
Account Name: SERVERNAME$
Service Information:
Service Name: krbtgt/DOMAIN.NAME
Network Information:
Client Address: ::1
Client Port: 0
Additional Information:
Ticket Options: 0x40810010
Failure Code: 0x18
Pre-Authentication Type: 2
Certificate Information:
Certificate Issuer Name:
Certificate Serial Number:
Certificate Thumbprint:
Certificate information is only provided if a certificate was used for pre-authentication.
Pre-authentication types, ticket options and failure codes are defined in RFC 4120.
If the ticket was malformed or damaged during transit and could not be decrypted, then many fields in this event might not be present.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4771</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>14339</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2017-01-10T20:06:19.664595600Z" />
<EventRecordID>13461329</EventRecordID>
<Correlation />
<Execution ProcessID="1004" ThreadID="16664" />
<Channel>Security</Channel>
<Computer>FULL.Server.Name</Computer>
<Security />
</System>
<EventData>
<Data Name="TargetUserName">SERVERNAME$</Data>
<Data Name="TargetSid">S-1-5-21-1979150871-126566477-2868468453-1104</Data>
<Data Name="ServiceName">krbtgt/DOMAIN.NAME</Data>
<Data Name="TicketOptions">0x40810010</Data>
<Data Name="Status">0x18</Data>
<Data Name="PreAuthType">2</Data>
<Data Name="IpAddress">::1</Data>
<Data Name="IpPort">0</Data>
<Data Name="CertIssuerName">
</Data>
<Data Name="CertSerialNumber">
</Data>
<Data Name="CertThumbprint">
</Data>
</EventData>
</Event>
Source: Microsoft-Windows-Security-Auditing
Date: 1/10/2017 3:06:19 PM
Event ID: 4771
Task Category: Kerberos Authentication Service
Level: Information
Keywords: Audit Failure
User: N/A
Computer: FULL.Server.Name
Description:
Kerberos pre-authentication failed.
Account Information:
Security ID: DOMAIN\SERVERNAME$
Account Name: SERVERNAME$
Service Information:
Service Name: krbtgt/DOMAIN.NAME
Network Information:
Client Address: ::1
Client Port: 0
Additional Information:
Ticket Options: 0x40810010
Failure Code: 0x18
Pre-Authentication Type: 2
Certificate Information:
Certificate Issuer Name:
Certificate Serial Number:
Certificate Thumbprint:
Certificate information is only provided if a certificate was used for pre-authentication.
Pre-authentication types, ticket options and failure codes are defined in RFC 4120.
If the ticket was malformed or damaged during transit and could not be decrypted, then many fields in this event might not be present.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4771</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>14339</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2017-01-10T20:06:19.664595600Z" />
<EventRecordID>13461329</EventRecordID>
<Correlation />
<Execution ProcessID="1004" ThreadID="16664" />
<Channel>Security</Channel>
<Computer>FULL.Server.Name</Computer>
<Security />
</System>
<EventData>
<Data Name="TargetUserName">SERVERNAME$</Data>
<Data Name="TargetSid">S-1-5-21-1979150871-126566477-2868468453-1104</Data>
<Data Name="ServiceName">krbtgt/DOMAIN.NAME</Data>
<Data Name="TicketOptions">0x40810010</Data>
<Data Name="Status">0x18</Data>
<Data Name="PreAuthType">2</Data>
<Data Name="IpAddress">::1</Data>
<Data Name="IpPort">0</Data>
<Data Name="CertIssuerName">
</Data>
<Data Name="CertSerialNumber">
</Data>
<Data Name="CertThumbprint">
</Data>
</EventData>
</Event>
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 1/10/2017 3:06:19 PM
Event ID: 4776
Task Category: Credential Validation
Level: Information
Keywords: Audit Failure
User: N/A
Computer: FULL.Computer.Name
Description:
The computer attempted to validate the credentials for an account.
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon Account: SERVERNAME
Source Workstation: SERVERNAME
Error Code: 0xC0000064
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4776</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>14336</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2017-01-10T20:06:19.664595600Z" />
<EventRecordID>13461330</EventRecordID>
<Correlation />
<Execution ProcessID="1004" ThreadID="16664" />
<Channel>Security</Channel>
<Computer>FULL.Server.Name</Computer>
<Security />
</System>
<EventData>
<Data Name="PackageName">MICROSOFT_AUTHENTICATION_PACKAGE_V1_0</Data>
<Data Name="TargetUserName">SERVERNAME</Data>
<Data Name="Workstation">SERVERNAME</Data>
<Data Name="Status">0xc0000064</Data>
</EventData>
</Event>
Source: Microsoft-Windows-Security-Auditing
Date: 1/10/2017 3:06:19 PM
Event ID: 4776
Task Category: Credential Validation
Level: Information
Keywords: Audit Failure
User: N/A
Computer: FULL.Computer.Name
Description:
The computer attempted to validate the credentials for an account.
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon Account: SERVERNAME
Source Workstation: SERVERNAME
Error Code: 0xC0000064
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4776</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>14336</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2017-01-10T20:06:19.664595600Z" />
<EventRecordID>13461330</EventRecordID>
<Correlation />
<Execution ProcessID="1004" ThreadID="16664" />
<Channel>Security</Channel>
<Computer>FULL.Server.Name</Computer>
<Security />
</System>
<EventData>
<Data Name="PackageName">MICROSOFT_AUTHENTICATION_PACKAGE_V1_0</Data>
<Data Name="TargetUserName">SERVERNAME</Data>
<Data Name="Workstation">SERVERNAME</Data>
<Data Name="Status">0xc0000064</Data>
</EventData>
</Event>
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 1/10/2017 3:06:19 PM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: FULL.Server.Name
Description:
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: SERVERNAME
Account Domain: DOMAIN
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: SERVERNAME
Source Network Address: ::1
Source Port: 54483
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4625</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2017-01-10T20:06:19.664595600Z" />
<EventRecordID>13461331</EventRecordID>
<Correlation />
<Execution ProcessID="1004" ThreadID="16664" />
<Channel>Security</Channel>
<Computer>FULL.Server.Name</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-0-0</Data>
<Data Name="SubjectUserName">-</Data>
<Data Name="SubjectDomainName">-</Data>
<Data Name="SubjectLogonId">0x0</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">SERVERNAME</Data>
<Data Name="TargetDomainName">DOMAIN</Data>
<Data Name="Status">0xc000006d</Data>
<Data Name="FailureReason">%%2313</Data>
<Data Name="SubStatus">0xc0000064</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">NtLmSsp </Data>
<Data Name="AuthenticationPackageName">NTLM</Data>
<Data Name="WorkstationName">SGFS1</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x0</Data>
<Data Name="ProcessName">-</Data>
<Data Name="IpAddress">::1</Data>
<Data Name="IpPort">54483</Data>
</EventData>
</Event>
Source: Microsoft-Windows-Security-Auditing
Date: 1/10/2017 3:06:19 PM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: FULL.Server.Name
Description:
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: SERVERNAME
Account Domain: DOMAIN
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: SERVERNAME
Source Network Address: ::1
Source Port: 54483
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4625</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2017-01-10T20:06:19.664595600Z" />
<EventRecordID>13461331</EventRecordID>
<Correlation />
<Execution ProcessID="1004" ThreadID="16664" />
<Channel>Security</Channel>
<Computer>FULL.Server.Name</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-0-0</Data>
<Data Name="SubjectUserName">-</Data>
<Data Name="SubjectDomainName">-</Data>
<Data Name="SubjectLogonId">0x0</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">SERVERNAME</Data>
<Data Name="TargetDomainName">DOMAIN</Data>
<Data Name="Status">0xc000006d</Data>
<Data Name="FailureReason">%%2313</Data>
<Data Name="SubStatus">0xc0000064</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">NtLmSsp </Data>
<Data Name="AuthenticationPackageName">NTLM</Data>
<Data Name="WorkstationName">SGFS1</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x0</Data>
<Data Name="ProcessName">-</Data>
<Data Name="IpAddress">::1</Data>
<Data Name="IpPort">54483</Data>
</EventData>
</Event>
Last edited: