DCDIAG

Hello -
I ran a simple DCDIAG with no switches and the errors below came back, I'm not sure how to fix these errors. Please help, I'd sure appreciate any guidance as to what the errors mean and how to go about fixing them.
See errors below:
Starting test: SystemLog
         An Warning Event occurred. EventID: 0x80001795
            Time Generated: 04/10/2014   12:52:35
            Event String:
            The program w3wp.exe, with the assigned process ID 7684, could not authenticate locally by using the target name HTTP/remote.legacyhc.com. The target name used is not valid. A target
name should refer to one of the local computer names, for example, the DNS host name.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   12:53:17
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   12:58:22
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:03:27
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:08:31
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:13:37
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:18:41
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:23:45
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:28:51
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:33:55
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:38:59
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Error Event occurred. EventID: 0xC0002719
            Time Generated: 04/10/2014   13:42:34
            Event String:
            DCOM was unable to communicate with the computer 208.67.220.220 using any of the configured protocols.
         An Error Event occurred. EventID: 0xC0002719
            Time Generated: 04/10/2014   13:42:56
            Event String:
            DCOM was unable to communicate with the computer 208.67.222.222 using any of the configured protocols.
         An Error Event occurred. EventID: 0xC0002719
            Time Generated: 04/10/2014   13:43:17
            Event String:
            DCOM was unable to communicate with the computer 8.8.4.4 using any of the configured protocols.
         An Error Event occurred. EventID: 0xC0002719
            Time Generated: 04/10/2014   13:43:38
            Event String:
            DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:44:05
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         ......................... LEGACYDC failed test SystemLog
      Starting test: Topology
         ......................... LEGACYDC passed test Topology
      Starting test: VerifyEnterpriseReferences
         The following problems were found while verifying various important DN
         references. Note, that these problems can be reported because of
         latency in replication. So follow up to resolve the following
         problems, only if the same problem is reported on all DCs for a given
         domain or if the problem persists after replication has had
         reasonable time to replicate changes.
            [1] Problem: Missing Expected Value
             Base Object:
            CN=PETERSONDC1,OU=Domain Controllers,DC=legacyhc,DC=local
             Base Object Description: "DC Account Object"
             Value Object Attribute Name: msDFSR-ComputerReferenceBL
             Value Object Description: "SYSVOL FRS Member Object"
             Recommended Action: See Knowledge Base Article: Q312862
            [2] Problem: Missing Expected Value
             Base Object:
            CN=EVANSTONDC,OU=Domain Controllers,DC=legacyhc,DC=local
             Base Object Description: "DC Account Object"
             Value Object Attribute Name: msDFSR-ComputerReferenceBL
             Value Object Description: "SYSVOL FRS Member Object"
             Recommended Action: See Knowledge Base Article: Q312862
            [3] Problem: Missing Expected Value
             Base Object:
            CN=LAGRANGE-VDC,OU=Domain Controllers,DC=legacyhc,DC=local
             Base Object Description: "DC Account Object"
             Value Object Attribute Name: msDFSR-ComputerReferenceBL
             Value Object Description: "SYSVOL FRS Member Object"
             Recommended Action: See Knowledge Base Article: Q312862
            [4] Problem: Missing Expected Value
             Base Object:
            CN=ARLINGTON-VDC,OU=Domain Controllers,DC=legacyhc,DC=local
             Base Object Description: "DC Account Object"
             Value Object Attribute Name: msDFSR-ComputerReferenceBL
             Value Object Description: "SYSVOL FRS Member Object"
             Recommended Action: See Knowledge Base Article: Q312862
            [5] Problem: Missing Expected Value
             Base Object:
            CN=AURORA-VDC,OU=Domain Controllers,DC=legacyhc,DC=local
             Base Object Description: "DC Account Object"
             Value Object Attribute Name: msDFSR-ComputerReferenceBL
             Value Object Description: "SYSVOL FRS Member Object"
             Recommended Action: See Knowledge Base Article: Q312862
            LDAP Error 0x5e (94) - No result present in message.
         ......................... LEGACYDC failed test

The note above is correct, the IPs in your DCDIAG are all public DNS servers:
208.67.220.220 and 208.67.222.222 are OpenDNS
8.8.8.8 and 8.8.4.4 are Google's DNS servers
The KB article that is referenced is calling out deleted FRS objects, so you may have some corruption in your AD environment.
I would take a look at the DNS, FRS, and other AD related logs and see what is there. Hopefully you have a recent backup that you can recover with if needed.
Although it is possible the issue is that your account does not have the rights to run the dcdiag. The event logs should have additional details that help.

Similar Messages

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.

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: SERVER6 failed test Advertising

This is one of quite a few errors I get after running a dcdiag on this particular domain controller:
   Testing server: Default-First-Site-Name\SERVER6
      Starting test: Advertising
         Warning: DsGetDcName returned information for
\\server5.domain.local,
         when we were trying to reach SERVER6.
         SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
Anyone know what might be going on here? Why is information being returned for server5 instead of server6?

Hi,
The error message SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE could be caused by that sysvol and netlogon share are not available.
Here are some suggestions for you:
Please open CMD then run "net share" command to confirm if they are shared successfully.
Make sure that needed ports for AD replication are not blocked in both directions and each DC has one IP address and one NIC card.
Make sure both DCs point to your DNS servers correctly. In addition, you can run ipconfig /registerdns and restart netlogon on each DC to re-register DNS records.
More detailed information, please refer to following threads:
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE ......................... ad2008R2 failed test Advertising
http://social.technet.microsoft.com/Forums/windowsserver/en-US/6713c55f-0bc5-4d74-a18b-b867ccc9d059/server-is-not-responding-or-is-not-considered-suitable-ad2008r2-failed?forum=winserverDS
Failed Advertising Test
http://social.technet.microsoft.com/Forums/windowsserver/en-US/831c58de-003b-4b9d-9da4-7f3d992e74c6/failed-advertising-test?forum=winservergen
Best Regards,
Erin

Domain controller permissions / dcdiag

Hi
When I run dcdiag without administistrative permissions (Run as admin); the dcdiag represents a wide range of different errors however when I do run it by "run as admin" it doesn't display the errors. Moreover; While I am Enterprise administrator,
and appropriate NTFS permissions are provided, I do not have permision on the NTDS folder( and files). I've add my account directly on the NTDS and solved the problem. I am wondering about the main cause of the problem.
There are 5 DCs in my enviroment; however I just faced the abovementioned problems only one of the newly promoted one. The enviroment is a windows 2003/2012R2 hybrid.

I would not consider this as a problem and it should be UAC related: http://andywolf.com/dcdiag-and-repadmin-access-denied-errors-on-2008-r2-dc/
Simply run dcdiag using an elevated prompt. This is how I always proceed.
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 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 DNStest TEST:Dynamic update

Hi,
I did a dcdiag DNS test by issuing the command "dcdiag /test:DNS". Upon looking at the output, I have the following line that says:
TEST: Dynamic update (dyn)
Warning: Failed to delete the test record dcdiag-test-record in zone xxx.com
But it passed the DNS test.
I've searched over the internet and they say that this happens if dynamic updates is set to "Nonsecure and secure". I've looked into our AD/DNS Servers and it is set to "sercure only".
What could have caused this? Is this ignorable?

Hello,
if you use DNS dynamic updates please assure that it is set to SECURE ONLY. If that isn't the case you may get this error message.
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

Dcdiag dns checks failing on external update attempt

It does sound like you're using an external DNS on that server instead of the internal ones.

While preparing to demote a DC I ran dcdiag and it's failing while attempting to register records in our external dns server at rackspace. I can only assume that since we use the same domain externally, and for AD, that the domain controller is seeing rackspace as authoritative and attempting to create the test records there. Has anyone seen this behavior before? It's never been a problem until now, and this issue did not appear in the logs when I demoted another DC earlier tonight.
Log:TextAn error event occurred. EventID: 0x0000168E Time Generated: 11/15/2010 15:37:52 Event String: The dynamic registration of the DNS record 'ForestDnsZones.contoso.com. 600 IN A 192.168.1.234' failed on the following DNS server: The DNS server it goes on to list is the public IP of our rackspace DNS.There are many of these errors listed as it attempts...
This topic first appeared in the Spiceworks Community

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.

Domain Controller DCDIAG DNS Failure

I have 18 domain controllers distributed world-wide and DNS hasn't been an issue. However I ran a DCDIAG /e /test:dns to validate my configurations and received this alert for a remote domain controller.
Running enterprise tests on : domain.com
    Starting test: DNS
       Test results for domain controllers:
          DC: SERVER.Domain.com
          Domain: Domain.com
             TEST: Basic (Basc)
                Error: Can't read OS version through WMI
                No host records (A or AAAA) were found for this DC
       Summary of DNS test results:
                                          Auth Basc
Forw Del Dyn RReg Ext
          Domain: Domain.com
             SERVER PASS FAIL n/a n/a n/a n/a n/a
       ......................... domain.com failed test DNS
I verified that the domain controller has an A record in DNS. The SRV records seem to be in place.
Any advice?
Thanks

I would agree with Pierre.
It might be that your WMI database is corrupted. You can do the required analysis using this MS tool: https://www.microsoft.com/en-us/download/details.aspx?id=7684
You can also rebuild the WMI repository using the method shared here: http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx
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

Failing frsevent in dcdiag

Hi there, I am in the process of upgrading our DCs, and am making sure things in the AD are clean, but when I run dcdiag, I receive the following error:
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... LEDC01 passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
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.
An Error Event occured. EventID: 0xC00034F7
Time Generated: 01/16/2015 09:04:22
(Event String could not be retrieved)
......................... LEDC01 failed test frsevent
I have cleared the System event log, but the issue still persists. Any ideas what I should be trying next?

Hi,
In addition, here are more troubleshooting articles below for you：
How To Troubleshoot the File Replication Service in Windows Server 2003
http://support.microsoft.com/kb/327341
Troubleshooting FRS
http://technet.microsoft.com/en-us/library/cc962209.aspx
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

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 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

DCDIAG reports broken delegations but not having any DNS issues.

I am planning on moving my 2003 domain to a 2012 domain, I need to resolve all the dns issues with my current domain. When i run DCDIAG i get the following error for all of my name servers. I have 3 seperate forests. I use forwarders to forward to all my
dns servers. I have no DNS issues as far as i know. When i run dcdiag on any of my DC's i get the following error for everyone of my Name Servers.
DNS server: 20.26.212.204 (server.mydomain.com.)
4 test failures on this DNS server
This is a valid DNS server
Name resolution is funtional. _ldap._tcp SRV record for the forest root domain is registered
Delegation is broken for the domain mydomain.com.mydomain.com. on the DNS server x.x.x.x
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
The only zones in my dns are the _msdcs.mydomain.com and mydomain.com. I do not understand why it is saying mydomain.com.mydomain.com in the error. I am not sure where else to look to try and resolve this error.
Any help greatly appreciated.
Thanks for your help

Hi,
Base on my experience, that must be the Delegated zone issue, this issue is because the new DNS
has duplicated the name for parent and child domain, you can try to backup your current DNS then delete the duplicate zone then restart the DNS service.
More information:
Back up a Zone File
http://technet.microsoft.com/en-us/library/ee649198(v=ws.10).aspx
Understanding Zone Delegation
http://technet.microsoft.com/en-gb/library/cc771640.aspx
Create a delegation for a domain controller
http://technet.microsoft.com/en-us/library/cc757375(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

DCDIag Assistance

Hi, im getting a lot of best practise analyser errors and warnings etc.
I had an old lab DC that I demoted and joined to a new 2012 DC as a secondary DC.
I have numerous errors and dns just doesn't seems right I deleted reference to my old records in dns and thought id cleaned things up but not sure I have.
also on the secondary DC there is no netlogon or sysvol so I don't have replication between dcs
d
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   Home Server = MYDC
   * Identified AD Forest.
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\MYDC
      Starting test: Connectivity
         ......................... MYDC passed test Connectivity
Doing primary tests
   Testing server: Default-First-Site-Name\MYDC
      Starting test: Advertising
         Warning: DsGetDcName returned information for
\\SVR2012PDC.AlexCorpDom.Internal, when we were trying to reach
         MYDC.
         SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
         ......................... MYDC failed test Advertising
      Starting test: FrsEvent
         ......................... MYDC passed test FrsEvent
      Starting test: DFSREvent
         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.
         ......................... MYDC failed test DFSREvent
      Starting test: SysVolCheck
         ......................... MYDC passed test SysVolCheck
      Starting test: KccEvent
         ......................... MYDC passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... MYDC passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... MYDC passed test MachineAccount
      Starting test: NCSecDesc
         ......................... MYDC passed test NCSecDesc
      Starting test: NetLogons
         Unable to connect to the NETLOGON share! (\\MYDC\netlogon)
         MYDC An net use or LsaPolicy operation failed with error 67,
         The network name cannot be found..
         ......................... MYDC failed test NetLogons
      Starting test: ObjectsReplicated
         ......................... MYDC passed test ObjectsReplicated
      Starting test: Replications
         ......................... MYDC passed test Replications
      Starting test: RidManager
         ......................... MYDC passed test RidManager
      Starting test: Services
         ......................... MYDC passed test Services
      Starting test: SystemLog
         A warning event occurred. EventID: 0x0000008E
            Time Generated: 02/14/2014   11:23:21
            Event String:
            The time service has stopped advertising as a time source because the local clock is not synchronized.
         A warning event occurred. EventID: 0x00001695
            Time Generated: 02/14/2014   11:35:11
            Event String:
            Dynamic registration or deletion of one or more DNS records associated with DNS domain 'oldDC.local.' failed. These records are used by other computers to locate this server as a domain
controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).
         A warning event occurred. EventID: 0x00001695
            Time Generated: 02/14/2014   11:35:11
            Event String:
            Dynamic registration or deletion of one or more DNS records associated with DNS domain 'DomainDnsZones.OLDDC.local.' failed. These records are used by other computers to locate this
server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).
         A warning event occurred. EventID: 0x00001695
            Time Generated: 02/14/2014   11:35:11
            Event String:
            Dynamic registration or deletion of one or more DNS records associated with DNS domain 'ForestDnsZones.OLDDC.local' failed. These records are used by other computers to locate this
server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).
         A warning event occurred. EventID: 0x0000008E
            Time Generated: 02/14/2014   12:06:49
            Event String:
            The time service has stopped advertising as a time source because the local clock is not synchronized.
         A warning event occurred. EventID: 0x00000032
            Time Generated: 02/14/2014   12:06:49
            Event String:
            The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by
suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.
         A warning event occurred. EventID: 0x0000008E
            Time Generated: 02/14/2014   12:09:01
            Event String:
            The time service has stopped advertising as a time source because the local clock is not synchronized.
         ......................... MYDC passed test SystemLog
      Starting test: VerifyReferences
         ......................... MYDC passed test VerifyReferences
   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test
         CrossRefValidation
   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones 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 : AlexCorpDom
      Starting test: CheckSDRefDom
         ......................... AlexCorpDom passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... AlexCorpDom passed test CrossRefValidation
   Running enterprise tests on : AlexCorpDom.Internal
      Starting test: LocatorCheck
         ......................... AlexCorpDom.Internal passed test
         LocatorCheck
      Starting test: Intersite
         ......................... AlexCorpDom.Internal passed test Intersite
cdiag output below (this output is fro the second dc). any help appreciated

That's didn't work
I have changed the dns and configured net time as that was throwing errors.
new dcdiag (on old DC)
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   Home Server = MYDC
   * Identified AD Forest.
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\MYDC
      Starting test: Connectivity
         ......................... MYDC passed test Connectivity
Doing primary tests
   Testing server: Default-First-Site-Name\MYDC
      Starting test: Advertising
         Warning: DsGetDcName returned information for
\\SVR2012PDC.AlexCorpDom.Internal, when we were trying to reach
         MYDC.
         SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
         ......................... MYDC failed test Advertising
      Starting test: FrsEvent
         ......................... MYDC passed test FrsEvent
      Starting test: DFSREvent
         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.
         ......................... MYDC failed test DFSREvent
      Starting test: SysVolCheck
         ......................... MYDC passed test SysVolCheck
      Starting test: KccEvent
         ......................... MYDC passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... MYDC passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... MYDC passed test MachineAccount
      Starting test: NCSecDesc
         ......................... MYDC passed test NCSecDesc
      Starting test: NetLogons
         Unable to connect to the NETLOGON share! (\\MYDC\netlogon)
         [MYDC] An net use or LsaPolicy operation failed with error 67,
         The network name cannot be found..
         ......................... MYDC failed test NetLogons
      Starting test: ObjectsReplicated
         ......................... MYDC passed test ObjectsReplicated
      Starting test: Replications
         ......................... MYDC passed test Replications
      Starting test: RidManager
         ......................... MYDC passed test RidManager
      Starting test: Services
         ......................... MYDC passed test Services
      Starting test: SystemLog
         A warning event occurred. EventID: 0x000003F6
            Time Generated: 02/16/2014   17:41:03
            Event String:
            Name resolution for the name 01cc.centrastage.net timed out after none of the configured DNS servers responded.
         An error event occurred. EventID: 0xC0001B61
            Time Generated: 02/16/2014   17:47:59
            Event String:
            A timeout was reached (30000 milliseconds) while waiting for the File Replication Service service to connect.
         An error event occurred. EventID: 0xC0001B61
            Time Generated: 02/16/2014   17:48:30
            Event String:
            A timeout was reached (30000 milliseconds) while waiting for the File Replication Service service to connect.
         An error event occurred. EventID: 0xC0001B61
            Time Generated: 02/16/2014   17:48:50
            Event String:
            A timeout was reached (30000 milliseconds) while waiting for the File Replication Service service to connect.
         A warning event occurred. EventID: 0x0000008E
            Time Generated: 02/16/2014   18:00:58
            Event String:
            The time service has stopped advertising as a time source because the local clock is not synchronized.
         A warning event occurred. EventID: 0x00000032
            Time Generated: 02/16/2014   18:00:58
            Event String:
            The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by
suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.
         A warning event occurred. EventID: 0x0000008E
            Time Generated: 02/16/2014   18:03:01
            Event String:
            The time service has stopped advertising as a time source because the local clock is not synchronized.
         An error event occurred. EventID: 0xC000271A
            Time Generated: 02/16/2014   18:05:35
            Event String:
            The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
         An error event occurred. EventID: 0xC004002E
            Time Generated: 02/16/2014   18:06:32
            Event String: Crash dump initialization failed!
         A warning event occurred. EventID: 0x8000001D
            Time Generated: 02/16/2014   18:06:45
            Event String:
            The Key Distribution Center (KDC) cannot find a suitable certificate to use for smart card logons, or the KDC certificate could not be verified. Smart card logon may not function correctly
if this problem is not resolved. To correct this problem, either verify the existing KDC certificate using certutil.exe or enroll for a new KDC certificate.
         A warning event occurred. EventID: 0x00000079
            Time Generated: 02/16/2014   18:06:47
            Event String:
            The firewall exception to allow Internet Storage Name Server (iSNS) client functionality is not enabled. iSNS client functionality is not available.
         An error event occurred. EventID: 0xC0001B61
            Time Generated: 02/16/2014   18:07:00
            Event String:
            A timeout was reached (30000 milliseconds) while waiting for the File Replication Service service to connect.
         An error event occurred. EventID: 0xC00003EC
            Time Generated: 02/16/2014   18:07:07
            Event String:
            The World Wide Web Publishing Service (WWW Service) did not register the URL prefix
http://*:80/ for site 1. The site has been disabled. The data field contains the error number.
         An error event occurred. EventID: 0xC0003A9D
            Time Generated: 02/16/2014   18:07:07
            Event String:
            Unable to bind to the underlying transport for [::]:80. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains
the error number.
         A warning event occurred. EventID: 0x80003BC4
            Time Generated: 02/16/2014   18:07:10
            Event String:
            SSL Certificate Settings deleted for Port : 0.0.0.0:9875 .
         A warning event occurred. EventID: 0x80003BC5
            Time Generated: 02/16/2014   18:07:11
            Event String:
            SSL Certificate Settings created by an admin process for Port : 0.0.0.0:9875 .
         An error event occurred. EventID: 0xC0001B72
            Time Generated: 02/16/2014   18:07:27
            Event String:
            The following boot-start or system-start driver(s) failed to load:
         A warning event occurred. EventID: 0x0000006C
            Time Generated: 02/16/2014   18:07:41
            Event String:
            Status 0x00001069 determining that device interface
\\?\{8e7bd593-6e6c-4c52-86a6-77175494dd8e}#MsVhdHba#1&3030e83&0&01#{2accfe60-c130-11d2-b082-00a0c91efb8b} does not support iSCSI WMI interfaces. If this device is not an iSCSI HBA then this error can be ignored.
         An error event occurred. EventID: 0xC0001B61
            Time Generated: 02/16/2014   18:09:20
            Event String:
            A timeout was reached (30000 milliseconds) while waiting for the File Replication Service service to connect.
         A warning event occurred. EventID: 0x00001695
            Time Generated: 02/16/2014   18:22:26
            Event String:
            Dynamic registration or deletion of one or more DNS records associated with DNS domain 'olddomain.local.' failed. These records are used by other computers to locate this server as
a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).
         A warning event occurred. EventID: 0x00001695
            Time Generated: 02/16/2014   18:22:28
            Event String:
            Dynamic registration or deletion of one or more DNS records associated with DNS domain 'DomainDnsZones.olddomain.local.' failed. These records are used by other computers to locate
this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).
         A warning event occurred. EventID: 0x00001695
            Time Generated: 02/16/2014   18:22:28
            Event String:
            Dynamic registration or deletion of one or more DNS records associated with DNS domain 'ForestDnsZones.olddomain.local.' failed. These records are used by other computers to locate
this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).
         ......................... MYDC failed test SystemLog
      Starting test: VerifyReferences
         ......................... MYDC passed test VerifyReferences
   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test
         CrossRefValidation
   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones 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 : AlexCorpDom
      Starting test: CheckSDRefDom
         ......................... AlexCorpDom passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... AlexCorpDom passed test CrossRefValidation
   Running enterprise tests on : AlexCorpDom.Internal
      Starting test: LocatorCheck
         ......................... AlexCorpDom.Internal passed test
         LocatorCheck
      Starting test: Intersite
         ......................... AlexCorpDom.Internal passed test Intersite
replmon below
Repadmin experienced the following error trying to resolve the DSA_NAME: dc*
If you are trying to connect to an AD LDS instance, you must use <server>:<port>
If you are trying to connect to an AD LDS instance with wildcarding support, you must use the /homeserver option.
Error: An error occurred:
    Win32 Error 8419(0x20e3): The DSA object could not be found.

DCDIAG

Similar Messages

Maybe you are looking for