Usuário com melhor resposta
File Replication Service is unable to replicate

Pergunta
-
Srs. Help!
Tenho 3 sites, um DC em cada site. O DC SERVIDOR04 foi criado há pouco tempo, assim que criamos o novo site IPANEMA, vimos que GPOs não estavam sendo aplicadas e netlogon não replicava. O SERVIDOR01 (FSMO) estava com erro na estrutura SYSVOL. Executei o Nonauthoritative restore por esse kb: http://support.microsoft.com/kb/290762/en-us . À partir daí o DC SERVIDOR04 recém criado passou a travar, e no momento de travamento encontro esse evento nos outros DCs:
Log Name: File Replication Service
Source: NtFrs
Event ID: 13548The File Replication Service is unable to replicate with its partner computer because the difference in clock times is outside the range of plus or minus 30 minutes.
The connection to the partner computer is: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)\SERVIDOR01\SERVIDOR01 -> DOMAIN\SERVIDOR04$ RemoteCxt" The detected time difference is: 177 minutes.
Note: If this time difference is close to a multiple of 60 minutes then it is likely that either this computer or its partner computer was set to the incorrect time zone whenthe computer time was initially set. Check that the time zone and the system time are correctly set on both computers.
If necessary, the default value used to test for computer time consistency may be changed in the registry on this computer. (Note: This is not recommended.)
To change this parameter, run regedit.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Partner Clock Skew In Minutes" and update the value.O horário está ok!
O AD está replicando com sucesso entre os DC, vejo no repadmin /showrepl:
Repadmin: running command /showrepl against full DC localhost
IPANEMA\SERVIDOR04
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 200b0ea5-6c69-4a7f-a45e-3f940d60e935
DSA invocationID: 25685b08-d374-4414-b2fa-caf1ea623964
==== INBOUND NEIGHBORS ======================================
DC=domain,DC=rede
SP\SERVIDOR03 via RPC
DSA object GUID: 3b9b4e90-c5b3-424f-bb82-1c349c7a5702
Last attempt @ 2014-05-19 17:58:51 was successful.
LEBLON\SERVIDOR01 via RPC
DSA object GUID: 34c5c77b-6abd-40dc-ad3b-7b02bb7b5ab1
Last attempt @ 2014-05-19 17:58:51 was successful.
CN=Configuration,DC=domian,DC=rede
SP\SERVIDOR03 via RPC
DSA object GUID: 3b9b4e90-c5b3-424f-bb82-1c349c7a5702
Last attempt @ 2014-05-19 17:58:51 was successful.
LEBLON\SERVIDOR01 via RPC
DSA object GUID: 34c5c77b-6abd-40dc-ad3b-7b02bb7b5ab1
Last attempt @ 2014-05-19 17:58:51 was successful.
CN=Schema,CN=Configuration,DC=domain,DC=rede
SP\SERVIDOR03 via RPC
DSA object GUID: 3b9b4e90-c5b3-424f-bb82-1c349c7a5702
Last attempt @ 2014-05-19 17:58:51 was successful.
LEBLON\SERVIDOR01 via RPC
DSA object GUID: 34c5c77b-6abd-40dc-ad3b-7b02bb7b5ab1
Last attempt @ 2014-05-19 17:58:51 was successful.
DC=DomainDnsZones,DC=domain,DC=rede
SP\SERVIDOR03 via RPC
DSA object GUID: 3b9b4e90-c5b3-424f-bb82-1c349c7a5702
Last attempt @ 2014-05-19 17:58:51 was successful.
LEBLON\SERVIDOR01 via RPC
DSA object GUID: 34c5c77b-6abd-40dc-ad3b-7b02bb7b5ab1
Last attempt @ 2014-05-19 17:58:51 was successful.
DC=ForestDnsZones,DC=domain,DC=rede
SP\SERVIDOR03 via RPC
DSA object GUID: 3b9b4e90-c5b3-424f-bb82-1c349c7a5702
Last attempt @ 2014-05-19 17:58:52 was successful.
LEBLON\SERVIDOR01 via RPC
DSA object GUID: 34c5c77b-6abd-40dc-ad3b-7b02bb7b5ab1
Last attempt @ 2014-05-19 17:58:52 was successful.
Repadmin: running command /showrepl against full DC localhost
LEBLON\SERVIDOR01
DSA Options: IS_GC
Site Options: W2K3_BRIDGES_REQUIRED
DSA object GUID: 34c5c77b-6abd-40dc-ad3b-7b02bb7b5ab1
DSA invocationID: 635fb5e9-525a-409c-aeae-16a84e27d0a8
==== INBOUND NEIGHBORS ======================================
DC=domain,DC=rede
SP\SERVIDOR03 via RPC
DSA object GUID: 3b9b4e90-c5b3-424f-bb82-1c349c7a5702
Last attempt @ 2014-05-19 17:54:56 was successful.
IPANEMA\SERVIDOR04 via RPC
DSA object GUID: 200b0ea5-6c69-4a7f-a45e-3f940d60e935
Last attempt @ 2014-05-19 17:54:58 was successful.
LEBLON\SERVIDOR02 via RPC
DSA object GUID: 7d30a8b7-f093-45c1-b260-f842768c046c
Last attempt @ 2014-05-19 18:04:52 was successful.
CN=Configuration,DC=domain,DC=rede
LEBLON\SERVIDOR02 via RPC
DSA object GUID: 7d30a8b7-f093-45c1-b260-f842768c046c
Last attempt @ 2014-05-19 17:54:57 was successful.
SP\SERVIDOR03 via RPC
DSA object GUID: 3b9b4e90-c5b3-424f-bb82-1c349c7a5702
Last attempt @ 2014-05-19 17:54:57 was successful.
IPANEMA\SERVIDOR04 via RPC
DSA object GUID: 200b0ea5-6c69-4a7f-a45e-3f940d60e935
Last attempt @ 2014-05-19 17:54:57 was successful.
CN=Schema,CN=Configuration,DC=domain,DC=rede
LEBLON\SERVIDOR02 via RPC
DSA object GUID: 7d30a8b7-f093-45c1-b260-f842768c046c
Last attempt @ 2014-05-19 17:54:57 was successful.
SP\SERVIDOR03 via RPC
DSA object GUID: 3b9b4e90-c5b3-424f-bb82-1c349c7a5702
Last attempt @ 2014-05-19 17:54:58 was successful.
IPANEMA\SERVIDOR04 via RPC
DSA object GUID: 200b0ea5-6c69-4a7f-a45e-3f940d60e935
Last attempt @ 2014-05-19 17:54:58 was successful.
DC=DomainDnsZones,DC=domain,DC=rede
SP\SERVIDOR03 via RPC
DSA object GUID: 3b9b4e90-c5b3-424f-bb82-1c349c7a5702
Last attempt @ 2014-05-19 17:54:58 was successful.
IPANEMA\SERVIDOR04 via RPC
DSA object GUID: 200b0ea5-6c69-4a7f-a45e-3f940d60e935
Last attempt @ 2014-05-19 17:54:59 was successful.
LEBLON\SERVIDOR02 via RPC
DSA object GUID: 7d30a8b7-f093-45c1-b260-f842768c046c
Last attempt @ 2014-05-19 17:55:29 was successful.
DC=ForestDnsZones,DC=domain,DC=rede
LEBLON\SERVIDOR02 via RPC
DSA object GUID: 7d30a8b7-f093-45c1-b260-f842768c046c
Last attempt @ 2014-05-19 17:54:57 was successful.
SP\SERVIDOR03 via RPC
DSA object GUID: 3b9b4e90-c5b3-424f-bb82-1c349c7a5702
Last attempt @ 2014-05-19 17:54:59 was successful.
IPANEMA\SERVIDOR04 via RPC
DSA object GUID: 200b0ea5-6c69-4a7f-a45e-3f940d60e935
Last attempt @ 2014-05-19 17:54:59 was successful.
O sites and services está configurado corretamente.
Estou pensando em passar a FSMO para outro DC.
Obrigado!
Luiz Cataldo MCP/MCSA W2k3 CNA NW 4.11 FCSE
terça-feira, 20 de maio de 2014 11:13
Respostas
-
Bom, apesar de o repadmin informar sucesso na replicação e você citar que o horário esta correto:
- Os servidores estão atualizados ?
- O sysvol esta acessível em todos os servidores, as permissões estão compatíveis ?
- Todos os DC's identificam as FSMO's ? netdom query fsmo
- Erros na execução do comando dcdiag e dcdiag /test:dns ?
- Reiniciando o FRS gera algum evento de erro adicional ?
- Pelo sites and services executando uma replicação manual, gera algum erro ?
abs,
Não se pode ensinar alguma coisa a um homem; apenas ajudá-lo a encontrá-lo dentro de si mesmo.
- Marcado como Resposta Luiz Cataldo quarta-feira, 21 de maio de 2014 18:34
terça-feira, 20 de maio de 2014 11:32
Todas as Respostas
-
Bom, apesar de o repadmin informar sucesso na replicação e você citar que o horário esta correto:
- Os servidores estão atualizados ?
- O sysvol esta acessível em todos os servidores, as permissões estão compatíveis ?
- Todos os DC's identificam as FSMO's ? netdom query fsmo
- Erros na execução do comando dcdiag e dcdiag /test:dns ?
- Reiniciando o FRS gera algum evento de erro adicional ?
- Pelo sites and services executando uma replicação manual, gera algum erro ?
abs,
Não se pode ensinar alguma coisa a um homem; apenas ajudá-lo a encontrá-lo dentro de si mesmo.
- Marcado como Resposta Luiz Cataldo quarta-feira, 21 de maio de 2014 18:34
terça-feira, 20 de maio de 2014 11:32 -
Qdo reinicio Ntfrs recebo esse evento:
File Replication Service is no longer preventing the computer SERVIDOR04 from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.
Todos os DCs responder a query FSMO com sucesso:
C:\>netdom query fsmo
Schema master SERVIDOR01.domain.rede
Domain naming master SERVIDOR01.domain.rede
PDC SERVIDOR01.domain.rede
RID pool manager SERVIDOR01.domain.rede
Infrastructure master SERVIDOR01.domain.rede
The command completed successfully.\\servidores\netlogon estão ativos respondendo e sincronizando, criei um TXT e foi replicado para todos.
GPO, é sempre um problema, tá aplicando com sucesso servidores e estações:
C:\>gpupdate /force
Updating policy...Computer Policy update has completed successfully.
Encontrei erros no DNS, estou analizando. FIZ COMENTÁRIOS ABAIXO.
C:\>dcdiag /test:dns
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = SERVIDOR04
* Identified AD Forest.
Done gathering initial info.Doing initial required tests
Testing server: IPANEMA\SERVIDOR04
Starting test: Connectivity
......................... SERVIDOR04 passed test ConnectivityDoing primary tests
Testing server: IPANEMA\SERVIDOR04
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... SERVIDOR04 passed test DNSRunning partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : gespat
Running enterprise tests on : gespat.rede
Starting test: DNS
Test results for domain controllers:DC: SERVIDOR04.gespat.rede
Domain: gespat.rede
TEST: Delegations (Del)
Error: DNS server: server01.gespat.rede. IP:<Unavailable>
[Missing glue A record]TEST: Records registration (RReg) - isso aqui é uma NIC adicional (Storage)
Network Adapter
[00000012] HP Ethernet 1Gb 4-port 331FLR Adapter:
Warning:
Missing A record at DNS server 169.254.0.1:
SERVIDOR04.gespat.redeWarning:
Missing A record at DNS server 169.254.0.1:
gc._msdcs.gespat.redeWarning: Record Registrations not found in some network adapters
Summary of test results for DNS servers used by the above domain
controllers:DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 128.8.10.90
DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:1::803f:235DNS server: 2001:500:2::c (c.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2::cDNS server: 2001:500:2d::d (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2d::dDNS server: 2001:500:2f::f (f.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2f::fDNS server: 2001:500:3::42 (l.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:3::42DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:ba3e::2:30DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:c27::2:30DNS server: 2001:7fd::1 (k.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fd::1DNS server: 2001:7fe::53 (i.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fe::53DNS server: 2001:dc3::35 (m.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:dc3::35Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
_________________________________________________________________
Domain: gespat.rede
SERVIDOR04 PASS PASS PASS FAIL PASS WARN n/a......................... gespat.rede failed test DNS
Luiz Cataldo MCP/MCSA W2k3 CNA NW 4.11 FCSE
terça-feira, 20 de maio de 2014 12:04 -
Acredito que seja o seu único problema, esses endereços APIPA registrados no DNS para o servidor04 inclusive indicando como GC um endereço automático. dá uma verificada no seu DNS. depois execute um dcdiag no servidor para uma verificação completa.
TEST: Delegations (Del)
Error: DNS server: server01.gespat.rede. IP:<Unavailable>
[Missing glue A record]Domain: gespat.rede
SERVIDOR04 PASS PASS PASS FAIL PASS WARN n/a......................... gespat.rede failed test DNS
abs,
Não se pode ensinar alguma coisa a um homem; apenas ajudá-lo a encontrá-lo dentro de si mesmo.
- Editado Felipe Feydit terça-feira, 20 de maio de 2014 12:25
- Sugerido como Resposta Luiz Felipe S. T. Costa quarta-feira, 21 de maio de 2014 11:08
terça-feira, 20 de maio de 2014 12:20 -
Felipe, acho que existem alguns erros pequenos no DNS, mas que não justifica o travamento. Depois dos questionamentos que você me fez e os testes que fiz em seguida, faz eu pensar que o problema agora pode não ser mais AD e o travamento tenha outra origem. Muito obrigado, tendo algo relevante colocarei aqui e marcarei seu post que foi muito útil.
abç
Luiz Cataldo MCP/MCSA W2k3 CNA NW 4.11 FCSE
terça-feira, 20 de maio de 2014 12:57 -
Ok. Talvez um teste de hardware seja apropriado.
Ficamos no aguardo.
abs,
Não se pode ensinar alguma coisa a um homem; apenas ajudá-lo a encontrá-lo dentro de si mesmo.
- Sugerido como Resposta Luiz Felipe S. T. Costa terça-feira, 20 de maio de 2014 16:18
terça-feira, 20 de maio de 2014 13:00 -
Srs.
Identificado, o serviço de DFS que estava travando o servidor por um problema de link.
Obrigado!
Luiz Cataldo MCP/MCSA W2k3 CNA NW 4.11 FCSE
quarta-feira, 21 de maio de 2014 18:34