Problema com novo servidor

[Fernando Vieira_737981]

Amigos, temos um problema com um novo servidor onde trabalhamos.

Precisamos pegar "arquivos" do servidor A pelo programa porém o mesmo da falha no logon.

Eu consigo acessar normalmente o servidores, as pastas, criar e editar arquivos, porém quando tento puxar pelo programa especifico da esse problema.

Já fiz as permissões, já abri como ADM. Indicam algo?

[Fernando Vieira_737981]

Segue também o log de evento.
 

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          21/08/2019 11:01:29
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      JCsec-AP01.JallCard.Sec
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:        maxsys
    Account Domain:        SN-60825-DATACA

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:    SN-60825-DATACA
    Source Network Address:    192.168.12.52
    Source Port:        58041

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="2019-08-21T14:01:29.338670900Z" />
    <EventRecordID>42393</EventRecordID>
    <Correlation ActivityID="{81389B46-542A-0007-499B-38812A54D501}" />
    <Execution ProcessID="708" ThreadID="7416" />
    <Channel>Security</Channel>
    <Computer>JCsec-AP01.JallCard.Sec</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">maxsys</Data>
    <Data Name="TargetDomainName">SN-60825-DATACA</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">SN-60825-DATACA</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">192.168.12.52</Data>
    <Data Name="IpPort">58041</Data>
  </EventData>
</Event>

+ System 

  - Provider 

   [ Name]  Microsoft-Windows-Security-Auditing 
   [ Guid]  {54849625-5478-4994-A5BA-3E3B0328C30D} 
 
   EventID 4625 
 
   Version 0 
 
   Level 0 
 
   Task 12544 
 
   Opcode 0 
 
   Keywords 0x8010000000000000 
 
  - TimeCreated 

   [ SystemTime]  2019-08-21T14:01:29.338670900Z 
 
   EventRecordID 42393 
 
  - Correlation 

   [ ActivityID]  {81389B46-542A-0007-499B-38812A54D501} 
 
  - Execution 

   [ ProcessID]  708 
   [ ThreadID]  7416 
 
   Channel Security 
 
   Computer JCsec-AP01.JallCard.Sec 
 
   Security 
 

- EventData 

  SubjectUserSid S-1-0-0 
  SubjectUserName - 
  SubjectDomainName - 
  SubjectLogonId 0x0 
  TargetUserSid S-1-0-0 
  TargetUserName maxsys 
  TargetDomainName SN-60825-DATACA 
  Status 0xc000006d 
  FailureReason %%2313 
  SubStatus 0xc0000064 
  LogonType 3 
  LogonProcessName NtLmSsp  
  AuthenticationPackageName NTLM 
  WorkstationName SN-60825-DATACA 
  TransmittedServices - 
  LmPackageName - 
  KeyLength 0 
  ProcessId 0x0 
  ProcessName - 
  IpAddress 192.168.12.52 
  IpPort 58041 

[Fernando Vieira_737981]

Aqui onde trabalho existe 2 servidores e as maquinas puxam arquivos por exemplo do servidor 12.1 (antigo)
Migramos para um novo servidor 12.19 (novo) até ai tudo bem.
Porém o software que usamos ele é registrado no dominio para ter as permissões para puxar os arquivos. porém o mesmo puxa com um dominio "local" e não o dominio que foi dado a permissão:
log do servidor novo
Account For Which Logon Failed:

Security ID: NULL SID

Account Name: maxsys

Account Domain: SN-60825-DATACA

no account dominio deveria puxar com o dominio que liberei mas ele puxa com esse dominio local o que faz com que o servidor não autorize.
Acredito que não seja problema na estação local pois do servidor antigo puxa normalmente com o dominio da rede

[Fernando Vieira_737981]

Outra duvida é eu usando a mesma maquina para acessar os arquivos do servidor antigo ela entra com o dominio certo, e no novo servidor ela entra com dominio local. Teria como mudar o dominio pelo servidor dessa maquina que está tentando acessar?