R
RHCJMO
Problem: Domain account is not allowed to access secondary drives that have been added to a fresh installation.
Troubleshooting:
1) Verified the issue is security related. Cannot browse via cmd to any directories, receive "Access Denied" errors. However, when I run CMD elevated (as admin), or run Server Manager elevated, I can access the drives (via Disk Management with the latter). Also verified domain user is added to the local administrators group. Copy of error:
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 11/21/2017 8:34:41 AM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: SERVER.DOMAIN.com
Description:
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: SERVER$
Account Domain: DOMAIN
Logon ID: 0x3E7
Logon Type: 7
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: ACCOUNT
Account Domain: DOMAIN
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC000006A
Process Information:
Caller Process ID: 0x1d0
Caller Process Name: C:\Windows\System32\winlogon.exe
Network Information:
Workstation Name: SERVER
Source Network Address: 127.0.0.1
Source Port: 0
Detailed Authentication Information:
Logon Process: User32
Authentication Package: Negotiate
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-11-21T16:34:41.447300300Z" />
<EventRecordID>24944</EventRecordID>
<Correlation />
<Execution ProcessID="528" ThreadID="1104" />
<Channel>Security</Channel>
<Computer>SERVER.DOMAIN.com</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-18</Data>
<Data Name="SubjectUserName">SERVER$</Data>
<Data Name="SubjectDomainName">DOMAIN</Data>
<Data Name="SubjectLogonId">0x3e7</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">ACCOUNT</Data>
<Data Name="TargetDomainName">DOMAIN</Data>
<Data Name="Status">0xc000006d</Data>
<Data Name="FailureReason">%%2313</Data>
<Data Name="SubStatus">0xc000006a</Data>
<Data Name="LogonType">7</Data>
<Data Name="LogonProcessName">User32 </Data>
<Data Name="AuthenticationPackageName">Negotiate</Data>
<Data Name="WorkstationName">SERVER</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x1d0</Data>
<Data Name="ProcessName">C:\Windows\System32\winlogon.exe</Data>
<Data Name="IpAddress">127.0.0.1</Data>
<Data Name="IpPort">0</Data>
</EventData>
</Event>
Also, I was able to access the drive's administrative share remotely using the same account without issue.
2) Manually added domain user to the security permissions of the specific drives with "Full" permissions. Ran "Effective Access" permission analysis which shows the user account in question has full permissions to the drives. Issue persists.
3) Additionally, disabled hot-plug function on drives for VMware.
This issue is also appearing on a new Server 2016 VM. What am I missing here? It seems the system isn't detecting the admin permissions level of the account unless forced to, which is not usual.
Continue reading...
Troubleshooting:
1) Verified the issue is security related. Cannot browse via cmd to any directories, receive "Access Denied" errors. However, when I run CMD elevated (as admin), or run Server Manager elevated, I can access the drives (via Disk Management with the latter). Also verified domain user is added to the local administrators group. Copy of error:
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 11/21/2017 8:34:41 AM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: SERVER.DOMAIN.com
Description:
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: SERVER$
Account Domain: DOMAIN
Logon ID: 0x3E7
Logon Type: 7
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: ACCOUNT
Account Domain: DOMAIN
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC000006A
Process Information:
Caller Process ID: 0x1d0
Caller Process Name: C:\Windows\System32\winlogon.exe
Network Information:
Workstation Name: SERVER
Source Network Address: 127.0.0.1
Source Port: 0
Detailed Authentication Information:
Logon Process: User32
Authentication Package: Negotiate
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-11-21T16:34:41.447300300Z" />
<EventRecordID>24944</EventRecordID>
<Correlation />
<Execution ProcessID="528" ThreadID="1104" />
<Channel>Security</Channel>
<Computer>SERVER.DOMAIN.com</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-18</Data>
<Data Name="SubjectUserName">SERVER$</Data>
<Data Name="SubjectDomainName">DOMAIN</Data>
<Data Name="SubjectLogonId">0x3e7</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">ACCOUNT</Data>
<Data Name="TargetDomainName">DOMAIN</Data>
<Data Name="Status">0xc000006d</Data>
<Data Name="FailureReason">%%2313</Data>
<Data Name="SubStatus">0xc000006a</Data>
<Data Name="LogonType">7</Data>
<Data Name="LogonProcessName">User32 </Data>
<Data Name="AuthenticationPackageName">Negotiate</Data>
<Data Name="WorkstationName">SERVER</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x1d0</Data>
<Data Name="ProcessName">C:\Windows\System32\winlogon.exe</Data>
<Data Name="IpAddress">127.0.0.1</Data>
<Data Name="IpPort">0</Data>
</EventData>
</Event>
Also, I was able to access the drive's administrative share remotely using the same account without issue.
2) Manually added domain user to the security permissions of the specific drives with "Full" permissions. Ran "Effective Access" permission analysis which shows the user account in question has full permissions to the drives. Issue persists.
3) Additionally, disabled hot-plug function on drives for VMware.
This issue is also appearing on a new Server 2016 VM. What am I missing here? It seems the system isn't detecting the admin permissions level of the account unless forced to, which is not usual.
Continue reading...