DC ve ADC Arasında Replikasyon Problemi

Bu konuyu okuyanlar

ferhat_.

Öğrenci
Katılım
13 Eylül 2017
Mesajlar
3
Reaksiyon puanı
0
Puanları
1
Yaş
35
Merhaba,

Yaşanan bir problemden dolayı DC sunucumuzu backuptan döndükten sonra ADC ile arasında replikasyon sorunu yaşadık. dcdiag raporunda SYSVOL replikasyon, time server ve DFSREvent testlerinin failed olduğu gözüküyor. Her iki Domain Controller üzerinde Active Directory Sites and Service kısmında manuel replikasyon yapmaya çalıştığımızda

"The following error occured during the attempt to synchronize naming context spacesun.local from Domain Controller DOMAIN2 to Domain Controller DOMAIN1: The destination server is currently rejecting replication request. This operation will not continue."

bildirimi alıyoruz. DC' de yapmış olduğumuz herhangi bir değişklik ADC' de güncellenmiyor. Yardımlarınızı rica ederim.

PS C:\Users\administrator.SPACESUN> dcdiag

Directory Server Diagnosis

Performing initial setup:
Trying to find home server...
Home Server = DOMAIN1
* Identified AD Forest.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\DOMAIN1
Starting test: Connectivity
......................... DOMAIN1 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DOMAIN1
Starting test: Advertising
Warning: DOMAIN1 is not advertising as a time server.
......................... DOMAIN1 failed test Advertising
Starting test: FrsEvent
......................... DOMAIN1 passed test FrsEvent
Starting test: DFSREvent
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.
......................... DOMAIN1 failed test DFSREvent
Starting test: SysVolCheck
......................... DOMAIN1 passed test SysVolCheck
Starting test: KccEvent
......................... DOMAIN1 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... DOMAIN1 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... DOMAIN1 passed test MachineAccount
Starting test: NCSecDesc
......................... DOMAIN1 passed test NCSecDesc
Starting test: NetLogons
......................... DOMAIN1 passed test NetLogons
Starting test: ObjectsReplicated
......................... DOMAIN1 passed test ObjectsReplicated
Starting test: Replications
[Replications Check,Replications Check] Inbound replication is disabled.
To correct, run "repadmin /options DOMAIN1 -DISABLE_INBOUND_REPL"
[Replications Check,DOMAIN1] Outbound replication is disabled.
To correct, run "repadmin /options DOMAIN1 -DISABLE_OUTBOUND_REPL"
......................... DOMAIN1 failed test Replications
Starting test: RidManager
......................... DOMAIN1 passed test RidManager
Starting test: Services
w32time Service is stopped on [DOMAIN1]
......................... DOMAIN1 failed test Services
Starting test: SystemLog
An error event occurred. EventID: 0x00002716
Time Generated: 09/13/2017 09:48:48
Event String:
DCOM got error "2147944122" from the computer 192.168.51.134 when attempting to activate the server:
An error event occurred. EventID: 0x40000004
Time Generated: 09/13/2017 09:53:28
Event String:
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server systemlab$. The target name used wa
s RPCSS/systemlab.SPACESUN.local. This indicates that the target server failed to decrypt the ticket provided by the cli
ent. This can occur when the target server principal name (SPN) is registered on an account other than the account the t
arget service is using. Ensure that the target SPN is only registered on the account used by the server. This error can
also happen if the target service account password is different than what is configured on the Kerberos Key Distribution
Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same p
assword. If the server name is not fully qualified, and the target domain (YASINKAPLAN.LOCAL) is different from the clie
nt domain (SPACESUN.LOCAL), check if there are identically named server accounts in these two domains, or use the fully-
qualified name to identify the server.
An error event occurred. EventID: 0x0000272C
Time Generated: 09/13/2017 09:53:28
Event String:
DCOM was unable to communicate with the computer 192.168.1.79 using any of the configured protocols; request
ed by PID 63c (C:\Program Files (x86)\Fortinet\FSAE\collectoragent.exe).
An error event occurred. EventID: 0x0000165B
Time Generated: 09/13/2017 10:01:04
Event String:
The session setup from computer 'EMREOZCAKMAK' failed because the security database does not contain a trust
account 'EMREOZCAKMAK$' referenced by the specified computer.
An error event occurred. EventID: 0x00002716
Time Generated: 09/13/2017 10:01:53
Event String:
DCOM got error "2147944122" from the computer 192.168.51.59 when attempting to activate the server:
An error event occurred. EventID: 0xC0001B7A
Time Generated: 09/13/2017 10:03:01
Event String: The CryptologAgent service terminated unexpectedly. It has done this 1 time(s).
An error event occurred. EventID: 0x00002716
Time Generated: 09/13/2017 10:05:23
Event String:
DCOM got error "2147944122" from the computer 192.168.51.134 when attempting to activate the server:
An error event occurred. EventID: 0x000016AD
Time Generated: 09/13/2017 10:06:16
Event String:
The session setup from the computer EMREOZCAKMAK failed to authenticate. The following error occurred:
An error event occurred. EventID: 0x00002716
Time Generated: 09/13/2017 10:09:25
Event String:
DCOM got error "2147944122" from the computer 192.168.51.212 when attempting to activate the server:
An error event occurred. EventID: 0x00002716
Time Generated: 09/13/2017 10:09:34
Event String:
DCOM got error "2147944122" from the computer 192.168.51.59 when attempting to activate the server:
An error event occurred. EventID: 0x00002716
Time Generated: 09/13/2017 10:13:19
Event String:
DCOM got error "2147944122" from the computer 192.168.51.134 when attempting to activate the server:
An error event occurred. EventID: 0x0000272C
Time Generated: 09/13/2017 10:17:35
Event String:
DCOM was unable to communicate with the computer 192.168.1.79 using any of the configured protocols; request
ed by PID 63c (C:\Program Files (x86)\Fortinet\FSAE\collectoragent.exe).
An error event occurred. EventID: 0x00002716
Time Generated: 09/13/2017 10:17:44
Event String:
DCOM got error "2147944122" from the computer 192.168.51.212 when attempting to activate the server:
An error event occurred. EventID: 0x00002716
Time Generated: 09/13/2017 10:21:24
Event String:
DCOM got error "2147944122" from the computer 192.168.51.134 when attempting to activate the server:
An error event occurred. EventID: 0x00002716
Time Generated: 09/13/2017 10:28:51
Event String:
DCOM got error "2147944122" from the computer 192.168.51.147 when attempting to activate the server:
An error event occurred. EventID: 0x0000272C
Time Generated: 09/13/2017 10:35:27
Event String:
DCOM was unable to communicate with the computer 192.168.1.79 using any of the configured protocols; request
ed by PID 63c (C:\Program Files (x86)\Fortinet\FSAE\collectoragent.exe).
An error event occurred. EventID: 0x00002716
Time Generated: 09/13/2017 10:36:02
Event String:
DCOM got error "2147944122" from the computer 192.168.51.59 when attempting to activate the server:
An error event occurred. EventID: 0x00002716
Time Generated: 09/13/2017 10:37:56
Event String:
DCOM got error "2147944122" from the computer 192.168.51.147 when attempting to activate the server:
......................... DOMAIN1 failed test SystemLog
Starting test: VerifyReferences
......................... DOMAIN1 passed test VerifyReferences


Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation

Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones 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 : SPACESUN
Starting test: CheckSDRefDom
......................... SPACESUN passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... SPACESUN passed test CrossRefValidation

Running enterprise tests on : SPACESUN.local
Starting test: LocatorCheck
......................... SPACESUN.local passed test LocatorCheck
Starting test: Intersite
......................... SPACESUN.local passed test Intersite
 

cumhuraltan

Öğrenci
Katılım
2 Mayıs 2017
Mesajlar
23
Reaksiyon puanı
5
Puanları
3
Yaş
42
Selamlar ;

Detay olarak belirtmemişsiniz sadece backuptan dönmüşssünüz ancak imaj backup'tan döndüğünüzü düşünüyorum Dc sunucularda imaj backuptan restore yaparsanız bu tarz sorunları yaşamanız normal yedekten dondugunuz dc yi artık saglıklı bir domain controller olarak kullanmanız pek mümkün olmayacaktır . backuptan dondugunuz dc yı kapatıp ve dns uzerınde gereklı yapılandırmaların duzenlenerek adc olan sunucunun domain controller olarak saglıklı calısıp calısmadıgı test edıldıkten sonra. Root domain controller olarak ayarlanmalı gerekıyorsa Fsmo rolleri seizing yapılmalı ve sonrasında backuptan dondunuz domain controller sunucu uzerındekı actıve dırectory rolunu kaldırmalı ve yenı bır domain controller kurulumu yaparak bu sunucuyu Adc olarak yapılandırmanız sonrasında replikasyonların duzenlenmesi ve duzeltilmesi mümkün olacaktır.
 
Üst