none
Erro DNS - O adaptador de rede Ethernet0 não lista o servidor local como um servidor DNS RRS feed

  • Pergunta

  • Prezados, bom dia!

    Fiz uma replicação do DNS de um Windows Server 2008R2 para um Server 2012R2, porém ao rodar o BPA em ambas máquinas, deparei com o erro abaixo. Entrei no adaptador de rede e coloquei o DNS preferencial do Server 2008 com o IP do Sever 2012 e coloquei o secundário como ele mesmo e vice-versa em relação ao Server 2012. Porém continua dando esse erro abaixo.

    Outra coisa que reparei, mas não sei se aconteceu isso antes ou depois da replicação, é que a pasta _msdcs está duplicada e sua cópia está dentro da pasta do meu domínio e em cor de cinza sem informações e _msdcs principal está normal com todas as informações padrões.

    Peço lhe ajuda para corrigir esses problemas, pois realmente ainda não tenho o conhecimento analístico necessário para a solução.

    Muito obrigado e segue abaixo o erro e foto do _msdcs

    Problema:
    O adaptador de rede Ethernet0 não lista o servidor local como um servidor DNS; ou está configurado como o primeiro servidor DNS neste adaptador.

    Impacto:
    Se o endereço IP de loopback for a primeira entrada na lista de servidores DNS, o Active Directory poderá não encontrar seus parceiros de replicação.

    Resolução:
    Defina as configurações do adaptador para adicionar o endereço IP de loopback à lista de servidores DNS em todas as interfaces ativas, mas não como o primeiro servidor na lista.

    FOTO DO _MSDCS 

    segunda-feira, 25 de março de 2019 13:55

Respostas

  • Para solucionar o problema em questão, recomendo as verificações a seguir:

    Primeiramente, revisar todas as configurações de DNS nos Controladores de domínio:

    • Existe a zona reversa? Se não, crie (Reverse Lookup Zones/New Zone/Primary Zone/IPV4 Zone/Network ID:Ip da faixa de rede interna);
    • Nas propriedades do Servidor DNS, Aba Interfaces, em Listen On, marcar o Box "Only the Following IP Address, abaixo marcando o box correspondente a interface/IP utilizado no serviço DNS;
    • Nas zonas Primárias (Forward Lookup Zones), validar na aba Name Servers se constam os Nomes/IPs dos Servidores DNS/DCs, se não, adicionar.
    • Validar na aba Zone Transfers, se o box "Allow Zone Transfers" está marcado e logo abaixo, a opção "Only to Servers listed on the Name Servers Tab". Em seguida, clicar no botão Notify e marcar o box Automatically Notify e Servers Listed on the Name Servers Tab;
    • Pasta cinza _msdcs dentro da zona primária do domínio: Excluir a mesma. O ideal é que ela esteja na raiz de "Forward Lookup Zones". Caso não exista a zona _msdcs na raiz, a mesma pode ser recriada manualmente. 
    • Revisar as configrações de DNS primário e alternativo das placas de rede dos servidores, garantindo que o DNS primário de cada servidor seja o outro membro (no caso que tenha 2 controladores de domínio);
    • Mais detalhes: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731991(v%3dws.11)

    Após a revisão de configurações do DNS, é recomendado executar o Best Pratices Analyzer, para ver se ainda existe algum problema de configuração/funcionamento do serviço ou outro item que possa estar relacionado.

    Depois, recomendo que faça testes na replicação do SYSVOL. Se ainda existir problemas, pode ser necessário forçar a replicação, com orientação deste link: https://support.microsoft.com/en-in/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

    Se depois de tudo, ainda existir algum problema, poste logs de erro/warning gerado para que possamos avaliar de forma mais detalhada.


    Odirlei Souza | Analista de Suporte | MCP (70-290)

    • Sugerido como Resposta IgorFKModerator sexta-feira, 29 de março de 2019 17:14
    • Marcado como Resposta Adriano Monção segunda-feira, 1 de abril de 2019 11:15
    sexta-feira, 29 de março de 2019 14:19

Todas as Respostas

  • Boa tarde Adriano Monção,

    Tudo certo?

    Experimente inverter as configurações de DNS nos dois servidores; o que estiver como primário coloque em secundário e vice-versa e veja se o problema para de ocorrer.

    https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ff807362(v=ws.10) 

    Atenciosamente, 


    Igor F. Kunrath

    Esse conteúdo é fornecido sem garantias de qualquer tipo, seja expressa ou implícita

    Technet Community Support

    Por favor, lembre-se de Marcar como Resposta as postagens que resolveram o seu problema. Essa é uma maneira comum de reconhecer aqueles que o ajudaram e fazer com que seja mais fácil para os outros visitantes encontrarem a resolução mais tarde.

    segunda-feira, 25 de março de 2019 20:09
    Moderador
  • Prezados, bom dia!

    Fiz uma replicação do DNS de um Windows Server 2008R2 para um Server 2012R2, porém ao rodar o BPA em ambas máquinas, deparei com o erro abaixo. Entrei no adaptador de rede e coloquei o DNS preferencial do Server 2008 com o IP do Sever 2012 e coloquei o secundário como ele mesmo e vice-versa em relação ao Server 2012. Porém continua dando esse erro abaixo.

    Outra coisa que reparei, mas não sei se aconteceu isso antes ou depois da replicação, é que a pasta _msdcs está duplicada e sua cópia está dentro da pasta do meu domínio e em cor de cinza sem informações e _msdcs principal está normal com todas as informações padrões.

    Peço lhe ajuda para corrigir esses problemas, pois realmente ainda não tenho o conhecimento analístico necessário para a solução.

    Muito obrigado e segue abaixo o erro e foto do _msdcs

    Problema:
    O adaptador de rede Ethernet0 não lista o servidor local como um servidor DNS; ou está configurado como o primeiro servidor DNS neste adaptador.

    Impacto:
    Se o endereço IP de loopback for a primeira entrada na lista de servidores DNS, o Active Directory poderá não encontrar seus parceiros de replicação.

    Resolução:
    Defina as configurações do adaptador para adicionar o endereço IP de loopback à lista de servidores DNS em todas as interfaces ativas, mas não como o primeiro servidor na lista.

    FOTO DO _MSDCS 

    Aparentemente não há nada de errado no seu DNS, este comportamento de delegação da zona _msdsc é padrão quando o DNS é instalado automaticamente na promoção de um domain controller.

    O erro do BPA apenas indica que você deve fazer uso do IP de loopback nas interfaces conforme melhores práticas da Microsoft.

    DNS Preferencial - IP 

    DNS Alternativo - IP

    IP de loopback 127.0.0.1 (ultimo da lista). não obrigatório, não dará erro se não houver esta entrada, eu não uso esta configuração.

    https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ff807362(v=ws.10)

    Se de fato quer analisar a saúde do ambiente de AD é rodar as ferramentas e diagnostico e validação de replicação

    dcdiag /e /v 

    dcdiag /test:dns , entre outras , execute dcdiag /? para analisar as possibilidades.

    repadmin /showreps

    repadmin /replsum

    repadmin/? para na ajuda do comando.

    https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/manage/ad-ds-troubleshooting

    Question

    What is Microsoft’s best practice for where and how many DNS servers exist? What about for configuring DNS client settings on DC’s and members?

    https://blogs.technet.microsoft.com/askds/2010/07/17/friday-mail-sack-saturday-edition/#dnsbest


    "Se eu tivesse oito horas para derrubar uma árvore passaria seis afiando meu machado". Abraham Lincoln

    • Sugerido como Resposta IgorFKModerator terça-feira, 26 de março de 2019 14:07
    terça-feira, 26 de março de 2019 13:35
    Moderador
  • Boa tarde Felipe, muito obrigado pela resposta.

    Rodei o comando dcdiag /e /v consegui visualizar o erro que eu tinha mencionado em um outro post separado que é conforme abaixo. Tirando isso não apareceu nenhum erro a mais. Porém ainda tenho a dúvida sobre essa PASTA CINZA a mais do _msdcs. Porquê disso? E quando você fala para colocar mais um IP DNS, como incluí-lo sendo que só tenho duas opções, o principal e o alternativo.

    O processamento da Diretiva de Grupo falhou. O Windows tentou ler o arquivo \\ meu domínio \ sysvol \ meu dominio \ Policies \ {6AC1786C-016F-11D2-945F-00C04fB984F9} \ gpt.ini de um controlador de domínio e não obteve êxito. As configurações da Diretiva de Grupo não podem ser aplicadas até que esse evento seja resolvido. Esse problema pode ser transitório e pode ser causado por um ou mais dos seguintes procedimentos:
    a) Resolução de nomes / conectividade de rede para o controlador de domínio atual.
    b) Latência do serviço de replicação de arquivos (um arquivo criado em outro controlador de domínio não foi replicado para o controlador de domínio atual).
    c) O cliente do Sistema de Arquivos Distribuídos (DFS) foi desativado.


    terça-feira, 26 de março de 2019 17:18
  • Muito obrigado Igor pela resposta.

    Fiz o procedimento que você me sugeriu, porém não tive sucesso e erro ainda surge, de acordo com a resposta do Felipe esse erro ocorre quando não coloco o IP de loopback e em relação a essa PASTA CINZA a mais, como proceder?

    Muito obrigado!

    terça-feira, 26 de março de 2019 17:21
  • tudo indica um problema de DNS no ambiente ou sujeira de outros DCs removidos incorretamente. 

    envie o resultado dos comandos citados assim como a saída do comando ipconfig /all de cada DC.

    sobre o _msdsc zone :

    The _msdcs.ForestName subdomain hosts the domain controller locator DNS resource records for all the domain controllers in an Active Directory forest. It is also used to locate domain controllers that have specific roles in the Active Directory domain or in the Active Directory forest, and to locate a domain controller by searching for its GUID when a domain has been renamed.

    https://support.microsoft.com/pt-br/help/817470/how-to-reconfigure-an-msdcs-subdomain-to-a-forest-wide-dns-application


    "Se eu tivesse oito horas para derrubar uma árvore passaria seis afiando meu machado". Abraham Lincoln

    quarta-feira, 27 de março de 2019 12:46
    Moderador
  • Felipe, bom dia!

    Obrigado pela resposta.

    Em relação a PASTA CINZA _MSDSC, acredito que eu não consegui lhe passar a minha dúvida. Observe por gentileza a imagem no primeiro post, que existe uma zone _msdcs.eshm.local com a cor amarela normal e outra abaixo do meu domínio que está dentro de eshm.local com a COR CINZA. Isso é normal?

    Referente aos comandos segue abaixo.

    PS C:\Users\Administrator.ESHM> DCDIAG /E /V
    
    Directory Server Diagnosis
    
    Performing initial setup:
       Trying to find home server...
       * Verifying that the local machine FILESERVER, is a Directory Server.
       Home Server = FILESERVER
       * Connecting to directory service on server FILESERVER.
       * Identified AD Forest.
       Collecting AD specific global data
       * Collecting site info.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=eshm,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSS
    iteSettings),.......
       The previous call succeeded
       Iterating through the sites
       Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=eshm,DC=lo
    cal
       Getting ISTG and options for the site
       * Identifying all servers.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=eshm,DC=local,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa)
    ,.......
       The previous call succeeded....
       The previous call succeeded
       Iterating through the list of servers
       Getting information for the server CN=NTDS Settings,CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=eshm,DC=local
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       Getting information for the server CN=NTDS Settings,CN=FILESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=C
    onfiguration,DC=eshm,DC=local
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       * Identifying all NC cross-refs.
       * Found 2 DC(s). Testing 2 of them.
       Done gathering initial info.
    
    Doing initial required tests
    
       Testing server: Default-First-Site-Name\SRVADM
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             Determining IP4 connectivity
             * Active Directory RPC Services Check
             ......................... SRVADM passed test Connectivity
    
       Testing server: Default-First-Site-Name\FILESERVER
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             Determining IP4 connectivity
             * Active Directory RPC Services Check
             ......................... FILESERVER passed test Connectivity
    
    Doing primary tests
    
       Testing server: Default-First-Site-Name\SRVADM
          Starting test: Advertising
             The DC SRVADM is advertising itself as a DC and having a DS.
             The DC SRVADM is advertising as an LDAP server
             The DC SRVADM is advertising as having a writeable directory
             The DC SRVADM is advertising as a Key Distribution Center
             The DC SRVADM is advertising as a time server
             The DS SRVADM is advertising as a GC.
             ......................... SRVADM passed test Advertising
          Test omitted by user request: CheckSecurityError
          Test omitted by user request: CutoffServers
          Starting test: FrsEvent
             * The File Replication Service Event log test
             Skip the test because the server is running DFSR.
             ......................... SRVADM passed test FrsEvent
          Starting test: DFSREvent
             The DFS Replication Event Log.
             The event log DFS Replication on server SRVADM.eshm.local could not be queried, error 0x6ba
             "The RPC server is unavailable."
             ......................... SRVADM failed test DFSREvent
          Starting test: SysVolCheck
             * The File Replication Service SYSVOL ready test
             File Replication Service's SYSVOL is ready
             ......................... SRVADM passed test SysVolCheck
          Starting test: KccEvent
             * The KCC Event log test
             The event log Directory Service on server SRVADM.eshm.local could not be queried, error 0x6ba
             "The RPC server is unavailable."
             ......................... SRVADM failed test KccEvent
          Starting test: KnowsOfRoleHolders
             Role Schema Owner = CN=NTDS Settings,CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,
    DC=eshm,DC=local
             Role Domain Owner = CN=NTDS Settings,CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,
    DC=eshm,DC=local
             Role PDC Owner = CN=NTDS Settings,CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=
    eshm,DC=local
             Role Rid Owner = CN=NTDS Settings,CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=
    eshm,DC=local
             Role Infrastructure Update Owner = CN=NTDS Settings,CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN
    =Configuration,DC=eshm,DC=local
             ......................... SRVADM passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             Checking machine account for DC SRVADM on DC SRVADM.
             * SPN found :LDAP/SRVADM.eshm.local/eshm.local
             * SPN found :LDAP/SRVADM.eshm.local
             * SPN found :LDAP/SRVADM
             * SPN found :LDAP/SRVADM.eshm.local/ESHM
             * SPN found :LDAP/c8b20662-3c43-4123-a6e5-0f7460d01116._msdcs.eshm.local
             * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/c8b20662-3c43-4123-a6e5-0f7460d01116/eshm.local
             * SPN found :HOST/SRVADM.eshm.local/eshm.local
             * SPN found :HOST/SRVADM.eshm.local
             * SPN found :HOST/SRVADM
             * SPN found :HOST/SRVADM.eshm.local/ESHM
             * SPN found :GC/SRVADM.eshm.local/eshm.local
             ......................... SRVADM passed test MachineAccount
          Starting test: NCSecDesc
             * Security Permissions check for all NC's on DC SRVADM.
             * Security Permissions Check for
               DC=ForestDnsZones,DC=eshm,DC=local
                (NDNC,Version 3)
             * Security Permissions Check for
               DC=DomainDnsZones,DC=eshm,DC=local
                (NDNC,Version 3)
             * Security Permissions Check for
               CN=Schema,CN=Configuration,DC=eshm,DC=local
                (Schema,Version 3)
             * Security Permissions Check for
               CN=Configuration,DC=eshm,DC=local
                (Configuration,Version 3)
             * Security Permissions Check for
               DC=eshm,DC=local
                (Domain,Version 3)
             ......................... SRVADM passed test NCSecDesc
          Starting test: NetLogons
             * Network Logons Privileges Check
             Verified share \\SRVADM\netlogon
             Verified share \\SRVADM\sysvol
             ......................... SRVADM passed test NetLogons
          Starting test: ObjectsReplicated
             SRVADM is in domain DC=eshm,DC=local
             Checking for CN=SRVADM,OU=Domain Controllers,DC=eshm,DC=local in domain DC=eshm,DC=local on 2 servers
                Object is up-to-date on all servers.
             Checking for CN=NTDS Settings,CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=eshm
    ,DC=local in domain CN=Configuration,DC=eshm,DC=local on 2 servers
                Object is up-to-date on all servers.
             ......................... SRVADM passed test ObjectsReplicated
          Test omitted by user request: OutboundSecureChannels
          Starting test: Replications
             * Replications Check
             * Replication Latency Check
             ......................... SRVADM passed test Replications
          Starting test: RidManager
             * Available RID Pool for the Domain is 2100 to 1073741823
             * SRVADM.eshm.local is the RID Master
             * DsBind with RID Master was successful
             * rIDAllocationPool is 1100 to 1599
             * rIDPreviousAllocationPool is 1100 to 1599
             * rIDNextRID: 1317
             ......................... SRVADM passed test RidManager
          Starting test: Services
             * Checking Service: EventSystem
             * Checking Service: RpcSs
             * Checking Service: NTDS
             * Checking Service: DnsCache
             * Checking Service: DFSR
             * Checking Service: IsmServ
             * Checking Service: kdc
             * Checking Service: SamSs
             * Checking Service: LanmanServer
             * Checking Service: LanmanWorkstation
             * Checking Service: w32time
             * Checking Service: NETLOGON
             ......................... SRVADM passed test Services
          Starting test: SystemLog
             * The System Event log test
             The event log System on server SRVADM.eshm.local could not be queried, error 0x6ba
             "The RPC server is unavailable."
             ......................... SRVADM failed test SystemLog
          Test omitted by user request: Topology
          Test omitted by user request: VerifyEnterpriseReferences
          Starting test: VerifyReferences
             The system object reference (serverReference) CN=SRVADM,OU=Domain Controllers,DC=eshm,DC=local and backlink on
             CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=eshm,DC=local are correct.
             The system object reference (serverReferenceBL)
             CN=SRVADM,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=eshm,DC=local and backlink
             on CN=NTDS Settings,CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=eshm,DC=local
             are correct.
             The system object reference (msDFSR-ComputerReferenceBL)
             CN=5fb61f97-672b-4ce2-a091-0ba97b861ea9,CN=Topology,CN=eshm.local\\arquivos\\gerencia,CN=DFSR-GlobalSettings,CN
    =System,DC=eshm,DC=local
             and backlink on CN=SRVADM,OU=Domain Controllers,DC=eshm,DC=local are correct.
             ......................... SRVADM passed test VerifyReferences
          Test omitted by user request: VerifyReplicas
    
       Testing server: Default-First-Site-Name\FILESERVER
          Starting test: Advertising
             The DC FILESERVER is advertising itself as a DC and having a DS.
             The DC FILESERVER is advertising as an LDAP server
             The DC FILESERVER is advertising as having a writeable directory
             The DC FILESERVER is advertising as a Key Distribution Center
             The DC FILESERVER is advertising as a time server
             The DS FILESERVER is advertising as a GC.
             ......................... FILESERVER passed test Advertising
          Test omitted by user request: CheckSecurityError
          Test omitted by user request: CutoffServers
          Starting test: FrsEvent
             * The File Replication Service Event log test
             Skip the test because the server is running DFSR.
             ......................... FILESERVER passed test FrsEvent
          Starting test: DFSREvent
             The DFS Replication Event Log.
             There are warning or error events within the last 24 hours after the SYSVOL has been shared.  Failing SYSVOL
             replication problems may cause Group Policy problems.
             A warning event occurred.  EventID: 0x80001396
                Time Generated: 03/26/2019   23:01:54
                Event String:
                The DFS Replication service is stopping communication with partner SRVADM for replication group eshm.local\a
    rquivos\educandoalem due to an error. The service will retry the connection periodically.
    
                Additional Information:
                Error: 9036 (Paused for backup or restore)
                Connection ID: AA6B5F58-FB36-4D97-B13D-C8157D48B1A2
                Replication Group ID: 8776641A-E893-49C9-AA41-A87BA192F7E5
             A warning event occurred.  EventID: 0x80001396
                Time Generated: 03/26/2019   23:01:54
                Event String:
                The DFS Replication service is stopping communication with partner SRVADM for replication group Domain Syste
    m Volume due to an error. The service will retry the connection periodically.
    
                Additional Information:
                Error: 9036 (Paused for backup or restore)
                Connection ID: E093CEB7-53AE-4AE1-B39E-4E676C7874AA
                Replication Group ID: 25D7402C-0D33-4A36-A0C4-21260CD17E2F
             A warning event occurred.  EventID: 0x80001396
                Time Generated: 03/26/2019   23:01:54
                Event String:
                The DFS Replication service is stopping communication with partner SRVADM for replication group eshm.local\a
    rquivos\adriano due to an error. The service will retry the connection periodically.
    
                Additional Information:
                Error: 9036 (Paused for backup or restore)
                Connection ID: B8B5E8D9-7DAC-4A13-A064-6B4B56AC5C59
                Replication Group ID: D83C263B-2FA1-4859-8B37-25835F50B7C1
             A warning event occurred.  EventID: 0x80001396
                Time Generated: 03/26/2019   23:01:54
                Event String:
                The DFS Replication service is stopping communication with partner SRVADM for replication group eshm.local\a
    rquivos\financeiro due to an error. The service will retry the connection periodically.
    
                Additional Information:
                Error: 9036 (Paused for backup or restore)
                Connection ID: D201A678-EFC7-4367-9F85-9CC0F2504C12
                Replication Group ID: 32D12A3E-7673-41B5-9759-182A0451DE7F
             A warning event occurred.  EventID: 0x80001396
                Time Generated: 03/26/2019   23:01:54
                Event String:
                The DFS Replication service is stopping communication with partner SRVADM for replication group eshm.local\a
    rquivos\esporte due to an error. The service will retry the connection periodically.
    
                Additional Information:
                Error: 9036 (Paused for backup or restore)
                Connection ID: D6596E5A-EE94-44C8-B4D0-408EED9E7121
                Replication Group ID: 8DD65C89-81A9-48A6-A209-A73D889BE2BD
             A warning event occurred.  EventID: 0x80001396
                Time Generated: 03/26/2019   23:01:54
                Event String:
                The DFS Replication service is stopping communication with partner SRVADM for replication group eshm.local\a
    rquivos\gerencia due to an error. The service will retry the connection periodically.
    
                Additional Information:
                Error: 9036 (Paused for backup or restore)
                Connection ID: 0D106B5B-BCF9-4C44-A1B2-1D4C8E0E0909
                Replication Group ID: 42ACAF89-CAF5-409F-8F40-1671588B6707
             A warning event occurred.  EventID: 0x80001396
                Time Generated: 03/26/2019   23:01:54
                Event String:
                The DFS Replication service is stopping communication with partner SRVADM for replication group eshm.local\a
    rquivos\biblioteca due to an error. The service will retry the connection periodically.
    
                Additional Information:
                Error: 9036 (Paused for backup or restore)
                Connection ID: A41634A1-7F10-41B2-BDD3-B74D88ADE35D
                Replication Group ID: B41FBA8C-9B14-4C66-9CD5-82B7373CA715
             A warning event occurred.  EventID: 0x80001396
                Time Generated: 03/26/2019   23:01:54
                Event String:
                The DFS Replication service is stopping communication with partner SRVADM for replication group eshm.local\a
    rquivos\pedagogia due to an error. The service will retry the connection periodically.
    
                Additional Information:
                Error: 9036 (Paused for backup or restore)
                Connection ID: 54AAB956-1E4A-4F82-88D2-400D7C4D0BB5
                Replication Group ID: 8F8A4D95-BD03-477E-94A6-035F215579D5
             A warning event occurred.  EventID: 0x80001396
                Time Generated: 03/26/2019   23:01:54
                Event String:
                The DFS Replication service is stopping communication with partner SRVADM for replication group eshm.local\a
    rquivos\servico social due to an error. The service will retry the connection periodically.
    
                Additional Information:
                Error: 9036 (Paused for backup or restore)
                Connection ID: E67AEEB1-BA17-4203-ACC6-CEEDE043F568
                Replication Group ID: E486B7B0-A6AD-4E3E-A620-791EF30F988B
             A warning event occurred.  EventID: 0x80001396
                Time Generated: 03/26/2019   23:01:54
                Event String:
                The DFS Replication service is stopping communication with partner SRVADM for replication group eshm.local\a
    rquivos\secretaria due to an error. The service will retry the connection periodically.
    
                Additional Information:
                Error: 9036 (Paused for backup or restore)
                Connection ID: FEBD9409-3575-4B11-A079-337266C920C4
                Replication Group ID: 28BD91EF-623F-4DB4-B651-4DFDDA1231D1
             A warning event occurred.  EventID: 0x80001396
                Time Generated: 03/26/2019   23:01:54
                Event String:
                The DFS Replication service is stopping communication with partner SRVADM for replication group eshm.local\a
    rquivos\manutencao due to an error. The service will retry the connection periodically.
    
                Additional Information:
                Error: 9036 (Paused for backup or restore)
                Connection ID: E0E062B4-45DE-4B42-AEDC-6D14C9276A1F
                Replication Group ID: E99B5EF9-8B8F-481E-AE66-8B37B4A27458
             A warning event occurred.  EventID: 0x80001396
                Time Generated: 03/26/2019   23:01:54
                Event String:
                The DFS Replication service is stopping communication with partner SRVADM for replication group eshm.local\a
    rquivos\disciplinarios due to an error. The service will retry the connection periodically.
    
                Additional Information:
                Error: 9036 (Paused for backup or restore)
                Connection ID: 15809F36-776B-4476-A523-50541CA86117
                Replication Group ID: CF9472FE-8DCF-4CB1-965D-3EF524FEFC32
             An error event occurred.  EventID: 0xC0001394
                Time Generated: 03/26/2019   23:02:08
                Event String:
                The DFS Replication service failed to communicate with partner SRVADM for replication group Domain System Vo
    lume. The partner did not recognize the connection or the replication group configuration.
    
                Partner DNS Address: SRVADM.eshm.local
    
                Optional data if available:
                Partner WINS Address: SRVADM
                Partner IP Address: 192.168.27.5
    
    
                The service will retry the connection periodically.
    
                Additional Information:
                Error: 9026 (The connection is invalid)
                Connection ID: E093CEB7-53AE-4AE1-B39E-4E676C7874AA
                Replication Group ID: 25D7402C-0D33-4A36-A0C4-21260CD17E2F
             An error event occurred.  EventID: 0xC0001394
                Time Generated: 03/26/2019   23:02:08
                Event String:
                The DFS Replication service failed to communicate with partner SRVADM for replication group eshm.local\arqui
    vos\adriano. The partner did not recognize the connection or the replication group configuration.
    
                Partner DNS Address: SRVADM.eshm.local
    
                Optional data if available:
                Partner WINS Address: SRVADM
                Partner IP Address: 192.168.27.5
    
    
                The service will retry the connection periodically.
    
                Additional Information:
                Error: 9026 (The connection is invalid)
                Connection ID: B8B5E8D9-7DAC-4A13-A064-6B4B56AC5C59
                Replication Group ID: D83C263B-2FA1-4859-8B37-25835F50B7C1
             An error event occurred.  EventID: 0xC0001394
                Time Generated: 03/26/2019   23:02:08
                Event String:
                The DFS Replication service failed to communicate with partner SRVADM for replication group eshm.local\arqui
    vos\financeiro. The partner did not recognize the connection or the replication group configuration.
    
                Partner DNS Address: SRVADM.eshm.local
    
                Optional data if available:
                Partner WINS Address: SRVADM
                Partner IP Address: 192.168.27.5
    
    
                The service will retry the connection periodically.
    
                Additional Information:
                Error: 9026 (The connection is invalid)
                Connection ID: D201A678-EFC7-4367-9F85-9CC0F2504C12
                Replication Group ID: 32D12A3E-7673-41B5-9759-182A0451DE7F
             An error event occurred.  EventID: 0xC0001394
                Time Generated: 03/26/2019   23:02:08
                Event String:
                The DFS Replication service failed to communicate with partner SRVADM for replication group eshm.local\arqui
    vos\esporte. The partner did not recognize the connection or the replication group configuration.
    
                Partner DNS Address: SRVADM.eshm.local
    
                Optional data if available:
                Partner WINS Address: SRVADM
                Partner IP Address: 192.168.27.5
    
    
                The service will retry the connection periodically.
    
                Additional Information:
                Error: 9026 (The connection is invalid)
                Connection ID: D6596E5A-EE94-44C8-B4D0-408EED9E7121
                Replication Group ID: 8DD65C89-81A9-48A6-A209-A73D889BE2BD
             An error event occurred.  EventID: 0xC0001394
                Time Generated: 03/26/2019   23:02:08
                Event String:
                The DFS Replication service failed to communicate with partner SRVADM for replication group eshm.local\arqui
    vos\educandoalem. The partner did not recognize the connection or the replication group configuration.
    
                Partner DNS Address: SRVADM.eshm.local
    
                Optional data if available:
                Partner WINS Address: SRVADM
                Partner IP Address: 192.168.27.5
    
    
                The service will retry the connection periodically.
    
                Additional Information:
                Error: 9026 (The connection is invalid)
                Connection ID: AA6B5F58-FB36-4D97-B13D-C8157D48B1A2
                Replication Group ID: 8776641A-E893-49C9-AA41-A87BA192F7E5
             An error event occurred.  EventID: 0xC0001394
                Time Generated: 03/26/2019   23:02:08
                Event String:
                The DFS Replication service failed to communicate with partner SRVADM for replication group eshm.local\arqui
    vos\gerencia. The partner did not recognize the connection or the replication group configuration.
    
                Partner DNS Address: SRVADM.eshm.local
    
                Optional data if available:
                Partner WINS Address: SRVADM
                Partner IP Address: 192.168.27.5
    
    
                The service will retry the connection periodically.
    
                Additional Information:
                Error: 9026 (The connection is invalid)
                Connection ID: 0D106B5B-BCF9-4C44-A1B2-1D4C8E0E0909
                Replication Group ID: 42ACAF89-CAF5-409F-8F40-1671588B6707
             An error event occurred.  EventID: 0xC0001394
                Time Generated: 03/26/2019   23:02:08
                Event String:
                The DFS Replication service failed to communicate with partner SRVADM for replication group eshm.local\arqui
    vos\biblioteca. The partner did not recognize the connection or the replication group configuration.
    
                Partner DNS Address: SRVADM.eshm.local
    
                Optional data if available:
                Partner WINS Address: SRVADM
                Partner IP Address: 192.168.27.5
    
    
                The service will retry the connection periodically.
    
                Additional Information:
                Error: 9026 (The connection is invalid)
                Connection ID: A41634A1-7F10-41B2-BDD3-B74D88ADE35D
                Replication Group ID: B41FBA8C-9B14-4C66-9CD5-82B7373CA715
             An error event occurred.  EventID: 0xC0001394
                Time Generated: 03/26/2019   23:02:08
                Event String:
                The DFS Replication service failed to communicate with partner SRVADM for replication group eshm.local\arqui
    vos\servico social. The partner did not recognize the connection or the replication group configuration.
    
                Partner DNS Address: SRVADM.eshm.local
    
                Optional data if available:
                Partner WINS Address: SRVADM
                Partner IP Address: 192.168.27.5
    
    
                The service will retry the connection periodically.
    
                Additional Information:
                Error: 9026 (The connection is invalid)
                Connection ID: E67AEEB1-BA17-4203-ACC6-CEEDE043F568
                Replication Group ID: E486B7B0-A6AD-4E3E-A620-791EF30F988B
             An error event occurred.  EventID: 0xC0001394
                Time Generated: 03/26/2019   23:02:08
                Event String:
                The DFS Replication service failed to communicate with partner SRVADM for replication group eshm.local\arqui
    vos\pedagogia. The partner did not recognize the connection or the replication group configuration.
    
                Partner DNS Address: SRVADM.eshm.local
    
                Optional data if available:
                Partner WINS Address: SRVADM
                Partner IP Address: 192.168.27.5
    
    
                The service will retry the connection periodically.
    
                Additional Information:
                Error: 9026 (The connection is invalid)
                Connection ID: 54AAB956-1E4A-4F82-88D2-400D7C4D0BB5
                Replication Group ID: 8F8A4D95-BD03-477E-94A6-035F215579D5
             An error event occurred.  EventID: 0xC0001394
                Time Generated: 03/26/2019   23:02:08
                Event String:
                The DFS Replication service failed to communicate with partner SRVADM for replication group eshm.local\arqui
    vos\secretaria. The partner did not recognize the connection or the replication group configuration.
    
                Partner DNS Address: SRVADM.eshm.local
    
                Optional data if available:
                Partner WINS Address: SRVADM
                Partner IP Address: 192.168.27.5
    
    
                The service will retry the connection periodically.
    
                Additional Information:
                Error: 9026 (The connection is invalid)
                Connection ID: FEBD9409-3575-4B11-A079-337266C920C4
                Replication Group ID: 28BD91EF-623F-4DB4-B651-4DFDDA1231D1
             An error event occurred.  EventID: 0xC0001394
                Time Generated: 03/26/2019   23:02:08
                Event String:
                The DFS Replication service failed to communicate with partner SRVADM for replication group eshm.local\arqui
    vos\manutencao. The partner did not recognize the connection or the replication group configuration.
    
                Partner DNS Address: SRVADM.eshm.local
    
                Optional data if available:
                Partner WINS Address: SRVADM
                Partner IP Address: 192.168.27.5
    
    
                The service will retry the connection periodically.
    
                Additional Information:
                Error: 9026 (The connection is invalid)
                Connection ID: E0E062B4-45DE-4B42-AEDC-6D14C9276A1F
                Replication Group ID: E99B5EF9-8B8F-481E-AE66-8B37B4A27458
             An error event occurred.  EventID: 0xC0001394
                Time Generated: 03/26/2019   23:02:08
                Event String:
                The DFS Replication service failed to communicate with partner SRVADM for replication group eshm.local\arqui
    vos\disciplinarios. The partner did not recognize the connection or the replication group configuration.
    
                Partner DNS Address: SRVADM.eshm.local
    
                Optional data if available:
                Partner WINS Address: SRVADM
                Partner IP Address: 192.168.27.5
    
    
                The service will retry the connection periodically.
    
                Additional Information:
                Error: 9026 (The connection is invalid)
                Connection ID: 15809F36-776B-4476-A523-50541CA86117
                Replication Group ID: CF9472FE-8DCF-4CB1-965D-3EF524FEFC32
             ......................... FILESERVER failed test DFSREvent
          Starting test: SysVolCheck
             * The File Replication Service SYSVOL ready test
             File Replication Service's SYSVOL is ready
             ......................... FILESERVER passed test SysVolCheck
          Starting test: KccEvent
             * The KCC Event log test
             Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
             ......................... FILESERVER passed test KccEvent
          Starting test: KnowsOfRoleHolders
             Role Schema Owner = CN=NTDS Settings,CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,
    DC=eshm,DC=local
             Role Domain Owner = CN=NTDS Settings,CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,
    DC=eshm,DC=local
             Role PDC Owner = CN=NTDS Settings,CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=
    eshm,DC=local
             Role Rid Owner = CN=NTDS Settings,CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=
    eshm,DC=local
             Role Infrastructure Update Owner = CN=NTDS Settings,CN=SRVADM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN
    =Configuration,DC=eshm,DC=local
             ......................... FILESERVER passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             Checking machine account for DC FILESERVER on DC FILESERVER.
             * SPN found :LDAP/FILESERVER.eshm.local/eshm.local
             * SPN found :LDAP/FILESERVER.eshm.local
             * SPN found :LDAP/FILESERVER
             * SPN found :LDAP/FILESERVER.eshm.local/ESHM
             * SPN found :LDAP/58a8afd0-693d-40c5-8481-e9931a364c83._msdcs.eshm.local
             * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/58a8afd0-693d-40c5-8481-e9931a364c83/eshm.local
             * SPN found :HOST/FILESERVER.eshm.local/eshm.local
             * SPN found :HOST/FILESERVER.eshm.local
             * SPN found :HOST/FILESERVER
             * SPN found :HOST/FILESERVER.eshm.local/ESHM
             * SPN found :GC/FILESERVER.eshm.local/eshm.local
             ......................... FILESERVER passed test MachineAccount
          Starting test: NCSecDesc
             * Security Permissions check for all NC's on DC FILESERVER.
             * Security Permissions Check for
               DC=ForestDnsZones,DC=eshm,DC=local
                (NDNC,Version 3)
             * Security Permissions Check for
               DC=DomainDnsZones,DC=eshm,DC=local
                (NDNC,Version 3)
             * Security Permissions Check for
               CN=Schema,CN=Configuration,DC=eshm,DC=local
                (Schema,Version 3)
             * Security Permissions Check for
               CN=Configuration,DC=eshm,DC=local
                (Configuration,Version 3)
             * Security Permissions Check for
               DC=eshm,DC=local
                (Domain,Version 3)
             ......................... FILESERVER passed test NCSecDesc
          Starting test: NetLogons
             * Network Logons Privileges Check
             Unable to connect to the NETLOGON share! (\\FILESERVER\netlogon)
             [FILESERVER] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
             ......................... FILESERVER failed test NetLogons
          Starting test: ObjectsReplicated
             FILESERVER is in domain DC=eshm,DC=local
             Checking for CN=FILESERVER,OU=Domain Controllers,DC=eshm,DC=local in domain DC=eshm,DC=local on 2 servers
                Object is up-to-date on all servers.
             Checking for CN=NTDS Settings,CN=FILESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=
    eshm,DC=local in domain CN=Configuration,DC=eshm,DC=local on 2 servers
                Object is up-to-date on all servers.
             ......................... FILESERVER passed test ObjectsReplicated
          Test omitted by user request: OutboundSecureChannels
          Starting test: Replications
             * Replications Check
             * Replication Latency Check
             ......................... FILESERVER passed test Replications
          Starting test: RidManager
             * Available RID Pool for the Domain is 2100 to 1073741823
             * SRVADM.eshm.local is the RID Master
             * DsBind with RID Master was successful
             * rIDAllocationPool is 1600 to 2099
             * rIDPreviousAllocationPool is 1600 to 2099
             * rIDNextRID: 1602
             ......................... FILESERVER passed test RidManager
          Starting test: Services
             * Checking Service: EventSystem
             * Checking Service: RpcSs
             * Checking Service: NTDS
             * Checking Service: DnsCache
             * Checking Service: DFSR
             * Checking Service: IsmServ
             * Checking Service: kdc
             * Checking Service: SamSs
             * Checking Service: LanmanServer
             * Checking Service: LanmanWorkstation
             * Checking Service: w32time
             * Checking Service: NETLOGON
             ......................... FILESERVER passed test Services
          Starting test: SystemLog
             * The System Event log test
             An error event occurred.  EventID: 0x00000422
                Time Generated: 03/27/2019   09:31:29
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\eshm.local\sysvol\eshm.local\Pol
    icies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini from a domain controller and was not successful. Group Policy setti
    ngs may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of t
    he following:
                a) Name Resolution/Network Connectivity to the current domain controller.
                b) File Replication Service Latency (a file created on another domain controller has not replicated to the c
    urrent domain controller).
                c) The Distributed File System (DFS) client has been disabled.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 03/27/2019   09:36:29
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\eshm.local\sysvol\eshm.local\Pol
    icies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini from a domain controller and was not successful. Group Policy setti
    ngs may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of t
    he following:
                a) Name Resolution/Network Connectivity to the current domain controller.
                b) File Replication Service Latency (a file created on another domain controller has not replicated to the c
    urrent domain controller).
                c) The Distributed File System (DFS) client has been disabled.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 03/27/2019   09:41:29
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\eshm.local\sysvol\eshm.local\Pol
    icies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini from a domain controller and was not successful. Group Policy setti
    ngs may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of t
    he following:
                a) Name Resolution/Network Connectivity to the current domain controller.
                b) File Replication Service Latency (a file created on another domain controller has not replicated to the c
    urrent domain controller).
                c) The Distributed File System (DFS) client has been disabled.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 03/27/2019   09:46:29
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\eshm.local\sysvol\eshm.local\Pol
    icies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini from a domain controller and was not successful. Group Policy setti
    ngs may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of t
    he following:
                a) Name Resolution/Network Connectivity to the current domain controller.
                b) File Replication Service Latency (a file created on another domain controller has not replicated to the c
    urrent domain controller).
                c) The Distributed File System (DFS) client has been disabled.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 03/27/2019   09:51:29
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\eshm.local\sysvol\eshm.local\Pol
    icies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini from a domain controller and was not successful. Group Policy setti
    ngs may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of t
    he following:
                a) Name Resolution/Network Connectivity to the current domain controller.
                b) File Replication Service Latency (a file created on another domain controller has not replicated to the c
    urrent domain controller).
                c) The Distributed File System (DFS) client has been disabled.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 03/27/2019   09:56:29
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\eshm.local\sysvol\eshm.local\Pol
    icies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini from a domain controller and was not successful. Group Policy setti
    ngs may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of t
    he following:
                a) Name Resolution/Network Connectivity to the current domain controller.
                b) File Replication Service Latency (a file created on another domain controller has not replicated to the c
    urrent domain controller).
                c) The Distributed File System (DFS) client has been disabled.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 03/27/2019   10:01:29
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\eshm.local\sysvol\eshm.local\Pol
    icies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini from a domain controller and was not successful. Group Policy setti
    ngs may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of t
    he following:
                a) Name Resolution/Network Connectivity to the current domain controller.
                b) File Replication Service Latency (a file created on another domain controller has not replicated to the c
    urrent domain controller).
                c) The Distributed File System (DFS) client has been disabled.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 03/27/2019   10:06:29
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\eshm.local\sysvol\eshm.local\Pol
    icies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini from a domain controller and was not successful. Group Policy setti
    ngs may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of t
    he following:
                a) Name Resolution/Network Connectivity to the current domain controller.
                b) File Replication Service Latency (a file created on another domain controller has not replicated to the c
    urrent domain controller).
                c) The Distributed File System (DFS) client has been disabled.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 03/27/2019   10:11:30
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\eshm.local\sysvol\eshm.local\Pol
    icies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini from a domain controller and was not successful. Group Policy setti
    ngs may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of t
    he following:
                a) Name Resolution/Network Connectivity to the current domain controller.
                b) File Replication Service Latency (a file created on another domain controller has not replicated to the c
    urrent domain controller).
                c) The Distributed File System (DFS) client has been disabled.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 03/27/2019   10:16:30
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\eshm.local\sysvol\eshm.local\Pol
    icies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini from a domain controller and was not successful. Group Policy setti
    ngs may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of t
    he following:
                a) Name Resolution/Network Connectivity to the current domain controller.
                b) File Replication Service Latency (a file created on another domain controller has not replicated to the c
    urrent domain controller).
                c) The Distributed File System (DFS) client has been disabled.
             An error event occurred.  EventID: 0x0000272C
                Time Generated: 03/27/2019   10:19:00
                Event String:
                DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by
     PID     1164 (C:\Windows\system32\dcdiag.exe).
             An error event occurred.  EventID: 0x00000422
                Time Generated: 03/27/2019   10:21:30
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\eshm.local\sysvol\eshm.local\Pol
    icies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini from a domain controller and was not successful. Group Policy setti
    ngs may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of t
    he following:
                a) Name Resolution/Network Connectivity to the current domain controller.
                b) File Replication Service Latency (a file created on another domain controller has not replicated to the c
    urrent domain controller).
                c) The Distributed File System (DFS) client has been disabled.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 03/27/2019   10:26:30
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\eshm.local\sysvol\eshm.local\Pol
    icies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini from a domain controller and was not successful. Group Policy setti
    ngs may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of t
    he following:
                a) Name Resolution/Network Connectivity to the current domain controller.
                b) File Replication Service Latency (a file created on another domain controller has not replicated to the c
    urrent domain controller).
                c) The Distributed File System (DFS) client has been disabled.
             ......................... FILESERVER failed test SystemLog
          Test omitted by user request: Topology
          Test omitted by user request: VerifyEnterpriseReferences
          Starting test: VerifyReferences
             The system object reference (serverReference) CN=FILESERVER,OU=Domain Controllers,DC=eshm,DC=local and
             backlink on CN=FILESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=eshm,DC=local are
             correct.
             The system object reference (serverReferenceBL)
             CN=FILESERVER,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=eshm,DC=local and
             backlink on
             CN=NTDS Settings,CN=FILESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=eshm,DC=local
    
             are correct.
             The system object reference (msDFSR-ComputerReferenceBL)
             CN=eb017dbb-01e3-404a-9769-1b828e40a5fa,CN=Topology,CN=eshm.local\\arquivos\\gerencia,CN=DFSR-GlobalSettings,CN
    =System,DC=eshm,DC=local
             and backlink on CN=FILESERVER,OU=Domain Controllers,DC=eshm,DC=local are correct.
             ......................... FILESERVER passed test VerifyReferences
          Test omitted by user request: VerifyReplicas
    
          Test omitted by user request: DNS
          Test omitted by user request: DNS
    
          Test omitted by user request: DNS
          Test omitted by user request: DNS
    
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
    
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
    
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
    
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
    
       Running partition tests on : eshm
          Starting test: CheckSDRefDom
             ......................... eshm passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... eshm passed test CrossRefValidation
    
       Running enterprise tests on : eshm.local
          Test omitted by user request: DNS
          Test omitted by user request: DNS
          Starting test: LocatorCheck
             GC Name: \\FILESERVER.eshm.local
             Locator Flags: 0xe000f1fc
             PDC Name: \\SRVADM.eshm.local
             Locator Flags: 0xe00031fd
             Time Server Name: \\FILESERVER.eshm.local
             Locator Flags: 0xe000f1fc
             Preferred Time Server Name: \\FILESERVER.eshm.local
             Locator Flags: 0xe000f1fc
             KDC Name: \\FILESERVER.eshm.local
             Locator Flags: 0xe000f1fc
             ......................... eshm.local passed test LocatorCheck
          Starting test: Intersite
             Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments
             provided.
             ......................... eshm.local passed test Intersite
    PS C:\Users\Administrator.ESHM>

    quarta-feira, 27 de março de 2019 13:37
  • sim, é normal para quem instala o DNS de forma automática junto com a promoção do Domain Controller, by design , conforme link repassado explicando. A principio não há erro de replicação

    com relação ao diagnóstico, seus problemas são:

    Há vários erros de comunicação para replicação DFS para vários grupos de replicação , o "manutencao" é um deles.

    The DFS Replication service failed to communicate with partner SRVADM for replication group eshm.local\arqui
    vos\manutencao. The partner did not recognize the connection or the replication group configuration.

    Vai ter que fazer um debug desse problema

    https://social.technet.microsoft.com/wiki/contents/articles/31558.dfsr-troubleshooting-handy-quick-tips.aspx

    Você faz uso de IPV6 internamente ? Esse IP de loopback IPV6 :1 pode estar impactando suas consultas. 

    Erro de acesso ao share do NETLOGON:

    Unable to connect to the NETLOGON share! (\\FILESERVER\netlogon)
             [FILESERVER] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
             ......................... FILESERVER failed test NetLogons

    https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

    Firewall esta ativado nos servidores ? se houver firewall entre os servidores ou firewall do windows ativado, liberou todas as portas de comunicação ?

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/b6097a84-d5aa-490c-9ba8-c6782fabf663/firewall-ports-between-domain-controllers?forum=winserverDS


    "Se eu tivesse oito horas para derrubar uma árvore passaria seis afiando meu machado". Abraham Lincoln

    quarta-feira, 27 de março de 2019 14:19
    Moderador
  • Felipe, boa tarde!

    Obrigado pela resposta.

    Eu não utilizo IPV6.

    Em relação a esse link
    https://social.technet.microsoft.com/wiki/contents/articles/31558.dfsr-troubleshooting-handy-quick-tips.aspx

    DEU ERRO NESSES DOIS ABAIXO. Os demais deu para fazer e esteve com status normal para todas replicações.

    Forçar replicação
    dfsrdiag syncnow /partner:RedMon-FS01 /RGName:"RedMon-FS01 - RedMon-FS02" /Time:1

    DFSRDIAG POLLAD /MEM:%computername%


    Verificando o backlog
    dfsrdiag backlog /rgname:"RedMon-FS01 - RedMon-FS02" /rfname:Folder_name /sendingmember:RedMon-FS01 /receivingmember:RedMon-FS02 




    Em relação a esse link.
    https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

    Não entendi com a leitura dele. Encontrei o arquivo ADSIEDIT.MSC porém ele não abre, então como fazer o procedimento abaixo:

    Na ferramenta ADSIEDIT.MSC , modifique o valor e o atributo DN (nome distinto) a seguir em cada um dos controladores de domínio que você deseja tornar não-autoritativos: 

    CN = Assinatura SYSVOL, CN = Volume do Sistema de Domínio, CN = DFSR-LocalSettings, CN = <o nome do servidor> , OU = Controladores de Domínio, DC = <domínio>

    msDFSR-Ativado = FALSE

    Muito obrigado pela atenção e paciência.

    Aguardo retorno.

    quarta-feira, 27 de março de 2019 17:45
  • Para solucionar o problema em questão, recomendo as verificações a seguir:

    Primeiramente, revisar todas as configurações de DNS nos Controladores de domínio:

    • Existe a zona reversa? Se não, crie (Reverse Lookup Zones/New Zone/Primary Zone/IPV4 Zone/Network ID:Ip da faixa de rede interna);
    • Nas propriedades do Servidor DNS, Aba Interfaces, em Listen On, marcar o Box "Only the Following IP Address, abaixo marcando o box correspondente a interface/IP utilizado no serviço DNS;
    • Nas zonas Primárias (Forward Lookup Zones), validar na aba Name Servers se constam os Nomes/IPs dos Servidores DNS/DCs, se não, adicionar.
    • Validar na aba Zone Transfers, se o box "Allow Zone Transfers" está marcado e logo abaixo, a opção "Only to Servers listed on the Name Servers Tab". Em seguida, clicar no botão Notify e marcar o box Automatically Notify e Servers Listed on the Name Servers Tab;
    • Pasta cinza _msdcs dentro da zona primária do domínio: Excluir a mesma. O ideal é que ela esteja na raiz de "Forward Lookup Zones". Caso não exista a zona _msdcs na raiz, a mesma pode ser recriada manualmente. 
    • Revisar as configrações de DNS primário e alternativo das placas de rede dos servidores, garantindo que o DNS primário de cada servidor seja o outro membro (no caso que tenha 2 controladores de domínio);
    • Mais detalhes: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731991(v%3dws.11)

    Após a revisão de configurações do DNS, é recomendado executar o Best Pratices Analyzer, para ver se ainda existe algum problema de configuração/funcionamento do serviço ou outro item que possa estar relacionado.

    Depois, recomendo que faça testes na replicação do SYSVOL. Se ainda existir problemas, pode ser necessário forçar a replicação, com orientação deste link: https://support.microsoft.com/en-in/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

    Se depois de tudo, ainda existir algum problema, poste logs de erro/warning gerado para que possamos avaliar de forma mais detalhada.


    Odirlei Souza | Analista de Suporte | MCP (70-290)

    • Sugerido como Resposta IgorFKModerator sexta-feira, 29 de março de 2019 17:14
    • Marcado como Resposta Adriano Monção segunda-feira, 1 de abril de 2019 11:15
    sexta-feira, 29 de março de 2019 14:19
  • Para solucionar o problema em questão, recomendo as verificações a seguir:

    Primeiramente, revisar todas as configurações de DNS nos Controladores de domínio:

    • Existe a zona reversa? Se não, crie (Reverse Lookup Zones/New Zone/Primary Zone/IPV4 Zone/Network ID:Ip da faixa de rede interna);
    • Nas propriedades do Servidor DNS, Aba Interfaces, em Listen On, marcar o Box "Only the Following IP Address, abaixo marcando o box correspondente a interface/IP utilizado no serviço DNS;
    • Nas zonas Primárias (Forward Lookup Zones), validar na aba Name Servers se constam os Nomes/IPs dos Servidores DNS/DCs, se não, adicionar.
    • Validar na aba Zone Transfers, se o box "Allow Zone Transfers" está marcado e logo abaixo, a opção "Only to Servers listed on the Name Servers Tab". Em seguida, clicar no botão Notify e marcar o box Automatically Notify e Servers Listed on the Name Servers Tab;
    • Pasta cinza _msdcs dentro da zona primária do domínio: Excluir a mesma. O ideal é que ela esteja na raiz de "Forward Lookup Zones". Caso não exista a zona _msdcs na raiz, a mesma pode ser recriada manualmente. 
    • Revisar as configrações de DNS primário e alternativo das placas de rede dos servidores, garantindo que o DNS primário de cada servidor seja o outro membro (no caso que tenha 2 controladores de domínio);
    • Mais detalhes: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731991(v%3dws.11)

    Após a revisão de configurações do DNS, é recomendado executar o Best Pratices Analyzer, para ver se ainda existe algum problema de configuração/funcionamento do serviço ou outro item que possa estar relacionado.

    Depois, recomendo que faça testes na replicação do SYSVOL. Se ainda existir problemas, pode ser necessário forçar a replicação, com orientação deste link: https://support.microsoft.com/en-in/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

    Se depois de tudo, ainda existir algum problema, poste logs de erro/warning gerado para que possamos avaliar de forma mais detalhada.


    Odirlei Souza | Analista de Suporte | MCP (70-290)

    Odirlei, bom dia!

    Muito obrigado pela resposta.

    Deu tudo certo.

    segunda-feira, 1 de abril de 2019 11:15