DcDiag error 67

Hi all,
i've runned Dcdiag /v /c /d /e /s on my child domain, because i can't access to the sysvol and netlogon, and the output is that i receive some errors included error 67.
I don't know what to do for solve this issue, can you help me?
From other domain i can access to sysvol and netlogon of my child domain.
In this gdrive link https://drive.google.com/file/d/0B2biJcjXGZkGY2xjXzZNNFROZms/view?usp=sharing you can see the output of my DcDiag.
This server is the only DC of the domain.
In the event viewer/system of my server (2012 R2) i've some warning with the NETLOGON event id 5802
Thank you in advance.

Hi,
 >Status is 53 The network path was not found.
For this question, you can try to check the DNS suffix to see if it helps.
dcdiag errors
https://social.technet.microsoft.com/Forums/windows/en-US/6bd96a6e-7161-49f3-994a-d178543305cc/dcdiag-errors?forum=winserverDS
>The registry lookup failed to determine the state of the SYSVOL. 
The error returned  was 0x43 "The network name cannot be found.". 
You can try to run net share command to check if sysvol and netlogon have successfully been shared.
It seems that there are some DNS issue, you can run dcdiag /test:DNS to see if there is any error meaasge.
Besides, How did you set your DNS configuration between child domain and parent domain?
Best Regards,
Erin

Similar Messages

  • Dcdiag error message

    Hi all,
    since a few days dcdiag
    gives me this error message:
    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.
    I think the error is here:
    Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller SRVDCENT02.solworld.com for FRS replica set configuration information.
    The nTDSConnection object cn=98e48971-a16e-4465-a636-e58abca82244,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com is conflicting with cn=254750de-d713-4b1f-b577-a3cb22cefcdb,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com.
    Using cn=98e48971-a16e-4465-a636-e58abca82244,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com
    The nTDSConnection object cn=98e48971-a16e-4465-a636-e58abca82244,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com is conflicting with cn=6c57954d-8e2c-4524-b17c-8b0859adc417,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com.
    Using cn=98e48971-a16e-4465-a636-e58abca82244,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com
    The nTDSConnection object cn=eedb61ba-027c-437a-9377-5f191f480c5f,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com is conflicting with cn=98e48971-a16e-4465-a636-e58abca82244,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com.
    Using cn=eedb61ba-027c-437a-9377-5f191f480c5f,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com
    The nTDSConnection object cn=eedb61ba-027c-437a-9377-5f191f480c5f,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com is conflicting with cn=88aa4eae-679e-48cb-89cd-dc8ba0fa5f59,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com.
    Using cn=eedb61ba-027c-437a-9377-5f191f480c5f,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com
    The nTDSConnection object cn=eedb61ba-027c-437a-9377-5f191f480c5f,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com is conflicting with cn=81d09cf0-be52-420d-bb8b-ebe3fe9cf55b,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com.
    Using cn=eedb61ba-027c-437a-9377-5f191f480c5f,cn=ntds settings,cn=dcsrv3,cn=servers,cn=be-solfeluy-francoforte,cn=sites,cn=configuration,dc=solworld,dc=com

    Hi,
    Look at this link: 
    http://support.microsoft.com/kb/312862/en-us
    Best regards Bourbita Thameur Microsoft Certified Technology Specialist: Windows Server 2008 R2,Server Virtualizaton

  • Dcdiag errors

    I recently imported the Active Directory management pack into SCOM and noticed lots of errors being flagged up in relation to our domain controllers. 
    We are running Server 2012 R2 domain controllers, about 4 writable ones with a whole host of read-only ones. 
    The following dcdiag report is from one of our read-only DCs:
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server = DomainController
       * Identified AD Forest. 
       Done gathering initial info.
    Doing initial required tests
       Testing server: TEPS-SOT\DomainController
          Starting test: Connectivity
             ......................... DomainController passed test Connectivity
    Doing primary tests
       Testing server: TEPS-SOT\DomainController
          Starting test: Advertising
             ......................... DomainController passed test Advertising
          Starting test: FrsEvent
             ......................... DomainController passed test FrsEvent
          Starting test: DFSREvent
             ......................... DomainController passed test DFSREvent
          Starting test: SysVolCheck
             ......................... DomainController passed test SysVolCheck
          Starting test: KccEvent
             An error event occurred.  EventID: 0xC000051F
                Time Generated: 04/13/2015   11:35:03
                Event String:
                The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition. 
             An error event occurred.  EventID: 0xC0000B58
                Time Generated: 04/13/2015   11:35:03
                Event String:
                This event documents additional REPAIR PROCEDURES to resolve the NTDS KCC Event 1311 on a read-only Active Directory Domain Controller. 
             A warning event occurred.  EventID: 0x80000749
                Time Generated: 04/13/2015   11:35:03
                Event String:
                The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site. 
             An error event occurred.  EventID: 0xC000051F
                Time Generated: 04/13/2015   11:35:03
                Event String:
                The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition. 
             An error event occurred.  EventID: 0xC0000B58
                Time Generated: 04/13/2015   11:35:03
                Event String:
                This event documents additional REPAIR PROCEDURES to resolve the NTDS KCC Event 1311 on a read-only Active Directory Domain Controller. 
             A warning event occurred.  EventID: 0x80000749
                Time Generated: 04/13/2015   11:35:03
                Event String:
                The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site. 
             An error event occurred.  EventID: 0xC000051F
                Time Generated: 04/13/2015   11:35:03
                Event String:
                The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition. 
             An error event occurred.  EventID: 0xC0000B58
                Time Generated: 04/13/2015   11:35:03
                Event String:
                This event documents additional REPAIR PROCEDURES to resolve the NTDS KCC Event 1311 on a read-only Active Directory Domain Controller. 
             A warning event occurred.  EventID: 0x80000749
                Time Generated: 04/13/2015   11:35:03
                Event String:
                The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site. 
             An error event occurred.  EventID: 0xC000051F
                Time Generated: 04/13/2015   11:35:03
                Event String:
                The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition. 
             An error event occurred.  EventID: 0xC0000B58
                Time Generated: 04/13/2015   11:35:03
                Event String:
                This event documents additional REPAIR PROCEDURES to resolve the NTDS KCC Event 1311 on a read-only Active Directory Domain Controller. 
             A warning event occurred.  EventID: 0x80000749
                Time Generated: 04/13/2015   11:35:03
                Event String:
                The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site. 
             ......................... DomainController failed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... DomainController passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... DomainController passed test MachineAccount
          Starting test: NCSecDesc
             ......................... DomainController passed test NCSecDesc
          Starting test: NetLogons
             ......................... DomainController passed test NetLogons
          Starting test: ObjectsReplicated
             ......................... DomainController passed test ObjectsReplicated
          Starting test: Replications
             ......................... DomainController passed test Replications
          Starting test: Services
             ......................... DomainController passed test Services
          Starting test: SystemLog
             An error event occurred.  EventID: 0x00000422
                Time Generated: 04/13/2015   11:04:25
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\localdomain.co.uk\SysVol\localdomain.co.uk\Policies\{8D59D86D-6BA2-44A0-B8D2-C6A0EBB2144F}\gpt.ini from a domain controller and was not successful.
    Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: 
             An error event occurred.  EventID: 0x0000165B
                Time Generated: 04/13/2015   11:08:39
                Event String:
                The session setup from computer 'FileAndPrint' failed because the security database does not contain a trust account 'FileAndPrint$' referenced by the specified computer.  
             An error event occurred.  EventID: 0x000016AD
                Time Generated: 04/13/2015   11:15:00
                Event String:
                The session setup from the computer FileAndPrint failed to authenticate. The following error occurred: 
             ......................... DomainController failed test SystemLog
          Starting test: VerifyReferences
             ......................... DomainController 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 : int
          Starting test: CheckSDRefDom
             ......................... int passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... int passed test CrossRefValidation
       Running enterprise tests on : localdomain.co.uk
          Starting test: LocatorCheck
             ......................... localdomain.co.uk passed test
             LocatorCheck
          Starting test: Intersite
             ......................... localdomain.co.uk passed test Intersite
    Any ideas as to what could be the cause? 
    www.techielass.com

    As already figured out, the errors you are getting are because of the WAN connectivity failures. Apart of checking the AD replication status using
    repadmin, it is already worth to check your DCs health status using
    dcdiag. Also, I would recommend that you refer to the IP settings I recommended here in case the issue persists: http://www.ahmedmalek.com/web/fr/articles.asp?artid=23
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • Dcdiag dns error

    I have a small test lab currently with 1 DC (srvr2012a).  I previously had 2 DCs but I have demoted srvr2012b and it no longer runs the DNS role. When I run dcdiag /test:dns /v /e, I get the following error:
    DCDiag error
    Should I be concerned with this?  Why is dcdiag seeing srvr2012b as a DNS server?

    It seems you have not completely demoted the DC. You may have to go through metadata clean up and clean your environment. Refer to the links below:
    Clean Up Server Metadata
    How to remove data in Active Directory after an unsuccessful domain controller demotion
    Metadata
    Cleanup – Unsuccessful Demotion of Domain Controller
    Mahdi Tehrani Loves Powershell
    Please kindly click on Propose As Answer
    or to mark this post as
    and helpful to other people.

  • Error with ADC on Azure dcdiag report failed test Advertising

    ever since I built an ADC on azure for my domain I am getting the below errors on dcdiag
    Starting test: Advertising
    Warning: DsGetDcName returned information for \\V2DC.V2.COM, when we
    were trying to reach V2-ADC02.
    SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
    ......................... V2-ADC02 failed test Advertising
    Unable to connect to the NETLOGON share! (\\V2-ADC02\netlogon)
    [V2-ADC02] An net use or LsaPolicy operation failed with error 67,
    The network name cannot be found..
    ......................... V2-ADC02 failed test NetLogons

    I just gave it some time and the error is gone looks like replication over the internet was slower than I thought

  • Dcdiag gives errors

    Hi I am running a win 2003 server which is the primary ad and DNS controller when running dcdiag I get the following:
    Domain Controller Diagnosis
    Performing initial setup:
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site\CW_SERVER
          Starting test: Connectivity
             The host 158c17ee-58bf-42c2-adea-9dfb9ab97e50._msdcs.cwmexico.local co
    ld not be resolved to an
             IP address.  Check the DNS server, DHCP, server name, etc
             Although the Guid DNS name
             (158c17ee-58bf-42c2-adea-9dfb9ab97e50._msdcs.cwmexico.local) couldn't
             be resolved, the server name (CW_SERVER) resolved to the IP address
             (192.168.1.119) and was pingable.  Check that the IP address is
             registered correctly with the DNS server.
             ......................... CW_SERVER failed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site\CW_SERVER
          Skipping all tests, because server CW_SERVER is
          not responding to directory service requests
       Running partition tests on : TAPI3Directory
          Starting test: CrossRefValidation
             ......................... TAPI3Directory passed test CrossRefValidatio
          Starting test: CheckSDRefDom
             ......................... TAPI3Directory passed test CheckSDRefDom
       Running partition tests on : ForestDnsZones
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidatio
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
       Running partition tests on : DomainDnsZones
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidatio
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
       Running partition tests on : Schema
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
       Running partition tests on : Configuration
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
       Running partition tests on : cwmexico
          Starting test: CrossRefValidation
             ......................... cwmexico passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... cwmexico passed test CheckSDRefDom
       Running enterprise tests on : cwmexico.local
          Starting test: Intersite
             ......................... cwmexico.local passed test Intersite
          Starting test: FsmoCheck
             ......................... cwmexico.local passed test FsmoCheck
    Can anyone help?
    Regards

    Hi Vivian I get the following after doing the netdiag /fix:
    C:\Documents and Settings\Administrador>netdiag /fix
        Computer Name: CW_SERVER
        DNS Host Name: CW_SERVER
        System info : Windows 2000 Server (Build 3790)
        Processor : x86 Family 6 Model 42 Stepping 7, GenuineIntel
        List of installed hotfixes :
            KB921503
            KB924667-v2
            KB925398_WMP64
            KB925876
            KB925902
            KB926122
            KB927891
            KB929123
            KB930178
            KB931784
            KB932168
            KB933360
            KB933729
            KB933854
            KB935839
            KB935840
            KB935966
            KB936021
            KB936357
            KB936782
            KB937143
            KB937143-IE7
            KB938127
            KB938127-IE7
            KB938464
            KB938759-v4
            KB939653-IE7
            KB941202
            KB941568
            KB941569
            KB941644
            KB941672
            KB941693
            KB942615-IE7
            KB942763
            KB943460
            KB943485
            KB943729
            KB944653
            KB945553
            KB947864-IE7
            KB948496
            KB948590
            KB948881
            KB949014
            KB950759-IE7
            KB950760
            KB950762
            KB950974
            KB951066
            KB951072-v2
            KB951698
            KB951746
            KB951748
            KB952954
            KB953838-IE7
            KB954211
            KB954550-v5
            KB955069
            KB956390-IE7
            KB956391
            KB956803
            KB956841
            KB957095
            KB957097
            KB958644
            Q147222
    Netcard queries test . . . . . . . : Passed
        GetStats failed for 'Paralelo directo'. [ERROR_NOT_SUPPORTED]
        GetStats failed for 'Minipuerto WAN (PPTP)'. [ERROR_NOT_SUPPORTED]
        GetStats failed for 'Minipuerto WAN (PPPOE)'. [ERROR_NOT_SUPPORTED]
        [WARNING] The net card 'Minipuerto WAN (IP)' may not be working because it h
    as not received any packets.
        GetStats failed for 'Minipuerto WAN (L2TP)'. [ERROR_NOT_SUPPORTED]
    Per interface results:
        Adapter : Conexi¾n de ßrea local 4
            Netcard queries test . . . : Passed
            Host Name. . . . . . . . . : CW_SERVER
            IP Address . . . . . . . . : 192.168.1.119
            Subnet Mask. . . . . . . . : 255.255.255.0
            Default Gateway. . . . . . : 192.168.1.254
            Dns Servers. . . . . . . . : 127.0.0.1
            AutoConfiguration results. . . . . . : Passed
            Default gateway test . . . : Passed
            NetBT name test. . . . . . : Passed
            [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
    r Service', <20> 'WINS' names is missing.
            WINS service test. . . . . : Skipped
                There are no WINS servers configured for this interface.
    Global results:
    Domain membership test . . . . . . : Passed
    NetBT transports test. . . . . . . : Passed
        List of NetBt transports currently configured:
            NetBT_Tcpip_{4670BBEF-9CCC-46FB-AF0B-A60F43A6A255}
        1 NetBt transport currently configured.
    Autonet address test . . . . . . . : Passed
    IP loopback ping test. . . . . . . : Passed
    Default gateway test . . . . . . . : Passed
    NetBT name test. . . . . . . . . . : Passed
        [WARNING] You don't have a single interface with the <00> 'WorkStation Servi
    ce', <03> 'Messenger Service', <20> 'WINS' names defined.
    Winsock test . . . . . . . . . . . : Passed
    DNS test . . . . . . . . . . . . . : Failed
        [WARNING] The DNS host name 'CW_SERVER' valid only on Windows 2000 DNS Serve
    rs. [DNS_ERROR_NON_RFC_NAME]
        [FATAL] Failed to fix: DC DNS entry cwmexico.local. re-registeration on DNS
    server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.cwmexico.local. re-registerat
    ion on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site._sites.cwm
    exico.local. re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.cwmexico.local. re
    -registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.cwmexico.local. re-
    registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site._sites.gc.
    _msdcs.cwmexico.local. re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.8856349a-cf14-424d-ac2f-f9fae
    29b3ea4.domains._msdcs.cwmexico.local. re-registeration on DNS server '127.0.0.1
    ' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry gc._msdcs.cwmexico.local. re-registerati
    on on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry 158c17ee-58bf-42c2-adea-9dfb9ab97e50._ms
    dcs.cwmexico.local. re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.cwmexico.local.
     re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site._sites
    .dc._msdcs.cwmexico.local. re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.cwmexico.local. re-
    registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site._sites.dc.
    _msdcs.cwmexico.local. re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.cwmexico.local. re-regist
    eration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site._sites
    .cwmexico.local. re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _gc._tcp.cwmexico.local. re-registeratio
    n on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _gc._tcp.Default-First-Site._sites.cwmex
    ico.local. re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _kerberos._udp.cwmexico.local. re-regist
    eration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _kpasswd._tcp.cwmexico.local. re-registe
    ration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _kpasswd._udp.cwmexico.local. re-registe
    ration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry DomainDnsZones.cwmexico.local. re-regist
    eration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.DomainDnsZones.cwmexico.local
    . re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site._sites.Dom
    ainDnsZones.cwmexico.local. re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry ForestDnsZones.cwmexico.local. re-regist
    eration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.ForestDnsZones.cwmexico.local
    . re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site._sites.For
    estDnsZones.cwmexico.local. re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry TAPI3Directory.cwmexico.local. re-regist
    eration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.TAPI3Directory.cwmexico.local
    . re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site._sites.TAP
    I3Directory.cwmexico.local. re-registeration on DNS server '127.0.0.1' failed.
    DNS Error code: 0x0000000D
        [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for th
    is DC on DNS server '127.0.0.1'.
        [FATAL] No DNS servers have the DNS records for this DC registered.
    Redir and Browser test . . . . . . : Passed
        List of NetBt transports currently bound to the Redir
            NetBT_Tcpip_{4670BBEF-9CCC-46FB-AF0B-A60F43A6A255}
        The redir is bound to 1 NetBt transport.
        List of NetBt transports currently bound to the browser
            NetBT_Tcpip_{4670BBEF-9CCC-46FB-AF0B-A60F43A6A255}
        The browser is bound to 1 NetBt transport.
    DC discovery test. . . . . . . . . : Passed
    DC list test . . . . . . . . . . . : Failed
            Failed to enumerate DCs by using the browser. [ERROR_NO_BROWSER_SERVERS_
    FOUND]
    Trust relationship test. . . . . . : Skipped
    Kerberos test. . . . . . . . . . . : Failed
            [FATAL] Kerberos does not have a ticket for host/CW_SERVER.
    LDAP test. . . . . . . . . . . . . : Failed
        [WARNING] The default SPN registration for 'HOST/CW_SERVER' is missing on DC
     'CW_SERVER'.
        [FATAL] The default SPNs are not properly registered on any DCs.
    Bindings test. . . . . . . . . . . : Passed
    WAN configuration test . . . . . . : Skipped
        No active remote access connections.
    Modem diagnostics test . . . . . . : Passed
    IP Security test . . . . . . . . . : Skipped
        Note: run "netsh ipsec dynamic show /?" for more detailed information
    The command completed successfully
    C:\Documents and Settings\Administrador>

  • Dcdiag fatal error

    I am having problems with my DFS shares not showing up, and in researching this I ran a dcdiag on my domain controllers and am getting the following error:
    Performing initial setup:
       Trying to find home server...
       Home Server = servername
       * Identified AD Forest.
       FATAL ERROR: ldap_search for parttion attributes with base DN = CN=Partitions
    ,CN=Configuration,DC=domain,DC=local failed with error = 32
    I have never seen so few results when searching for this error. I have no idea where to begin.

    So that was a nightmare... I had to move DHCP, FSMO, CA Authority... took several hours. BUT I eventually got it demoted and re-promoted. Same issue. HOWEVER, I ran as administrator and it worked. It has been a very long day. I guess I didn't realize I was
    doing that on the other DCs when I ran on them.
    SO. Now when I run dcdiag, I get some other errors:
    REPLICATION LATENCY WARNING ERROR: Expected notification link is missing.Source DC2 -this is the new PDC fyi Replication of new changes along this path
    will be delayed. This problem should self-correct on the next periodic sync.
    I ran repadmin /showrepl on all 4 DCs and everything was successful.
    I have no idea what is happening. Maybe the issue I am having is not a DC issue. Here is what happened to me:
    Some machines could not access "\\domain.local\share", while others could. On the other hand, they ALL could access "\\domain\share". I fixed that by changing all my drive mappings to \\domain\share (took off the .local) Don't know why
    that was an issue, I was going to get to that later.
    This morning I discovered that there were two more issues happening. The DFS share was showing up empty on many computers (they could access "\\domain\share" but there was nothing in it, while other machines saw the folders they should see. Trying
    to get everybody working while I fixed THAT issue, I changed the drive mappings again to point directly to the servers they needed (without DFS).
    That worked for some, but not others. The ones it did not work on had Group Policy errors in the event log saying they could not find a group policy server or something (hours ago, who can remember exact errors at this point), so they were still pointing
    to the DFS shares. Several reboots would usually eventually get things resolved.
    So here I am, can't figure out if it is a DFS issue, DC Replication issue, DNS issue, WINS issue or what. I am just burnt and I am going home for the day.
    Thank you so much for your help so far, I can tell you have been spending a lot of time on this. Maybe I need to start a new thread?

  • DCDIAG Result A net user or LsaPolicy failed with error 67

    I have looked through all the similar posts and have ran an Authoritative and UnAthroativte process. This allowed my SYSVOL to replicate and come back. I still keep getting this error on the one DC. Everything else passes fine. I am pulling my hair out
    if anyone has had this problem please help. Also this is a Server 2012 R2 DC 

    Hi Mike,
    Before going further, how did you do the Sysvol restore? What’s our Sysvol replication mechanism, FRS or DFSR?
    If our Sysvol replication mechanism is FRS, we need to do an authoritative (D4) restore on a healthy DC and non-authoritative (D2) restore on other DCs.
    Regarding this point, the following thread and article can be referred to for more information.
    [DC2] An net use or LsaPolicy operation failed with error 67 - Moving AD from 2003R2 to Server 2012
    http://social.technet.microsoft.com/Forums/en-US/401f7023-9ef1-4dc7-94f4-f59a74b49d65/dc2-an-net-use-or-lsapolicy-operation-failed-with-error-67-moving-ad-from-2003r2-to-server-2012?forum=winserverDS
    Using the BurFlags registry key to reinitialize File Replication Service replica sets
    http://support.microsoft.com/kb/290762/en-us
    If our Sysvol replication mechanism is DFSR, we can follow the article below to do the Sysvol restore.
    How to force an authoritative and non-authoritative synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS)
    http://support.microsoft.com/kb/2218556/en-us
    Best regards,
    Frank Shen

  • DNS Server Errors 4015 and 4010

    Hi all,
    we have upgraded a 2003 Domain to 2012 R2. All DCs now are 2012 R2. The Domain and Forest Level are 2008. Be checking the Eventlogs of the DNS Server we found that we have DNS Error 4010 and 4015 Events repeatedly.
    4015:
    The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.
    4010:
    The DNS server was unable to create a resource record for f55ab78a-df8d-4c2c-8420-52dc8b5604e2._msdcs.domain.local. in zone Domain.local. The Active Directory definition of this resource record is corrupt or contains an invalid DNS name. The event data contains
    the error.
    We found that the Errors are available on oll DCs. The errors occurs only after the DNS Server Service are restartet on the DCs.
    We check the dcdiag /e /test:dns with all PASS
    We check the netlogon Service are successfully update be a restart the _.msdcs records in the Zone if the record are not present
    We check the _msdcs.Domain.local Zone, it is in the forest Root Partition and AD integrated. We move it to the root of the DNS like the KB817470 describe
    We check the dns by the Best Practices Analyzer, wihtout a error
    We check the AD replication by repadmin without error
    Thanks for help
    Regards Steven

    Hi,
    Can you tell more information about the migration?
    The roles that installed on windows server 2003 before migration. Is DNS role installed on it?
    You can refer to this similar thread:
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/55c7a4cd-2932-4b0e-bfd2-b043490df000/eventid-4010-dns-the-active-directory-definition-of-this-resource-record-is-corrupt-or-contains-an?forum=winserverDS

  • Replication error on windows 2012 DC

    Hi,
    I have added Windows 2012 R2 server (cadpdc1) to windows 2003 sp2 DC  (Primary DC) and promoted it as DC. After the promote I have ran dcdiag and it shows errors.
    Each of servers have three NICs connected to different networks.
    Please help me with your expertise since I need to bring this up on monday.
    Thank you
    Kind regards
    Chamara
    here the dcdiag output of new DC
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server = CADPDC1
       * Identified AD Forest.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\CADPDC1
          Starting test: Connectivity
             Error during resolution of hostname CADPDC1.engineer.com through
             IPv6 stack.
             *** Warning: could not confirm the identity of this server in the
             directory versus the names returned by DNS servers. Hostname
             resolution error 0x2af9 "No such host is known."
             ......................... CADPDC1 passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\CADPDC1
          Starting test: Advertising
             Warning: DsGetDcName returned information for
             \\cadpdc.engineer.com, when we were trying to reach CADPDC1.
             SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
             ......................... CADPDC1 failed 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.
             ......................... CADPDC1 passed test FrsEvent
          Starting test: DFSREvent
             ......................... CADPDC1 passed test DFSREvent
          Starting test: SysVolCheck
             ......................... CADPDC1 passed test SysVolCheck
          Starting test: KccEvent
             ......................... CADPDC1 passed test KccEvent
          Starting test: KnowsOfRoleHolders
             [CADPDC] DsBindWithSpnEx() failed with error -2146893022,
             The target principal name is incorrect..
             Warning: CADPDC is the Schema Owner, but is not responding to DS RPC
             Bind.
             [CADPDC] LDAP bind failed with error 8341,
             A directory service error has occurred..
             Warning: CADPDC is the Schema Owner, but is not responding to LDAP
             Bind.
             Warning: CADPDC is the Domain Owner, but is not responding to DS RPC
             Bind.
             Warning: CADPDC is the Domain Owner, but is not responding to LDAP
             Bind.
             Warning: CADPDC is the PDC Owner, but is not responding to DS RPC
             Bind.
             Warning: CADPDC is the PDC Owner, but is not responding to LDAP Bind.
             Warning: CADPDC is the Rid Owner, but is not responding to DS RPC
             Bind.
             Warning: CADPDC is the Rid Owner, but is not responding to LDAP Bind.
             Warning: CADPDC is the Infrastructure Update Owner, but is not
             responding to DS RPC Bind.
             Warning: CADPDC is the Infrastructure Update Owner, but is not
             responding to LDAP Bind.
             ......................... CADPDC1 failed test KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... CADPDC1 passed test MachineAccount
          Starting test: NCSecDesc
             ......................... CADPDC1 passed test NCSecDesc
          Starting test: NetLogons
             Unable to connect to the NETLOGON share! (\\CADPDC1\netlogon)
             [CADPDC1] An net use or LsaPolicy operation failed with error 67,
             The network name cannot be found..
             ......................... CADPDC1 failed test NetLogons
          Starting test: ObjectsReplicated
             ......................... CADPDC1 passed test ObjectsReplicated
          Starting test: Replications
             [Replications Check,CADPDC1] A recent replication attempt failed:
                From CADPDC to CADPDC1
                Naming Context: DC=ForestDnsZones,DC=engineer,DC=com
                The replication generated an error (-2146893022):
                The target principal name is incorrect.
                The failure occurred at 2014-06-27 17:05:59.
                The last success occurred at 2014-06-27 17:01:21.
                1 failures have occurred since the last success.
             [Replications Check,CADPDC1] A recent replication attempt failed:
                From CADPDC to CADPDC1
                Naming Context: DC=DomainDnsZones,DC=engineer,DC=com
                The replication generated an error (-2146893022):
                The target principal name is incorrect.
                The failure occurred at 2014-06-27 17:05:59.
                The last success occurred at 2014-06-27 17:01:21.
                1 failures have occurred since the last success.
             [Replications Check,CADPDC1] A recent replication attempt failed:
                From CADPDC to CADPDC1
                Naming Context: CN=Schema,CN=Configuration,DC=engineer,DC=com
                The replication generated an error (1727):
                The remote procedure call failed and did not execute.
                The failure occurred at 2014-06-27 17:05:59.
                The last success occurred at 2014-06-27 17:01:06.
                1 failures have occurred since the last success.
             [Replications Check,CADPDC1] A recent replication attempt failed:
                From CADPDC to CADPDC1
                Naming Context: CN=Configuration,DC=engineer,DC=com
                The replication generated an error (-2146893022):
                The target principal name is incorrect.
                The failure occurred at 2014-06-27 17:05:59.
                The last success occurred at 2014-06-27 17:01:07.
                1 failures have occurred since the last success.
             [Replications Check,CADPDC1] A recent replication attempt failed:
                From CADPDC to CADPDC1
                Naming Context: DC=engineer,DC=com
                The replication generated an error (-2146893022):
                The target principal name is incorrect.
                The failure occurred at 2014-06-27 17:05:59.
                The last success occurred at 2014-06-27 17:01:21.
                1 failures have occurred since the last success.
             ......................... CADPDC1 failed test Replications
          Starting test: RidManager
             ......................... CADPDC1 failed test RidManager
          Starting test: Services
             ......................... CADPDC1 passed test Services
          Starting test: SystemLog
             A warning event occurred.  EventID: 0x000727A5
                Time Generated: 06/27/2014   17:01:38
                Event String:
                The WinRM service is not listening for WS-Management requests.
             A warning event occurred.  EventID: 0x80050004
                Time Generated: 06/27/2014   17:05:03
                Event String:
                HP Ethernet 1Gb 2-port 332T Adapter: The network link is down.  Check to make sure the network cable is properly connected.
             A warning event occurred.  EventID: 0xA004001B
                Time Generated: 06/27/2014   17:05:06
                Event String: HP NC112T PCIe Gigabit Server Adapter
             An error event occurred.  EventID: 0x40000004
                Time Generated: 06/27/2014   17:05:39
                Event String:
                The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server cadpdc1$. The target name used was LDAP/cadpdc.engineer.com/[email protected]. This indicates that the target
    server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target 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 password. If the server name is not fully qualified, and the target domain (ENGINEER.COM) is different from the client domain (ENGINEER.COM), 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: 0x40000004
                Time Generated: 06/27/2014   17:05:39
                Event String:
                The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server cadpdc1$. The target name used was ldap/cadpdc.engineer.com/[email protected]. This indicates that the target
    server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target 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 password. If the server name is not fully qualified, and the target domain (ENGINEER.COM) is different from the client domain (ENGINEER.COM), 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: 0x40000004
                Time Generated: 06/27/2014   17:05:41
                Event String:
                The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server cadpdc1$. The target name used was cadpdc$. This indicates that the target server failed to decrypt the ticket provided
    by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target 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 password. If the server name
    is not fully qualified, and the target domain (ENGINEER.COM) is different from the client domain (ENGINEER.COM), 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: 0x40000004
                Time Generated: 06/27/2014   17:05:43
                Event String:
                The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server cadpdc1$. The target name used was GC/cadpdc.engineer.com/engineer.com. This indicates that the target server failed
    to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target 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 password. If the server name is not fully qualified, and the target domain (ENGINEER.COM) is different from the client domain (ENGINEER.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to
    identify the server.
             A warning event occurred.  EventID: 0x000727AA
                Time Generated: 06/27/2014   17:05:43
                Event String:
                The WinRM service failed to create the following SPNs: WSMAN/CADPDC1.engineer.com; WSMAN/CADPDC1.
             An error event occurred.  EventID: 0x40000004
                Time Generated: 06/27/2014   17:05:55
                Event String:
                The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server cadpdc1$. The target name used was cifs/cadpdc.engineer.com. This indicates that the target server failed to decrypt
    the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target 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 password.
    If the server name is not fully qualified, and the target domain (ENGINEER.COM) is different from the client domain (ENGINEER.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
             A warning event occurred.  EventID: 0x84350444
                Time Generated: 06/27/2014   17:05:58
                Event String:
                System Information Agent: Health: Post Errors were detected.  One or more Power-On-Self-Test errors were detected during server startup.
             An error event occurred.  EventID: 0x40000004
                Time Generated: 06/27/2014   17:05:59
                Event String:
                The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server cadpdc1$. The target name used was E3514235-4B06-11D1-AB04-00C04FC2DCD2/5122bd13-c8ac-4265-a879-3a6831224994/[email protected].
    This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target 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 password. If the server name is not fully qualified, and the target domain (ENGINEER.COM) is different from the client domain (ENGINEER.COM), 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: 0x40000004
                Time Generated: 06/27/2014   17:05:59
                Event String:
                The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server cadpdc1$. The target name used was ldap/cadpdc.engineer.com. This indicates that the target server failed to decrypt
    the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target 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 password.
    If the server name is not fully qualified, and the target domain (ENGINEER.COM) is different from the client domain (ENGINEER.COM), 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: 0x0000410B
                Time Generated: 06/27/2014   17:05:59
                Event String:
                The request for a new account-identifier pool failed. The operation will be retried until the request succeeds. The error is
             An error event occurred.  EventID: 0x40000004
                Time Generated: 06/27/2014   17:06:07
                Event String:
                The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server cadpdc1$. The target name used was LDAP/cadpdc.engineer.com. This indicates that the target server failed to decrypt
    the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target 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 password.
    If the server name is not fully qualified, and the target domain (ENGINEER.COM) is different from the client domain (ENGINEER.COM), 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: 0x0000041F
                Time Generated: 06/27/2014   17:06:30
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following:
             An error event occurred.  EventID: 0x0000041D
                Time Generated: 06/27/2014   17:07:07
                Event String:
                The processing of Group Policy failed. Windows could not resolve the user name. This could be caused by one of more of the following:
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 06/27/2014   17:11:32
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following:
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 06/27/2014   17:16:33
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following:
             An error event occurred.  EventID: 0x40000004
                Time Generated: 06/27/2014   17:16:38
                Event String:
                The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server cadpdc1$. The target name used was LDAP/5122bd13-c8ac-4265-a879-3a6831224994._msdcs.engineer.com. This indicates that
    the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target 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 password. If the server name is not fully qualified, and the target domain (ENGINEER.COM) is different from the client domain (ENGINEER.COM), 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: 0x0000041F
                Time Generated: 06/27/2014   17:21:35
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following:
             ......................... CADPDC1 failed test SystemLog
          Starting test: VerifyReferences
             ......................... CADPDC1 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 : engineer
          Starting test: CheckSDRefDom
             ......................... engineer passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... engineer passed test CrossRefValidation
       Running enterprise tests on : engineer.com
          Starting test: LocatorCheck
             ......................... engineer.com passed test LocatorCheck
          Starting test: Intersite
             ......................... engineer.com passed test Intersite

    Hi,
    Please check the following : 
    - Confgigure IPv6 in DNS Management
    - Kerberos and LDAP records of dns.
    - Zone transfer from old server to new server.
    Thanks.
    Alper YAZGAN *

  • TableAdapter Configuration Wizard gives error when adding new TableAdapter

    Hi,
    I recently downloaded and installed the ODT for visual studio on my computer. I am running VS2008 on Windows 7 64-bit. I am able to create an ODP.NET connection to the Oracle XE 10.2g instance that is running on my computer with no problems and use that connection to browse the database. When I add a DataSet to my project, and start adding TableAdapters to the DataSet, I am getting errors. In an attempt to figure out what the problem is, I have followed various scenarios. I will describe each scenario, and what the end result is, and then after I have described them all, I will explain what I think the problem might be. Here are the different scenarios I have used:
    Scenario 1:
    From the Server Explorer, highlight ALL of the tables in my schema and drag them to the designer (all table adapters are added with no issues). I can add additional queries to each of the TableAdapters and then change the additional queries by right clicking and choosing "Configure". This all works with no issues. However, on certain TableAdapters, if I try to modify the primary query (Fill,GetData()), I can open the query editor just fine, change various settings, etc, but when I click on "Finish" I get the following error:
    Configure TableAdapter TABLENAME failed.
    Index was outside the bounds of the array.
    Scenario 2:
    From the Server Explorer, drag tables from my schema onto the designer one at a time. Some tables get added just fine, but for the rest of them, I get the following error:
    Failed to merge object(s).
    Index was outside the bounds of the array.
    Scenario 3:
    On the Dataset Designer, add tables one at a time by right clicking and choosing "Add -> TableAdapter" and then using SQL to define the query for each table. Some tables get added just fine, but for the rest of them, I get the following error:
    Failed to add TableAdapter.
    Index was outside the bounds of the array.
    Ok... now that I have described all of the different scenarios, I will explain what I think the problem is, and why. Based on my research, I believe the underlying problem has to do with Foreign Key Constraints on the various tables. While working on Scenarios 2 & 3, the same exact tables worked just fine in both scenarios. When I started looking at the definitions for the tables in my schema, it turns out that all of the tables that failed had foreign key constraints defined. When I remove the FK constraints from a table, I am then able to add it to my dataset and change the default query with no problems. My original application used the System.Data.OracleClient provided by Microsoft. When adding my tableadapters using the microsoft data provider, the FK relations are automatically generated for me in the designer, but not with the Oracle Data Provider
    I would be happy to provide you with the DDL that I used for creating my schema (it is not very big) if needed.
    Thanks,
    Jim

    Sorry let me clarify some of the config a little more.
    MAIL101 - Exch 2013
    MAIL102 - Exch 2013
    AP104 - Witness (strictly a witness nothing else on this machine)
    EDGE01 - Exch 2007 Edge
    CAS01 - Exch 2007 Hub/CAS load balancer for CAS02/03
    CAS02 - Exch 2007 Hub/CAS
    CAS03 - Exch 2007 Hub/CAS
    MBOX01 - Exch 2007 Mail cluster
    MBOX02 - Exch 2007 Mail cluster node
    MBOX03 - Exch 2007 Mail cluster node
    RDC01, RDC02, RDC03 - all 2008 R2 root domain controllers for rootdomain.rootdomain
    DC01, DC02, DC03, DC04 - all 2008 R2 domain controllers for us.rootdomain.rootdomain
    All DCs are Global Catalogs.
    I can ping all DCs and root DCs fromboth MAIL101 and 102
    The Exchange Replication service is running on both MAIL101 and 102.
    DC03 is in the same site as the MAIL101/102 servers so I'll run all replication tests from here.
    DCDIAG comes back with all tests passed.
    repadmin /replsum comes back with 0 fails and no errors largest delta for any intersite communication is 13min.
    When I run Test-ReplicationHealth -Identity MAIL101 and also 102 they both come back as everything passed.  No errors.

  • While running dcdiag /test:dns getting Warning: The AAAA record for this DC was not found

    DCDIAG /test:dns result is pested here.
    C:\Users\administrator.SUD>dcdiag /test:dns
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server = MUM-ADS-01
       * Identified AD Forest.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\MUM-ADS-01
          Starting test: Connectivity
             ......................... MUM-ADS-01 passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\MUM-ADS-01
          Starting test: DNS
             DNS Tests are running and not hung. Please wait a few minutes...
             ......................... MUM-ADS-01 passed test DNS
       Running partition tests on : ForestDnsZones
       Running partition tests on : DomainDnsZones
       Running partition tests on : Schema
       Running partition tests on : Configuration
       Running partition tests on : sud
       Running enterprise tests on : sud.in
          Starting test: DNS
             Test results for domain controllers:
                DC: MUM-ADS-01.sud.in
                Domain: sud.in
                   TEST: Basic (Basc)
                      Warning: The AAAA record for this DC was not found
                   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. (128.9.0.107)
                      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. (198.32.64.12)
                      Error: Root hints list has invalid root hint server:
                      m.root-servers.net. (202.12.27.33)
                   TEST: Delegations (Del)
                      Error: DNS server: sud-ad.sud.in. IP:<Unavailable>
                      [Missing glue A record]
                   TEST: Records registration (RReg)
                      Network Adapter
                      [00000006] Intel(R) PRO/1000 MT Network Connection:
                         Warning:
                         Missing AAAA record at DNS server 10.1.6.132:
                         MUM-ADS-01.sud.in
                         Warning:
                         Missing AAAA record at DNS server 10.1.6.132:
                         gc._msdcs.sud.in
                         Warning:
                         Missing AAAA record at DNS server 10.1.6.133:
                         MUM-ADS-01.sud.in
                         Warning:
                         Missing AAAA record at DNS server 10.1.6.133:
                         gc._msdcs.sud.in
                   Warning: Record Registrations not found in some network adapters
             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
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
    S server 128.63.2.53
                DNS server: 128.8.10.90 (d.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
    S server 128.8.10.90
                DNS server: 128.9.0.107 (b.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
    S server 128.9.0.107
                DNS server: 192.112.36.4 (g.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
    S server 192.112.36.4
                DNS server: 192.203.230.10 (e.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
    S server 192.203.230.10
                DNS server: 192.33.4.12 (c.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
    S server 192.33.4.12
                DNS server: 192.36.148.17 (i.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
    S server 192.36.148.17
                DNS server: 192.5.5.241 (f.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
    S server 192.5.5.241
                DNS server: 192.58.128.30 (j.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
    S server 192.58.128.30
                DNS server: 193.0.14.129 (k.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
    S server 193.0.14.129
                DNS server: 198.32.64.12 (l.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
    S server 198.32.64.12
                DNS server: 198.41.0.4 (a.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
    S server 198.41.0.4
                DNS server: 202.12.27.33 (m.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
    S server 202.12.27.33
             Summary of DNS test results:
    Auth Basc Forw Del  Dyn  RReg Ext
                Domain: sud.in
                   MUM-ADS-01                   PASS WARN FAIL FAIL PASS WARN n/a
             ......................... sud.in failed test DNS

    Hi Meinolf,
    Please find the IP Details as well as DNS test results.
    C:\Users\Administrator.SCI>dcdiag /test:dns
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server = MDCDCDNS
       * Identified AD Forest.
       Done gathering initial info.
    Doing initial required tests
       Testing server: MDC-Powai\MDCDCDNS
          Starting test: Connectivity
             ......................... MDCDCDNS passed test Connectivity
    Doing primary tests
       Testing server: MDC-Powai\MDCDCDNS
          Starting test: DNS
             DNS Tests are running and not hung. Please wait a few minutes...
     ERROR: NO DNS servers for IPV6 stack was found
             ......................... MDCDCDNS passed test DNS
       Running partition tests on : ForestDnsZones
       Running partition tests on : DomainDnsZones
       Running partition tests on : Schema
       Running partition tests on : Configuration
       Running partition tests on : sci
       Running enterprise tests on : sci.com
          Starting test: DNS
             Test results for domain controllers:
                DC: MDCDCDNS.sci.com
                Domain: sci.com
                   TEST: Basic (Basc)
                      Warning: The AAAA record for this DC was not found
                   TEST: Records registration (RReg)
                      Network Adapter
                      [00000009] Microsoft Virtual Network Switch Adapter:
                         Warning:
                         Missing AAAA record at DNS server 10.64.7.32:
                         MDCDCDNS.sci.com
                         Warning:
                         Missing AAAA record at DNS server 10.64.7.32:
                         gc._msdcs.sci.com
                         Warning:
                         Missing AAAA record at DNS server 10.64.7.35:
                         MDCDCDNS.sci.com
                         Warning:
                         Missing AAAA record at DNS server 10.64.7.35:
                         gc._msdcs.sci.com
                         Warning:
                         Missing AAAA record at DNS server 10.20.33.72:
                         MDCDCDNS.sci.com
                         Warning:
                         Missing AAAA record at DNS server 10.20.33.72:
                         gc._msdcs.sci.com
                         Warning:
                         Missing AAAA record at DNS server 10.20.33.71:
                         MDCDCDNS.sci.com
                         Warning:
                         Missing AAAA record at DNS server 10.20.33.71:
                         gc._msdcs.sci.com
                   Warning: Record Registrations not found in some network adapters
                   MDCDCDNS                     PASS WARN PASS PASS PASS WARN n/a
             ......................... sci.com passed test DNS
    C:\Users\Administrator.SCI>ipconfig /all
    Windows IP Configuration
       Host Name . . . . . . . . . . . . : MDCDCDNS
       Primary Dns Suffix  . . . . . . . : sci.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : sci.com
    Ethernet adapter Local Area Connection 7:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : External Internal Virtual Network
       Physical Address. . . . . . . . . : 00-14-4F-CA-83-AC
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.64.7.32(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.64.7.1
       DNS Servers . . . . . . . . . . . : 10.64.7.32
                                           10.64.7.35
                                           10.20.33.72
                                           10.20.33.71
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter Local Area Connection 6:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : TEAM : Team #1
       Physical Address. . . . . . . . . : 00-14-4F-CA-83-AC
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Autoconfiguration IPv4 Address. . : 169.254.105.163(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Tunnel adapter Local Area Connection* 8:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{2D5A4A27-298F-48E5-A376-EA886EF1E
    42A}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter Local Area Connection* 9:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{14FA7CD4-8B69-4C86-A58B-056793B7D
    901}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    Please check and revert back for any queries..
    Thanks...
    Deva Self-trust is the first secret of success.

  • WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found.

    I have two forests with a transitive on-way trust between them: PROD -> TEST (test trusts PROD). I had previously had kerberos authentication working with winrm from PROD to machines in TEST. I have verified the trust is healthy, I also verified users
    in TEST can use WINRM with kerberos just fine. Users from PROD cannot connect via kerberos to machines in TEST with winrm.
    I have verified the service has registered the appropriate SPNs. I ran dcdiag against all my PROD and TEST domain controllers and didn't find anything that would prevent kerberos from happening. I even tried disabling the firewall entirely on my TEST dcs
    but that didn't gain me anything.
    I've enabled kerberos logging but only see the expected errors such as it couldn't find a PROD SPN for the machine, which it shouldn't from what I understand, it should go to the TEST domain and find the SPN from there.
    I'm really out of next steps before I call PSS and hope someone here has run into this and could provide me some next steps.
    PowerShell Error:
    Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found.  
     Possible causes are:
      -The user name or password specified are invalid.
      -Kerberos is used when no authentication method and no user name are specified.
      -Kerberos accepts domain user names, but not local user names.
      -The Service Principal Name (SPN) for the remote computer name and port does not exist.
      -The client and remote computers are in different domains and there is no trust between the two domains.
     After checking for the above issues, try the following:
      -Check the Event Viewer for events related to authentication.
      -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport.
     Note that computers in the TrustedHosts list might not be authenticated.
       -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.
        + CategoryInfo          : OpenError: (:) [], PSRemotingTransportException
        + FullyQualifiedErrorId : PSSessionStateBroken
    winrs Error:
    Winrs error:
    WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found.  
     Possible causes are:
      -The user name or password specified are invalid.
      -Kerberos is used when no authentication method and no user name are specified.
      -Kerberos accepts domain user names, but not local user names.
      -The Service Principal Name (SPN) for the remote computer name and port does not exist.
      -The client and remote computers are in different domains and there is no trust between the two domains.
     After checking for the above issues, try the following:
      -Check the Event Viewer for events related to authentication.
      -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport.
     Note that computers in the TrustedHosts list might not be authenticated.
       -For more information about WinRM configuration, run the following command: winrm help config.

    Hi Adam,
    I'm a little unclear about which SPNs you were looking for, in which case could you confirm you were checking that on the computer object belonging to the actual destination host it has the following SPNs registered?
    WSMAN/<NetBIOS name>
    WSMAN/<FQDN>
    If you were actually trying to use WinRM to connect to the remote forest's domain controllers, then what you said makes sense, but I was caught between assuming this was the case or you meant another member server in that remote forest.
    Also, from the client trying to connect to this remote server, are you able to telnet to port 5985? (If you've used something other than the default, try that port)
    If you can't, then you've got something else like a firewall (be that the Windows firewall on the destination or a hardware firewall somewhere in between) blocking you at the port level, or the listener on the remote box just isn't working as expected. I
    just replied to your other winrm post with steps for checking the latter, so I won't repeat myself here.
    If you can telnet to it and the SPNs exist, then you might be up against something called selective authentication which has to do with how the trust was defined. You can have a read of
    this to learn a bit more about selective trusts and whether or not it's affecting you.
    Cheers,
    Lain

  • Exchange 2013 SP1 prerequ errors

    Current installation. 4 Exchange 2013 machines on Server 2008 R2 platform (VM with Hyper-V), all have CAS and mailbox role installed. DAG across all for servers. 2 servers
    reside in main datacenter and 2 on a DR site.
    The Exchange installation is at CU 2 and working.<o:p></o:p>
    We have 2 domain controllers in the main datacenter (win 2008 R2) and 2 domain controllers in the DR site (Win 2012 R2).<o:p></o:p>
    DCDIAG checks out fine on all. Network is fine for all.
    Running SP1 installation on the Exchange servers in the DR site results in prerequisites in a bunch of errors which all stem from one root issue: <o:p></o:p>
    Error:
    Either Active Directory doesn't exist, or it can't be contacted.<o:p></o:p>
    Running the same on the main site (DC= Win 2008 R2) completes prereq for SP1 with no errors.
    So the difference is that the 2 Exchange servers on the DR site have Win 2012 R2 for their domain controllers and fail.<o:p></o:p>
    Any advise?<o:p></o:p>
    Gerhard Waterkamp ACSLA Inc.

    No, I am not done.
    The situation is that on the DR site SP1 on 2 Exchange 2013 servers (on 2008 R2) using Windows 2012 R2 Domain controllers does not install.
    Error messages: ( a whole bunch more, but all related to this)
    Error:
    Either Active Directory doesn't exist, or it can't be contacted.
    It is not resolved but still open.
    Gerhard Waterkamp ACSLA Inc.

  • Windows 8.1 Pro has error while joining domain, while windows 7 pro has no problem to join in the same network

    I am having the same issue as posted in http://social.technet.microsoft.com/Forums/windows/en-US/6ea57e5f-6e9d-49bd-9dd7-832ea84c0276/windows-81-pro-will-not-join-domain?forum=w8itpronetworking
    There are a few other people have the same issues.  However there was no real solution provided although the post was marked as answered.  I am posting it here again and hopefully I can get some help to solve this issue.
    We got two new PCs, one with windows 7 and the other with windows 8.1 Pro.  In the same network with domain, the windows 7 pc has no problem at all to join the domain.  However the windows 8.1 Pro won't join the domain. On the windows 8.1 Pro computer,
    I can ping the other computers in the network.  The error message says:
    An Active Directory Domain Controller (AD DC) for the domain "cmi" could not be contacted. ...
    In my case, the domain name is "CMI".  I am sure the DNS setting is correct.  What did I do wrong?  Any help is greatly appreciated.  Thanks.

    I tried the solution in that article.
    In HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters folder, there is no
    NeutralizeNT4Emulator.  So I followed the instructions and created one, and set the value to 1. Then I restarted the computer and tried to join the domain again.  I got the same error.  Below is more from the netsetup log file:
    06/04/2014 21:36:37:256 -----------------------------------------------------------------
    06/04/2014 21:36:37:256 NetpValidateName: checking to see if 'XPS8700' is valid as type 1 name
    06/04/2014 21:36:40:256 NetpCheckNetBiosNameNotInUse for 'XPS8700' [MACHINE] returned 0x0
    06/04/2014 21:36:40:256 NetpValidateName: name 'XPS8700' is valid for type 1
    06/04/2014 21:36:40:256 -----------------------------------------------------------------
    06/04/2014 21:36:40:256 NetpValidateName: checking to see if 'XPS8700' is valid as type 5 name
    06/04/2014 21:36:40:256 NetpValidateName: name 'XPS8700' is valid for type 5
    06/04/2014 21:36:40:256 -----------------------------------------------------------------
    06/04/2014 21:36:40:256 NetpValidateName: checking to see if 'cmi' is valid as type 3 name
    06/04/2014 21:36:40:272 NetpCheckDomainNameIsValid for cmi returned 0x54b, last error is 0x0
    06/04/2014 21:36:40:272 NetpCheckDomainNameIsValid [ Exists ] for 'cmi' returned 0x54b
    ----------------below is the error message from the pop up window
    Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.
    The domain name "cmi" might be a NetBIOS domain name.  If this is the case, verify that the domain name is properly registered with WINS.
    If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
    DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain "cmi":
    The query was for the SRV record for _ldap._tcp.dc._msdcs.cmi
    The following domain controllers were identified by the query:
    cmi-dc2.cmi
    cmi-dc1.cmi
    However no domain controllers could be contacted.
    Thanks.

Maybe you are looking for