Usuário com melhor resposta
Replicação

Pergunta
-
boa tarde!
estou com problemas de replicação entre os meus servidores, quando eu crio um usuario no AD de um dos meus servidores, ele não apareçe quando a abro os demais, fica só no dele. este prblema começou ontem, não estou conseguindo resolver... voces podem me ajudar?
obrigado.
deem uma olhada neste log:
Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1864
Date: 28/01/2010
Time: 19:55:30
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: KMEX01
Description:
This is the replication status for the following directory partition on the local domain controller.
Directory partition:
DC=ForestDnsZones,DC=KM001,DC=LOCAL
The local domain controller has not recently received replication information from a number of domain controllers. The count of domain controllers is shown, divided into the following intervals.
More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
1
More than a tombstone lifetime:
0
Tombstone lifetime (days):
180
Domain controllers that do not replicate in a timely manner may encounter errors. It may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.
To identify the domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>".For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Respostas
-
Olá Andre.
Vendo o resultado do DCDiag, o primeiro erro que aparece é o 1256. Referente a esse erro encontrei a seguinte Thread:
http://social.technet.microsoft.com/Forums/en/winserverDS/thread/bb0c1b17-ffff-4cbc-b33e-7f85b0ebdbd3
Onde a causa parece ser um problema no DNS.
Veja essa Thread, e tente realizar as dicas passadas, qualquer coisa, nos informe.
Abraço.
Richard Juhasz- Marcado como Resposta Richard Juhasz terça-feira, 9 de fevereiro de 2010 12:06
Todas as Respostas
-
Olá André Brasiliano,
Verifique a ferramenta Serviços e sites do Active Directory, e confira se os servidores que fazem parte da replicação estão dentros os servers.
Verifique também no Ad, a OU Dommain Controllers, checando os servidores dominio estão dentro.
Espero ter ajudado.
Se útil classifique como tal. -
-
-
-
Thiago,
Tenho 04 seridores que se replicam entre...o servidor que está com problema é o servidor que eu tenho o exchange 2003, inclusive, ontem eu tive um problema que ele derrepente parou de reconheçer a base de dados, isso eu consegui arrumar, mas hoje eu precisei criar um usuario por ele, em razão de ja criar também os diretorios de e-mail, mas ele não replicou aos outros servidores, que também possuem o AD e domain controller, inclusive a minha maquina tem o admin pack onde eu administro o domínio. -
-
desculpe!
não, não fiz nada recente e os firewalls do windows estão desabilitados.- Marcado como Resposta André Brasiliano sexta-feira, 29 de janeiro de 2010 18:54
- Editado André Brasiliano sexta-feira, 29 de janeiro de 2010 18:54
- Não Marcado como Resposta Thiago.PereiraModerator sexta-feira, 29 de janeiro de 2010 19:06
-
Olá,
A partir do cd de instalação do Windows Server, na pasta support, execute o suptools.msi, apos a instalção execute o dcdiag e poste os resultados.
Diogo Molina MCP, MCSA, MCSE, MCTS. Ajude manter o forum organizado, se util classifique! Http://diogo-molina.spaces.live.com -
-
-
-
-
Bom dia.
Você consegue baixar da internet sim.
Windows Server 2003 SP 1: http://www.microsoft.com/downloads/details.aspx?FamilyId=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en
Windows Server 2003 SP 2: http://www.microsoft.com/downloads/details.aspx?familyid=96A35011-FD83-419D-939B-9A772EA2DF90&displaylang=en
Abraço.
Se útil, classifique. Matheus M. Bertuco – MCP, MCSA, MCTS.- Sugerido como Resposta Matheus M. BertucoModerator terça-feira, 2 de fevereiro de 2010 18:06
- Não Sugerido como Resposta Thiago.PereiraModerator terça-feira, 2 de fevereiro de 2010 20:27
-
-
Baixe os dois arquivos e execute o suptools.msi.
Como utilizar o Dcdiag: http://www.computerperformance.co.uk/w2k3/utilities/windows_dcdiag.htm
Abraço.
Se útil, classifique. Matheus M. Bertuco – MCP, MCSA, MCTS.- Sugerido como Resposta Matheus M. BertucoModerator terça-feira, 2 de fevereiro de 2010 18:06
- Não Sugerido como Resposta Thiago.PereiraModerator terça-feira, 2 de fevereiro de 2010 20:27
-
-
-
Matheus,
segue abaixo os resultados.
Domain Controller DiagnosisPerforming initial setup:
Done gathering initial info.Doing initial required tests
Testing server: Primeiro-site-padrao\KMEX01
Starting test: Connectivity
......................... KMEX01 passed test ConnectivityDoing primary tests
Testing server: Primeiro-site-padrao\KMEX01
Starting test: Replications
[Replications Check,KMEX01] A recent replication attempt failed:
From KMSVR005 to KMEX01
Naming Context: DC=ForestDnsZones,DC=KM001,DC=LOCAL
The replication generated an error (1256):
Win32 Error 1256
The failure occurred at 2010-02-02 15:55:58.
The last success occurred at 2009-10-23 18:50:16.
2419 failures have occurred since the last success.
[KMSVR005] DsBindWithSpnEx() failed with error 1722,
Win32 Error 1722.
[Replications Check,KMEX01] A recent replication attempt failed:
From KMSVR005 to KMEX01
Naming Context: DC=DomainDnsZones,DC=KM001,DC=LOCAL
The replication generated an error (1256):
Win32 Error 1256
The failure occurred at 2010-02-02 15:55:58.
The last success occurred at 2009-10-23 18:50:16.
2419 failures have occurred since the last success.
[Replications Check,KMEX01] A recent replication attempt failed:
From KMSVR005 to KMEX01
Naming Context: CN=Schema,CN=Configuration,DC=KM001,DC=LOCAL
The replication generated an error (1722):
Win32 Error 1722
The failure occurred at 2010-02-02 15:56:40.
The last success occurred at 2009-10-23 18:50:16.
2420 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,KMEX01] A recent replication attempt failed:
From KMSVR005 to KMEX01
Naming Context: CN=Configuration,DC=KM001,DC=LOCAL
The replication generated an error (1722):
Win32 Error 1722
The failure occurred at 2010-02-02 15:56:19.
The last success occurred at 2009-10-23 19:05:54.
2420 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,KMEX01] A recent replication attempt failed:
From KMSVR005 to KMEX01
Naming Context: DC=KM001,DC=LOCAL
The replication generated an error (1722):
Win32 Error 1722
The failure occurred at 2010-02-02 15:55:58.
The last success occurred at 2009-10-23 19:47:26.
2419 failures have occurred since the last success.
The source remains down. Please check the machine.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source KMEX02
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source KMSVR001
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
REPLICATION-RECEIVED LATENCY WARNING
KMEX01: Current time is 2010-02-02 16:04:31.
DC=ForestDnsZones,DC=KM001,DC=LOCAL
Last replication recieved from KMSVR005 at 2009-10-23 18:54:12.
DC=DomainDnsZones,DC=KM001,DC=LOCAL
Last replication recieved from KMSVR005 at 2009-10-23 18:54:12.
CN=Schema,CN=Configuration,DC=KM001,DC=LOCAL
Last replication recieved from KMSVR005 at 2009-10-23 18:54:12.
CN=Configuration,DC=KM001,DC=LOCAL
Last replication recieved from KMSVR005 at 2009-10-23 19:05:54.
DC=KM001,DC=LOCAL
Last replication recieved from KMSVR005 at 2009-10-23 19:47:51.
......................... KMEX01 passed test Replications
Starting test: NCSecDesc
......................... KMEX01 passed test NCSecDesc
Starting test: NetLogons
......................... KMEX01 passed test NetLogons
Starting test: Advertising
Warning: KMEX01 is not advertising as a time server.
......................... KMEX01 failed test Advertising
Starting test: KnowsOfRoleHolders
Warning: KMSVR005 is the Schema Owner, but is not responding to DS RPC
Bind.
[KMSVR005] LDAP search failed with error 58,
Win32 Error 58.
Warning: KMSVR005 is the Schema Owner, but is not responding to LDAP Bi
nd.
Warning: KMSVR005 is the Domain Owner, but is not responding to DS RPC
Bind.
Warning: KMSVR005 is the Domain Owner, but is not responding to LDAP Bi
nd.
Warning: KMSVR005 is the PDC Owner, but is not responding to DS RPC Bin
d.
Warning: KMSVR005 is the PDC Owner, but is not responding to LDAP Bind.Warning: KMSVR005 is the Rid Owner, but is not responding to DS RPC Bin
d.
Warning: KMSVR005 is the Rid Owner, but is not responding to LDAP Bind.Warning: KMSVR005 is the Infrastructure Update Owner, but is not respon
ding to DS RPC Bind.
Warning: KMSVR005 is the Infrastructure Update Owner, but is not respon
ding to LDAP Bind.
......................... KMEX01 failed test KnowsOfRoleHolders
Starting test: RidManager
......................... KMEX01 failed test RidManager
Starting test: MachineAccount
......................... KMEX01 passed test MachineAccount
Starting test: Services
......................... KMEX01 passed test Services
Starting test: ObjectsReplicated
......................... KMEX01 passed test ObjectsReplicated
Starting test: frssysvol
......................... KMEX01 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.
......................... KMEX01 failed test frsevent
Starting test: kccevent
......................... KMEX01 passed test kccevent
Starting test: systemlog
......................... KMEX01 passed test systemlog
Starting test: VerifyReferences
......................... KMEX01 passed test VerifyReferencesRunning partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidationStarting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDomRunning partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidationStarting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDomRunning partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDomRunning partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDomRunning partition tests on : KM001
Starting test: CrossRefValidation
......................... KM001 passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... KM001 passed test CheckSDRefDomRunning enterprise tests on : KM001.LOCAL
Starting test: Intersite
......................... KM001.LOCAL passed test Intersite
Starting test: FsmoCheck -
-
-
Olá Andre.
Vendo o resultado do DCDiag, o primeiro erro que aparece é o 1256. Referente a esse erro encontrei a seguinte Thread:
http://social.technet.microsoft.com/Forums/en/winserverDS/thread/bb0c1b17-ffff-4cbc-b33e-7f85b0ebdbd3
Onde a causa parece ser um problema no DNS.
Veja essa Thread, e tente realizar as dicas passadas, qualquer coisa, nos informe.
Abraço.
Richard Juhasz- Marcado como Resposta Richard Juhasz terça-feira, 9 de fevereiro de 2010 12:06