none
Клиентская машина на Windows 10 RRS feed

  • Общие обсуждения

  • Добрый день. Есть проблема в компании, с тем что обновив, свой компьютер до Windows 10, завел машину в домен.

    Все работает, все рады. Но как только начал подгружаться профиль, он начал ругаться, на то, что у него нет доступа к домен контроллеру. А именно, в папки Netlogon и Sysvol. Пишет отказано в доступе. Ввожу свои данные, все равно не дает доступ. Ввожу данные админа, такая же проблема. Хотелось бы узнать в чем проблема. Заранее спасибо за помощь.

    1 октября 2015 г. 9:38

Все ответы

  • Посмотрите журналы на предмет ошибок аудита входа и опубликуйте результаты

    The opinion expressed by me is not an official position of Microsoft

    1 октября 2015 г. 13:37
    Модератор
  • Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          10/2/2015 6:26:37 AM
    Event ID:      4624
    Task Category: Logon
    Level:         Information
    Keywords:      Audit Success
    User:          N/A
    Computer:      OLZHASDC16.sawa.kz
    Description:
    An account was successfully logged on.

    Subject:
    Security ID: NULL SID
    Account Name: -
    Account Domain: -
    Logon ID: 0x0

    Logon Information:
    Logon Type: 3
    Restricted Admin Mode: -
    Virtual Account: No
    Elevated Token: Yes

    Impersonation Level: Impersonation

    New Logon:
    Security ID: SAWA\o.absemetov
    Account Name: o.absemetov
    Account Domain: SAWA
    Logon ID: 0x196F0E
    Linked Logon ID: 0x0
    Network Account Name: -
    Network Account Domain: -
    Logon GUID: {00000000-0000-0000-0000-000000000000}

    Process Information:
    Process ID: 0x0
    Process Name: -

    Network Information:
    Workstation Name: AWKS179
    Source Network Address: 192.168.1.99
    Source Port: 64982

    Detailed Authentication Information:
    Logon Process: NtLmSsp 
    Authentication Package: NTLM
    Transited Services: -
    Package Name (NTLM only): NTLM V2
    Key Length: 128

    This event is generated when a logon session is created. It is generated on the computer that was accessed.

    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 occurred. The most common types are 2 (interactive) and 3 (network).

    The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

    The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

    The impersonation level field indicates the extent to which a process in the logon session can impersonate.

    The authentication information fields provide detailed information about this specific logon request.
    - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
    - 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>4624</EventID>
        <Version>2</Version>
        <Level>0</Level>
        <Task>12544</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8020000000000000</Keywords>
        <TimeCreated SystemTime="2015-10-02T13:26:37.577011500Z" />
        <EventRecordID>4586</EventRecordID>
        <Correlation ActivityID="{02150CEA-FD0B-0002-130D-15020BFDD001}" />
        <Execution ProcessID="568" ThreadID="604" />
        <Channel>Security</Channel>
        <Computer>OLZHASDC16.sawa.kz</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-5-21-2738172563-1956931380-1179964481-1105</Data>
        <Data Name="TargetUserName">o.absemetov</Data>
        <Data Name="TargetDomainName">SAWA</Data>
        <Data Name="TargetLogonId">0x196f0e</Data>
        <Data Name="LogonType">3</Data>
        <Data Name="LogonProcessName">NtLmSsp </Data>
        <Data Name="AuthenticationPackageName">NTLM</Data>
        <Data Name="WorkstationName">AWKS179</Data>
        <Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
        <Data Name="TransmittedServices">-</Data>
        <Data Name="LmPackageName">NTLM V2</Data>
        <Data Name="KeyLength">128</Data>
        <Data Name="ProcessId">0x0</Data>
        <Data Name="ProcessName">-</Data>
        <Data Name="IpAddress">192.168.1.99</Data>
        <Data Name="IpPort">64982</Data>
        <Data Name="ImpersonationLevel">%%1833</Data>
        <Data Name="RestrictedAdminMode">-</Data>
        <Data Name="TargetOutboundUserName">-</Data>
        <Data Name="TargetOutboundDomainName">-</Data>
        <Data Name="VirtualAccount">%%1843</Data>
        <Data Name="TargetLinkedLogonId">0x0</Data>
        <Data Name="ElevatedToken">%%1842</Data>
      </EventData>
    </Event>
    2 октября 2015 г. 6:28