none
DsBindWithCred to Aed failed with status 1722 (0x6ba). The RPC server is unavailable. RRS feed

  • Общие обсуждения

  • Добрый день, коллеги!

    При подготовке к переходу с FRS на DRS-R, обнаружил на одном из  DC проблемы с репликацией, а именно с доступностью RPC.

    Время запуска сводки по репликации: 2017-05-29 12:07:24

    Начат сбор данных для сводки по репликации, подождите:
      ......


    Исходный DSA        наиб. дельта     сбоев/всего %%   ошибка
     DC0                       19m:02s    0 /  10    0
     DC1                       19m:02s    0 /  10    0
     MDC120           >60 days            5 /  10   50  (1722) Сервер RPC недоступен.


    Конечный DSA        наиб. дельта      сбои/всего %%   ошибка
     DC0              >60 days            5 /  10   50  (1722) Сервер RPC недоступен.
     DC1                       13m:48s    0 /  10    0
     MDC120                    19m:03s    0 /  10    0



    Если запустить принудительную синхронизации на всех DC ругается на RPC:

    PS C:\Windows\system32> repadmin /syncall Aed
    DsBindWithCred to Aed failed with status 1722 (0x6ba):
        The RPC server is unavailable.


    На проблемном DC0 DCDIAG выдает следующее, на остальных проверка репликации проходит:

    Directory Server Diagnosis

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

    Doing initial required tests

       Testing server: Moscow\DC0
          Starting test: Connectivity
             ......................... DC0 passed test Connectivity

    Doing primary tests

       Testing server: Moscow\DC0
          Starting test: Advertising
             ......................... DC0 passed test Advertising
          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.
             ......................... DC0 passed test FrsEvent
          Starting test: DFSREvent
             ......................... DC0 passed test DFSREvent
          Starting test: SysVolCheck
             ......................... DC0 passed test SysVolCheck
          Starting test: KccEvent
             ......................... DC0 passed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... DC0 passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... DC0 passed test MachineAccount
          Starting test: NCSecDesc
             ......................... DC0 passed test NCSecDesc
          Starting test: NetLogons
             ......................... DC0 passed test NetLogons
          Starting test: ObjectsReplicated
             ......................... DC0 passed test ObjectsReplicated
          Starting test: Replications
             [Replications Check,DC0] A recent replication attempt failed:
                From MDC120 to DC0
                Naming Context: DC=ForestDnsZones,DC=xxx,DC=local
                The replication generated an error (1256):
                The remote system is not available. For information about network troubleshooting, see Windows Help.
                The failure occurred at 2017-05-29 12:55:21.
                The last success occurred at 2016-11-04 04:28:11.
                5133 failures have occurred since the last success.
             REPLICATION LATENCY WARNING
             ERROR: Expected notification link is missing.
             Source MDC120
             Replication of new changes along this path will be delayed.
             This problem should self-correct on the next periodic sync.
             [Replications Check,DC0] A recent replication attempt failed:
                From MDC120 to DC0
                Naming Context: DC=DomainDnsZones,DC=xx,DC=local
                The replication generated an error (1256):
                The remote system is not available. For information about network troubleshooting, see Windows Help.
                The failure occurred at 2017-05-29 12:55:21.
                The last success occurred at 2016-11-04 04:51:53.
                21279 failures have occurred since the last success.
             [Replications Check,DC0] A recent replication attempt failed:
                From MDC120 to DC0
                Naming Context: CN=Schema,CN=Configuration,DC=xx,DC=local
                The replication generated an error (1722):
                The RPC server is unavailable.
                The failure occurred at 2017-05-29 12:56:45.
                The last success occurred at 2016-11-04 04:26:33.
                5025 failures have occurred since the last success.
                The source MDC120 is responding now.
             REPLICATION LATENCY WARNING
             ERROR: Expected notification link is missing.
             Source MDC120
             Replication of new changes along this path will be delayed.
             This problem should self-correct on the next periodic sync.
             [Replications Check,DC0] A recent replication attempt failed:
                From MDC120 to DC0
                Naming Context: CN=Configuration,DC=xx,DC=local
                The replication generated an error (1722):
                The RPC server is unavailable.
                The failure occurred at 2017-05-29 12:56:03.
                The last success occurred at 2016-11-04 04:26:33.
                5719 failures have occurred since the last success.
                The source MDC120 is responding now.
             [Replications Check,DC0] A recent replication attempt failed:
                From MDC120 to DC0
                Naming Context: DC=xx,DC=local
                The replication generated an error (1722):
                The RPC server is unavailable.
                The failure occurred at 2017-05-29 13:04:06.
                The last success occurred at 2016-11-04 04:51:35.
                190198 failures have occurred since the last success.
                The source MDC120 is responding now.
             ......................... DC0 failed test Replications
          Starting test: RidManager
             ......................... DC0 passed test RidManager
          Starting test: Services
             ......................... DC0 passed test Services
          Starting test: SystemLog
             A warning event occurred.  EventID: 0x80040020
                Time Generated: 05/29/2017   12:24:23
                Event String:
                The driver detected that the device \Device\Harddisk0\DR0 has its write cache enabled. Data corruption may
    ccur.
             A warning event occurred.  EventID: 0x80040020
                Time Generated: 05/29/2017   12:24:23
                Event String:
                The driver detected that the device \Device\Harddisk0\DR0 has its write cache enabled. Data corruption may
    ccur.
             A warning event occurred.  EventID: 0x80040020
                Time Generated: 05/29/2017   12:24:23
                Event String:
                The driver detected that the device \Device\Harddisk0\DR0 has its write cache enabled. Data corruption may
    ccur.
             A warning event occurred.  EventID: 0x00001796
                Time Generated: 05/29/2017   12:24:42
                Event String:
                Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and
    his server. This event occurs once per boot of the server on the first time a client uses NTLM with this server.
             ......................... DC0 passed test SystemLog
          Starting test: VerifyReferences
             ......................... DC0 passed test VerifyReferences


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

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

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



    Подскажите в какую сторону копать, полазил по форумам похожая проблемы вызывалась фаерволом или остатками старых DC, но это не мой случай, фаервол отключил для диагностики.



     



Все ответы