Forum
Bildirimler
Hepsini Temizle
Windows Server
6
Yazılar
3
Üyeler
0
Reactions
1,057
Görüntüleme
Konu başlatıcı
2 adet domain controllerımız var fakat replikasyon hataları almaktayım. Event id:1863 - 1864 gibi hatalar almaktayım. Birkaç çözüm denedim fakat sonuç alamadım
repadmin /removelingeringobjects invsrv01.inviso.local ac44b376-8b5d-41d9-aed4-db794a7be41c dc=inviso,dc=local /advisory_mode bu komutu çalıştırdığımda aşağıdaki hatayı alıyorum
DsBindWithCred to invsrv01.INVISO.LOCAL failed with status 1722 (0x6ba):
Can't retrieve message string 1722 (0x6ba), error 1815.
Manuel olarak replikasyon başlattığımda ise aşağıdaki hatayı alıyorum
"Target Principal Name is Incorrect"
Bu hata ile ilgili olarakta microsoftun makalesindeki
netdom resetpwd /server:server_name /userd:domain_name\administrator /passwordd:administrator_password adımlarını uyguladım ve aşağıdaki hatayı aldım
The machine account password for the local machine could not be reset.
Logon Failure: The target account name is incorrect.
The command failed to complete successfully.
Bu konu ile ilgili yapılabilecek birşey varmı domaini baştan kurmak çok zor bir iş çok fazla ayar ve kurulum mevcut DC lerin tekinde exchange 2003 kurulu bilgi olarak vermek istedim.Yardımlarınız için şimdiden teşekkürler.
Ayıca yapı hakkında biraz bilgi veriyim
server isimleri invsrv01 ve invsrv02 invsrv01 üzerinde exchange mevcut ayrıca invsrv01 FSMO rollerine sahip
Schema owner invsrv01.INVISO.LOCAL
Domain role owner invsrv01.INVISO.LOCAL
PDC role invsrv01.INVISO.LOCAL
RID pool manager invsrv01.INVISO.LOCAL
Infrastructure owner invsrv01.INVISO.LOCAL
repadmin /showrepl çıktısıda aşağıdaki gibi invsrv01 üzerinde çalıştırdığım komut
repadmin running command /showrepl against server localhost
Default-First-Site-Name\INVSRV01
DC Options: IS_GC
Site Options: (none)
DC object GUID: 1e7106fe-b72d-4d92-8c30-bd6ad8368357
DC invocationID: 1e7106fe-b72d-4d92-8c30-bd6ad8368357
==== INBOUND NEIGHBORS ======================================
DC=INVISO,DC=LOCAL
Default-First-Site-Name\INVSRV02 via RPC
DC object GUID: ac44b376-8b5d-41d9-aed4-db794a7be41c
Last attempt @ 2010-07-18 07:55:22 failed, result 8606 (0x21
Can't retrieve message string 8606 (0x219e), error 1815.
241792 consecutive failure(s).
Last success @ 2009-09-30 17:04:34.
CN=Configuration,DC=INVISO,DC=LOCAL
Default-First-Site-Name\INVSRV02 via RPC
DC object GUID: ac44b376-8b5d-41d9-aed4-db794a7be41c
Last attempt @ 2010-07-18 07:55:22 was successful.
CN=Schema,CN=Configuration,DC=INVISO,DC=LOCAL
Default-First-Site-Name\INVSRV02 via RPC
DC object GUID: ac44b376-8b5d-41d9-aed4-db794a7be41c
Last attempt @ 2010-07-18 07:55:22 was successful.
DC=DomainDnsZones,DC=INVISO,DC=LOCAL
Default-First-Site-Name\INVSRV02 via RPC
DC object GUID: ac44b376-8b5d-41d9-aed4-db794a7be41c
Last attempt @ 2010-07-18 07:55:22 was successful.
DC=ForestDnsZones,DC=INVISO,DC=LOCAL
Default-First-Site-Name\INVSRV02 via RPC
DC object GUID: ac44b376-8b5d-41d9-aed4-db794a7be41c
Last attempt @ 2010-07-18 07:55:22 was successful.
Source: Default-First-Site-Name\INVSRV02
**** 241792 CONSECUTIVE FAILURES since 2009-09-30 17:04:34
Last error: 8606 (0x219e):
Can't retrieve message string 8606 (0x219e), error 1815.
Buda invsrv02 üzerinde çalıştırdığım komut çıktısı
repadmin running command /showrepl against server localhost
Default-First-Site-Name\INVSRV02
DC Options: (none)
Site Options: (none)
DC object GUID: ac44b376-8b5d-41d9-aed4-db794a7be41c
DC invocationID: c06190f6-6e76-44dc-a85a-84112beb8c47
==== INBOUND NEIGHBORS ======================================
DC=INVISO,DC=LOCAL
Default-First-Site-Name\INVSRV01 via RPC
DC object GUID: 1e7106fe-b72d-4d92-8c30-bd6ad8368357
Last attempt @ 2010-07-18 08:54:08 failed, result -2146893022 (0x800903
2):
Can't retrieve message string -2146893022 (0x80090322), error 1815.
57421 consecutive failure(s).
Last success @ 2010-04-01 18:20:31.
CN=Configuration,DC=INVISO,DC=LOCAL
Default-First-Site-Name\INVSRV01 via RPC
DC object GUID: 1e7106fe-b72d-4d92-8c30-bd6ad8368357
Last attempt @ 2010-07-18 08:55:37 failed, result -2146893022 (0x800903
2):
Can't retrieve message string -2146893022 (0x80090322), error 1815.
181 consecutive failure(s).
Last success @ 2010-07-15 19:04:40.
CN=Schema,CN=Configuration,DC=INVISO,DC=LOCAL
Default-First-Site-Name\INVSRV01 via RPC
DC object GUID: 1e7106fe-b72d-4d92-8c30-bd6ad8368357
Last attempt @ 2010-07-18 08:52:06 failed, result -2146893022 (0x800903
2):
Can't retrieve message string -2146893022 (0x80090322), error 1815.
63 consecutive failure(s).
Last success @ 2010-07-15 18:51:49.
DC=ForestDnsZones,DC=INVISO,DC=LOCAL
Default-First-Site-Name\INVSRV01 via RPC
DC object GUID: 1e7106fe-b72d-4d92-8c30-bd6ad8368357
Last attempt @ 2010-07-18 08:52:06 failed, result 1256 (0x4e8):
Can't retrieve message string 1256 (0x4e8), error 1815.
63 consecutive failure(s).
Last success @ 2010-07-15 18:51:49.
DC=DomainDnsZones,DC=INVISO,DC=LOCAL
Default-First-Site-Name\INVSRV01 via RPC
DC object GUID: 1e7106fe-b72d-4d92-8c30-bd6ad8368357
Last attempt @ 2010-07-18 08:55:40 failed, result -2146893022 (0x800903
2):
Can't retrieve message string -2146893022 (0x80090322), error 1815.
96 consecutive failure(s).
Last success @ 2010-07-15 18:51:49.
Source: Default-First-Site-Name\INVSRV01
**** 57416 CONSECUTIVE FAILURES since 2010-07-15 19:04:40
Last error: -2146893022 (0x80090322):
Can't retrieve message string -2146893022 (0x80090322), error 1815.
Gönderildi : 19/07/2010 14:58
administrator kullanıcısının usernamei gerçekten administrator olarak mı geçiyor, sonradan değiştirmiş olabilir misiniz? Komut bundan çalışmamış olabilir. ayrıca "dcdiag /test:dns" komutunun sonuçlarını paylaşır mısınız? Netlogon servisinizin düzgün çalışıp çalışmadığını kontrol edin. DNS kayıtlarınızı netdiag /fix komutuyla güncelleyin. İki makinenin dns ayarlarının düzgün çalıştığına emin olduktan sonra replikasyonu tekrar deneyin.
Gönderildi : 19/07/2010 15:21
Konu başlatıcı
INVSRV01 Üzerindeki komut çıktısı
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\INVSRV01
Starting test: Connectivity
......................... INVSRV01 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\INVSRV01
DNS Tests are running and not hung. Please wait a few minutes...
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : INVISO
Running enterprise tests on : INVISO.LOCAL
Starting test: DNS
Test results for domain controllers:
DC: invsrv01.INVISO.LOCAL
Domain: INVISO.LOCAL
TEST: Forwarders/Root hints (Forw)
Error: Root hints list has invalid root hint server: a.root-servers.net. (198.41.0.4)
Error: Root hints list has invalid root hint server: b.root-servers.net. (192.228.79.201)
Error: Root hints list has invalid root hint server: c.root-servers.net. (192.33.4.12)
Error: Root hints list has invalid root hint server: d.root-servers.net. (128.8.10.90)
Error: Root hints list has invalid root hint server: e.root-servers.net. (192.203.230.10)
Error: Root hints list has invalid root hint server: f.root-servers.net. (192.5.5.241)
Error: Root hints list has invalid root hint server: g.root-servers.net. (192.112.36.4)
Error: Root hints list has invalid root hint server: h.root-servers.net. (128.63.2.53)
Error: Root hints list has invalid root hint server: i.root-servers.net. (192.36.148.17)
Error: Root hints list has invalid root hint server: j.root-servers.net. (192.58.128.30)
Error: Root hints list has invalid root hint server: k.root-servers.net. (193.0.14.129)
Error: Root hints list has invalid root hint server: l.root-servers.net. (199.7.83.42)
Error: Root hints list has invalid root hint server: m.root-servers.net. (202.12.27.33)
Summary of test results for DNS servers used by the above domain controllers:
DNS server: 128.63.2.53 (h.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
128.63.2.53
DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
128.8.10.90
DNS server: 192.112.36.4 (g.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.112.36.4
DNS server: 192.203.230.10 (e.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.203.230.10
DNS server: 192.228.79.201 (b.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.228.79.201
DNS server: 192.33.4.12 (c.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.33.4.12
DNS server: 192.36.148.17 (i.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.36.148.17
DNS server: 192.5.5.241 (f.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.5.5.241
DNS server: 192.58.128.30 (j.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.58.128.30
DNS server: 193.0.14.129 (k.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
193.0.14.129
DNS server: 198.41.0.4 (a.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
198.41.0.4
DNS server: 199.7.83.42 (l.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
199.7.83.42
DNS server: 202.12.27.33 (m.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
202.12.27.33
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
________________________________________________________________
Domain: INVISO.LOCAL
invsrv01 PASS PASS FAIL PASS PASS PASS n/a
......................... INVISO.LOCAL failed test DNS
C:\Documents and Settings\Administrator>
INVSRV02 Üzerindeki komut çıktısı
C:\Documents and Settings\Administrator.INVISO>dcdiag /test:dns
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\INVSRV02
Starting test: Connectivity
......................... INVSRV02 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\INVSRV02
DNS Tests are running and not hung. Please wait a few minutes...
Running partition tests on : DomainDnsZones
Running partition tests on : ForestDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : INVISO
Running enterprise tests on : INVISO.LOCAL
Starting test: DNS
Test results for domain controllers:
DC: invsrv02.INVISO.LOCAL
Domain: INVISO.LOCAL
TEST: Forwarders/Root hints (Forw)
Error: Root hints list has invalid root hint server: a.root-servers.net. (198.41.0.4)
Error: Root hints list has invalid root hint server: b.root-servers.net. (192.228.79.201)
Error: Root hints list has invalid root hint server: c.root-servers.net. (192.33.4.12)
Error: Root hints list has invalid root hint server: d.root-servers.net. (128.8.10.90)
Error: Root hints list has invalid root hint server: e.root-servers.net. (192.203.230.10)
Error: Root hints list has invalid root hint server: f.root-servers.net. (192.5.5.241)
Error: Root hints list has invalid root hint server: g.root-servers.net. (192.112.36.4)
Error: Root hints list has invalid root hint server: h.root-servers.net. (128.63.2.53)
Error: Root hints list has invalid root hint server: i.root-servers.net. (192.36.148.17)
Error: Root hints list has invalid root hint server: j.root-servers.net. (192.58.128.30)
Error: Root hints list has invalid root hint server: k.root-servers.net. (193.0.14.129)
Error: Root hints list has invalid root hint server: l.root-servers.net. (199.7.83.42)
Error: Root hints list has invalid root hint server: m.root-servers.net. (202.12.27.33)
Summary of test results for DNS servers used by the above domain controllers:
DNS server: 128.63.2.53 (h.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS serve
128.63.2.53
DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS serve
128.8.10.90
DNS server: 192.112.36.4 (g.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS serve
192.112.36.4
DNS server: 192.203.230.10 (e.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS serve
192.203.230.10
DNS server: 192.228.79.201 (b.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS serve
192.228.79.201
DNS server: 192.33.4.12 (c.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS serve
192.33.4.12
DNS server: 192.36.148.17 (i.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS serve
192.36.148.17
DNS server: 192.5.5.241 (f.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS serve
192.5.5.241
DNS server: 192.58.128.30 (j.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS serve
192.58.128.30
DNS server: 193.0.14.129 (k.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS serve
193.0.14.129
DNS server: 198.41.0.4 (a.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS serve
198.41.0.4
DNS server: 199.7.83.42 (l.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS serve
199.7.83.42
DNS server: 202.12.27.33 (m.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS serve
202.12.27.33
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
________________________________________________________________
Domain: INVISO.LOCAL
invsrv02 PASS PASS FAIL PASS PASS PASS n/a
......................... INVISO.LOCAL failed test DNS
C:\Documents and Settings\Administrator.INVISO>
Kullanıcı adı administrator değiştirmedik,netlogon servisleri her iki sunucu üzerinde çalşır durumda,netdiag /fix komutunu çalıştırdım fakat replikasyon yine başlamadı
Gönderildi : 19/07/2010 15:40
iki sunucuda da forwarders ve root hintslerle ilgili hata var, her iki sunucu için dns servisini kaldırıp baştan yapılandırın. Tekrar netdiag /fix komutunu iki tarafta da çalıştırın. 15 dk sonra replikasyon işlemini deneyin. Bu arada event viewerları temizleyin ve yeni oluşacak hataları görmeniz kolay olsun.
Gönderildi : 19/07/2010 15:58
alper hocam
netdiag/fix yapıldığında silinen dns teki kullanıcılar 15dk. sonra gelirmi. yenidenmi kullanıcı oluşturacağız dns te.
Gönderildi : 20/07/2010 14:31
sistem2010, dnste kullanıcılar değil kayıtlar bulunur. Kavram karmaşası olmasın. DNS konusunu tekrar gözden geçirmeni önereceğim. Netdiag /fix olmayan kayıtları getirmen için sana yardımcı olacak komut türü. Yeni replike süresi 15 dk.
Gönderildi : 21/07/2010 12:24
