none
Problema ao promover um novo DC a um dominio existente RRS feed

  • Pergunta

  • Caros,

    Estou tentando adicionar um novo DC a minha rede, Faço o DCPROMO no member server e completa todo o processo sem erros, só que no novo servidor não aparecem os compartilhamentos NETLOGON e SYSVOL, o unico erro que aparece nos logs são erros de replicação :

    eventID:13508

    The File Replication Service is having trouble enabling replication from SERVERAUTH2 to DC1 for c:\windows\sysvol\domain using the DNS name serverauth2.saomarcos.org.br. FRS will keep retrying.

    Following are some of the reasons you would see this warning.

     

    [1] FRS can not correctly resolve the DNS name serverauth2.saomarcos.org.br from this computer.

    [2] FRS is not running on serverauth2.saomarcos.org.br.

    [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.

     

    This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    segue DCDIAG do dc que esta funcionando:


    Domain Controller Diagnosis

    Performing initial setup:
       Done gathering initial info.

    Doing initial required tests
      
       Testing server: Default-First-Site-Name\SERVERAUTH2
          Starting test: Connectivity
             ......................... SERVERAUTH2 passed test Connectivity

    Doing primary tests
      
       Testing server: Default-First-Site-Name\SERVERAUTH2
          Starting test: Replications
             ......................... SERVERAUTH2 passed test Replications
          Starting test: NCSecDesc
             ......................... SERVERAUTH2 passed test NCSecDesc
          Starting test: NetLogons
             ......................... SERVERAUTH2 passed test NetLogons
          Starting test: Advertising
             ......................... SERVERAUTH2 passed test Advertising
          Starting test: KnowsOfRoleHolders
             ......................... SERVERAUTH2 passed test KnowsOfRoleHolders
          Starting test: RidManager
             ......................... SERVERAUTH2 passed test RidManager
          Starting test: MachineAccount
             ......................... SERVERAUTH2 passed test MachineAccount
          Starting test: Services
             ......................... SERVERAUTH2 passed test Services
          Starting test: ObjectsReplicated
             ......................... SERVERAUTH2 passed test ObjectsReplicated
          Starting test: frssysvol
             ......................... SERVERAUTH2 passed test frssysvol
          Starting test: frsevent
             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.
             ......................... SERVERAUTH2 failed test frsevent
          Starting test: kccevent
             ......................... SERVERAUTH2 passed test kccevent
          Starting test: systemlog
             ......................... SERVERAUTH2 passed test systemlog
          Starting test: VerifyReferences
             ......................... SERVERAUTH2 passed test VerifyReferences
      
       Running partition tests on : ForestDnsZones
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
      
       Running partition tests on : DomainDnsZones
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
      
       Running partition tests on : Schema
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
      
       Running partition tests on : Configuration
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
      
       Running partition tests on : saomarcos
          Starting test: CrossRefValidation
             ......................... saomarcos passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... saomarcos passed test CheckSDRefDom
      
       Running enterprise tests on : saomarcos.org.br
          Starting test: Intersite
             ......................... saomarcos.org.br passed test Intersite
          Starting test: FsmoCheck
             ......................... saomarcos.org.br passed test FsmoCheck

    DCDIAG do  Controlador de Dominio novo:


    Domain Controller Diagnosis

    Performing initial setup:
       Done gathering initial info.

    Doing initial required tests
      
       Testing server: Default-First-Site-Name\DC1
          Starting test: Connectivity
             ......................... DC1 passed test Connectivity

    Doing primary tests
      
       Testing server: Default-First-Site-Name\DC1
          Starting test: Replications
             ......................... DC1 passed test Replications
          Starting test: NCSecDesc
             ......................... DC1 passed test NCSecDesc
          Starting test: NetLogons
             Unable to connect to the NETLOGON share! (\\DC1\netlogon)
             [DC1] An net use or LsaPolicy operation failed with error 1203, No network provider accepted the given network path..
             ......................... DC1 failed test NetLogons
          Starting test: Advertising
             Warning: DsGetDcName returned information for \\serverauth2.saomarcos.org.br, when we were trying to reach DC1.
             Server is not responding or is not considered suitable.
             ......................... DC1 failed test Advertising
          Starting test: KnowsOfRoleHolders
             ......................... DC1 passed test KnowsOfRoleHolders
          Starting test: RidManager
             ......................... DC1 passed test RidManager
          Starting test: MachineAccount
             ......................... DC1 passed test MachineAccount
          Starting test: Services
             ......................... DC1 passed test Services
          Starting test: ObjectsReplicated
             ......................... DC1 passed test ObjectsReplicated
          Starting test: frssysvol
             ......................... DC1 passed test frssysvol
          Starting test: frsevent
             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.
             ......................... DC1 failed test frsevent
          Starting test: kccevent
             ......................... DC1 passed test kccevent
          Starting test: systemlog
             ......................... DC1 passed test systemlog
          Starting test: VerifyReferences
             ......................... DC1 passed test VerifyReferences
      
       Running partition tests on : Schema
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
      
       Running partition tests on : Configuration
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
      
       Running partition tests on : saomarcos
          Starting test: CrossRefValidation
             ......................... saomarcos passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... saomarcos passed test CheckSDRefDom
      
       Running enterprise tests on : saomarcos.org.br
          Starting test: Intersite
             ......................... saomarcos.org.br passed test Intersite
          Starting test: FsmoCheck
             ......................... saomarcos.org.br passed test FsmoCheck

    Já chequei as configurações de DNS aparentemente esta tudo OK, Alguem tem alguma ideia??

     

     

     

    terça-feira, 27 de abril de 2010 11:25

Respostas

Todas as Respostas

  • isso pode ser "N" coisas.

    já verificou se o serviço de Replicação está habilitado e iniciado nos dois servidores?

    o server novo está com os DNs apontando para o server antigo?

    está habilitado a replicação de DNS entre os servidores?


    Analista de Suporte MCP W2K
    terça-feira, 27 de abril de 2010 13:03
  • Ghustavo,

    o serviço de replicação esta habilitado e iniciado nos dois!

    o server novo esta com o dns apotando para o antigo sim, onde habilito a repllicaçao de DNS entre os servidores?

     

    terça-feira, 27 de abril de 2010 13:07
  • na pressa acho que me expressei mau

    é transferencia de zonas.

    na propriedades da sua zona DNS


    Analista de Suporte MCP W2K
    terça-feira, 27 de abril de 2010 13:11
  • Prezado Hugo,

    Seguem algumas informações do http://technet.microsoft.com/en-us/library/bb727056.aspx#EMAA, sobre troubleshooting do evento 13508.

    Troubleshooting FRS Events 13508 without FRS Event 13509

    FRS event ID 13508 is a warning that the FRS service has been unable to complete the RPC connection to a specific replication partner. It indicates that FRS is having trouble enabling replication with that partner and will keep trying to establish the connection.

    A single FRS event ID 13508 does not mean anything is broken or not working, as long as it is followed by FRS event ID 13509, which indicates that the problem was resolved. Based on the time between FRS event IDs 13508 and 13509, you can determine if a real problem needs to be addressed.

    Note: If FRS is stopped after an event ID 13508 is logged and then later started at a time when the communication issue has been resolved, event ID 13509 will not appear in the event log. In this case, look for an event indicating that FRS has started, and ensure it is not followed by another event 13508.

    Because FRS servers gather replication topology information from the closest domain controller, a replica partner in another site will not be aware of the replica set until the topology information has been replicated to domain controllers in that site. When the topology information finally reaches that distant domain controller, the FRS partner in that site will be able to participate in the replica set and FRS event ID 13509 will be logged. Intrasite Active Directory replication partners replicate every five minutes. Intersite replication only replicates when the schedule is open (the shortest delay is 15 minutes). In addition, FRS polls the topology at defined intervals: five minutes on domain controllers, and one hour on other member servers of a replica set. These delays and schedules can delay propagation of the FRS replication topology, especially in topologies with multiple hops.

    Procedures for Troubleshooting FRS Event 13508 without Event 13509

    1. Examine the FRS event ID 13508 to determine the machine that FRS has been unable to communicate with.

    2. Determine whether the remote machine is working properly, and verify that FRS is running on it. Type the following command at a command prompt on the computer that logged the FRS event ID 13508 and press ENTER:

      ntfrsutl version <FQDN of remote domain controller> 
      

      If this fails, check network connectivity by using the Ping command to ping the fully qualified domain name (FQDN) of the remote domain controller from the computer that logged the FRS event ID 13508. If this fails, then troubleshoot as a DNS or TCP/IP issue. If it succeeds, confirm that the FRS service is started on the remote domain controller.

    3. Determine whether FRS has ever been able to communicate with the remote computer by looking for FRS event ID 13509 in the event log and see if the FRS problem correlates to recent change management to networking, firewalls, DNS configuration, or Active Directory infrastructure.

    4. Determine whether anything between the two machines is capable of blocking RPC traffic, such as a firewall or router.

    5. Confirm that Active Directory replication is working. For more information about troubleshooting Active Directory replication, see Troubleshooting Active Directory Replication Problems in this guide.

    terça-feira, 27 de abril de 2010 13:40
  • Ghustavo,

    A transferencia de zona esta habilitada sim. Eu vi em alguns forums que eu devo reconstruir a arvore de diretorios usando a chave burflags, alguem já fez isso e teve sucesso?

     

    terça-feira, 27 de abril de 2010 20:19
  • Volney,

     

    Ja verifiquei tudo isso e esta tudo ok.

    terça-feira, 27 de abril de 2010 20:20
  • Pessoal,

     

    Consegui resolver utilizando, a clausula BURFLAGS do registro.

     

    Valeu

    • Marcado como Resposta Hugo Mazullo segunda-feira, 3 de maio de 2010 11:37
    segunda-feira, 3 de maio de 2010 11:37