2008 R2 - [решено] Рассинхронизация контроллеров домена Windows 2008 r2

[Telepuzik]

katsman@vk,

В логах на КД какие есть ошибки?


Цитата katsman@vk:



Да, только на DC1 (192.168.45.202)

2008 R2 - [решено] Рассинхронизация контроллеров домена Windows 2008 r2

А если DC1 откажет как сеть будет жить без DNS сервера?

[katsman@vk]

Цитата Telepuzik:



А если DC1 откажет как сеть будет жить без DNS сервера?

2008 R2 - [решено] Рассинхронизация контроллеров домена Windows 2008 r2

Пользуясь случаем, добавил роль DNS на TS1.



Вопрос с синхронизацией все еще не решен.

[katsman@vk]

Цитата Telepuzik:



В логах на КД какие есть ошибки?

2008 R2 - [решено] Рассинхронизация контроллеров домена Windows 2008 r2

[Telepuzik]

Цитата Telepuzik:



В логах на КД какие есть ошибки? »

2008 R2 - [решено] Рассинхронизация контроллеров домена Windows 2008 r2

Есть, полно



DC1







EVENT ID: 2092



This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors are preventing validation of this role.



Operations which require contacting a FSMO operation master will fail until this condition is corrected.



FSMO Role: DC=vilomix-orenburg,DC=ru



User Action:



1. Initial synchronization is the first early replications done by a system as it is starting. A failure to initially synchronize may explain why a FSMO role cannot be validated. This process is explained in KB article 305476.

2. This server has one or more replication partners, and replication is failing for all of these partners. Use the command repadmin /showrepl to display the replication errors. Correct the error in question. For example there maybe problems with IP connectivity, DNS name resolution, or security authentication that are preventing successful replication.

3. In the rare event that all replication partners being down is an expected occurance, perhaps because of maintenance or a disaster recovery, you can force the role to be validated. This can be done by using NTDSUTIL.EXE to seize the role to the same server. This may be done using the steps provided in KB articles 255504 and 324801 on

http://support.microsoft.com

.



The following operations may be impacted:

Schema: You will no longer be able to modify the schema for this forest.

Domain Naming: You will no longer be able to add or remove domains from this forest.

PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Domain Services accounts.

RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.

Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed.





EVENTID: 1864



This is the replication status for the following directory partition on this directory server.



Directory partition:

DC=ForestDnsZones,DC=vilomix-orenburg,DC=ru



This directory server has not recently received replication information from a number of directory servers. The count of directory servers 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:

0

More than a tombstone lifetime:

0

Tombstone lifetime (days):

180



Directory servers that do not replicate in a timely manner may encounter errors. They 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 directory servers by name, use the dcdiag.exe tool.

You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency ".







EVENTID: 2088



Active Directory Domain Services could not use DNS to resolve the IP address of the source domain controller listed below. To maintain the consistency of Security groups, group policy, users and computers and their passwords, Active Directory Domain Services successfully replicated using the NetBIOS or fully qualified computer name of the source domain controller.



Invalid DNS configuration may be affecting other essential operations on member computers, domain controllers or application servers in this Active Directory Domain Services forest, including logon authentication or access to network resources.



You should immediately resolve this DNS configuration error so that this domain controller can resolve the IP address of the source domain controller using DNS.



Alternate server name:

TS1.vilomix-orenburg.ru

Failing DNS host name:

b3b34f71-0441-4f19-9c38-4b20c2769245._msdcs.vilomix-orenburg.ru



NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur. To log all individual failure events, set the following diagnostics registry value to 1:



Registry Path:

HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client



User Action:



1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498.



2) Confirm that the source domain controller is running Active Directory Domain Services and is accessible on the network by typing "net view \\" or "ping ".



3) Verify that the source domain controller is using a valid DNS server for DNS services, and that the source domain controller's host record and CNAME record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE available on

http://www.microsoft.com/dns

dcdiag /test:dns



4) Verify that this destination domain controller is using a valid DNS server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller, as follows:



dcdiag /test:dns



5) For further analysis of DNS error failures see KB 824449:

http://support.microsoft.com/?kbid=824449

Additional Data

Error value:

11004 Запрошенное имя верно, но данные запрошенного типа не найдены.









Вот последнее, мне кажется, ключевое. Где-то в ДНС косяк, мне кажется.



Прикладываю скриншот окна DNS Manager DC1

[katsman@vk]

Цитата katsman@vk:



EVENTID: 2088

Active Directory Domain Services could not use DNS to resolve the IP address of the source domain controller listed below. To maintain the consistency of Security groups, group policy, users and computers and their passwords, Active Directory Domain Services successfully replicated using the NetBIOS or fully qualified computer name of the source domain controller.

2008 R2 - [решено] Рассинхронизация контроллеров домена Windows 2008 r2

Покажите вывод dcdiag /test:dns с обоих КД.

[Telepuzik]

Цитата Telepuzik:



Покажите вывод dcdiag /test:dns с обоих КД.

2008 R2 - [решено] Рассинхронизация контроллеров домена Windows 2008 r2

Вроде все красиво

[katsman@vk]

Цитата katsman@vk:



Прикладываю скриншот окна DNS Manager DC1

2008 R2 - [решено] Рассинхронизация контроллеров домена Windows 2008 r2

Покажите такой же скрин с сервера TS1 можно ничего не затирать.

[Telepuzik]

Цитата Telepuzik:



Покажите такой же скрин с сервера TS1 можно ничего не затирать.

2008 R2 - [решено] Рассинхронизация контроллеров домена Windows 2008 r2

вот

[katsman@vk]

Цитата katsman@vk:



b3b34f71-0441-4f19-9c38-4b20c2769245._msdcs.vilomix-orenburg.ru

2008 R2 - [решено] Рассинхронизация контроллеров домена Windows 2008 r2

Вот эта запись судя по всему лишняя или ошибочная.

[Telepuzik]

Я не сильно сталкивался с такими проблемами, но из курса MCSE нам рекомендовали (в случае если у вас нет статических записий в DNS) удалить зоны на обоих серверах, прописать в сетевых картах серверов оба DNS сервера, и сделать ipconfig /registerdns, тогда все ресурсы каждого сервера заного зарегестрируются, включая AD, PDC, GC, а так же exchange и проиче сервисы которые публикуются в DNS. или можно их по очереди перезапустить, тогда каждый зарегестрируется заного при старте