1.Заметил странную вещь. Когда один контроллер недоступен с одного ПК, то даже пинг не проходит, но в этот же момент с другого ПК он доступен и есть пинги.
Запустил PING -t -пинг идет постоянно, но как только перезапустил консоль AD users and Computers, то Пинги c этого ПК пропали.
2. Файервол отключен на обоих контроллерах.
3. В журнале на одном контроллере есть ошибки и предупреждения:
Журнал Dns Server
event ID: 7062
The DNS server encountered a packet addressed to itself on IP address 10.65.0.22. The packet is for the DNS name "72.83.16.199.in-addr.arpa.". The packet will be discarded. This condition usually indicates a configuration error.
Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS server unless subzone is also on this server.
5) Root hints.
Example of self-delegation:
-> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com.
-> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com,
(bar.example.microsoft.com NS dns1.example.microsoft.com)
-> BUT the bar.example.microsoft.com zone is NOT on this server.
Note, you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server, then the self-send could result. If found, the subzone DNS server admin should remove the offending NS record.
You can use the DNS server debug logging facility to track down the cause of this problem.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
event ID:3000
The DNS server has encountered numerous run-time events. To determine the initial cause of these run-time events, examine the DNS server event log entries that precede this event. To prevent the DNS server from filling the event log too quickly, subsequent events with Event IDs higher than 3000 will be suppressed until events are no longer being generated at a high rate.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Журнал: System
event ID: 5722
The session setup from the computer RUD-BUH2 failed to authenticate. The name(s) of the account(s) referenced in the security database is RUD-BUH2$. The following error occurred:
Access is denied.
event ID: 5805
The session setup from the computer ENC-PAB failed to authenticate. The following error occurred:
Access is denied.
4. dcdiag на обоих DC в прикрепленных txt-файлах
