DCDiag GUID Error

Discussion in 'DNS Server' started by Thom Paine, Feb 6, 2007.

  1. Thom Paine

    Thom Paine Guest

    I'm having problems with my server, and I ran the dcdiag and it's coming up
    about the guid of the server not resolving. I'm unsure how to correct this
    error.

    Testing server: Default-First-Site\PDC-RL-401
    Starting test: Connectivity
    PDC-RL-401's server GUID DNS name could not be resolved to an
    IP address. Check the DNS server, DHCP, server name, etc
    Although the Guid DNS name

    (e2756922-bc3d-440c-a4b8-40794678c722._msdcs.RocklandFlooring.local)

    couldn't be resolved, the server name

    (PDC-RL-401.RocklandFlooring.local) resolved to the IP address

    (192.168.0.2) and was pingable. Check that the IP address is

    registered correctly with the DNS server.
    ......................... PDC-RL-401 failed test Connectivity

    Where would I go to fix this?

    Thanks.
     
    Thom Paine, Feb 6, 2007
    #1
    1. Advertisements

  2. Thom Paine

    Thom Paine Guest

    I should followup that google hits telling me to try dcdiag /fix and
    stopping and starting the netlogon service have proved unsuccessful.
     
    Thom Paine, Feb 6, 2007
    #2
    1. Advertisements

  3. Thom Paine

    Herb Martin Guest

    Ok there are two major reasons for these failures so you check and correct
    these, then re-run the NetDiag /fix or stop/start NetLogon AGAIN, as you
    already
    tried.

    Typical reasons:

    On DNS Server:
    1) zone is not dynamic
    2) zone doesn't exist
    3) Multiple DNS servers, but not replicated (see other fixes too)
    arrange secondary zone transfer from primary or other master

    Check the above for both the "domain zone" and the _MSDCS zone if
    it is separate (i.e., not a subdomain of the domain zone itself.)

    On DC as a DNS "client":
    1) NIC must point STRICTLY at the INTERNAL DNS servers
    2) Remove any external (ISP etc) DNS server
    3) If replication problem persists, set all DCs to ONE "favored" DNS
    server until replication is fixed -- inefficient but
    works for
    temporary fix purposes

    DC replication of AD and integrated DNS:
    1) DCs are AD Integrated but not replicating so DNS is also not
    replicating -- use "DNS client" #3 above.
     
    Herb Martin, Feb 6, 2007
    #3
  4. Thom Paine

    Thom Paine Guest

    One quick question.

    Should I have the DNS ip in the TCPIP properties of my nic to be 127.0.0.1
    or should it be the IP address of my server?
    This is on the server., not on workstations. On workstations I have only the
    IP of the server.

    Thanks.
     
    Thom Paine, Feb 7, 2007
    #4
  5. Thom Paine

    Thom Paine Guest

    Herb:

    I have the _msdcs zone as a subdomain of my scps.lan domain. I looked at my
    old server which is running Windows 2000 server that worked awesome and it
    has the guid in the _msdcs zone. I tried creating this CNAME record but I
    get an error that this CNAME record cannot be added to this domain because
    it contains records that are incompatible with the cname record.

    Also, I am unable to run netdiag as I get a different error. The error
    message is:

    The procedure entry point DnsGetPrimaryDomainName_UTF8 could not be located
    in the dynamic link library DNSAPI.dll.

    I have the Windows Server 2003 Resource kit, but I can't seem to get this
    working after alot of reading and googling.

    Thanks.

    -=/>Thom
     
    Thom Paine, Feb 7, 2007
    #5
  6. Thom Paine

    Herb Martin Guest

    It isn't that big a deal which you use. They route to the same place.
    That is correct also. All of your DNS "clients" (all of your machines) must
    use strictly the addresses of your Internal DNS server (set).

    On a machine, 127.0.0.1 is equivalent to it's own address.
     
    Herb Martin, Feb 7, 2007
    #6
  7. Thom Paine

    Herb Martin Guest

    The above paragraph made some sense but ended in confusing me --
    You would ahve ONLY the _msdcs in your AD zone if you started with
    Win2000, but it would be separate (also) if you started with Win2003.

    If separate, that zone needs to be dynamic and replicated to (or findable
    by)
    all of your internal DNS servers.
    Likely wrong NetDiag. You need SP1 or some current NetDiag from the later
    Support Tools. Or you are running Win2000 tools on Win2003 or vice versa.
    "Can't seem to get it working" is not something that I can diagnose beyond
    telling
    you to go back to Microsoft and download the one that matches you OS and
    SP status.
     
    Herb Martin, Feb 7, 2007
    #7
  8. Thom Paine

    Herb Martin Guest


    Sorry, I don't open .Doc files from unverified sources.

    Post a jpg or something on a web site.

    Do you currently have any DNS problems? What are you current symptoms?
     
    Herb Martin, Feb 7, 2007
    #8
  9. Thom Paine

    Thom Paine Guest

    The above paragraph made some sense but ended in confusing me --
    This is a brand new dell server running 2003 r2.
    Everything was a fresh install. No upgrade was done.
    I found the correct version and I am able to run netdiag and dcdiag now.
    Here is the output from dcdiag. I have a dns issue and slow logons and some
    other problems. I think the root of it is dns issues with group policy.


    Domain Controller Diagnosis

    Performing initial setup:
    Done gathering initial info.

    Doing initial required tests

    Testing server: Default-First-Site\PDC-SCPS-2006
    Starting test: Connectivity
    The host ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan could
    not be resolved to an
    IP address. Check the DNS server, DHCP, server name, etc
    Although the Guid DNS name

    (ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan) couldn't be

    resolved, the server name (PDC-SCPS-2006.scps.lan) resolved to the
    IP

    address (192.168.142.150) and was pingable. Check that the IP
    address

    is registered correctly with the DNS server.
    ......................... PDC-SCPS-2006 failed test Connectivity

    Doing primary tests

    Testing server: Default-First-Site\PDC-SCPS-2006
    Skipping all tests, because server PDC-SCPS-2006 is
    not responding to directory service requests

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

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

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

    Running enterprise tests on : scps.lan
    Starting test: Intersite
    ......................... scps.lan passed test Intersite
    Starting test: FsmoCheck
    ......................... scps.lan passed test FsmoCheck


    Thanks.

    -=/>Thom
     
    Thom Paine, Feb 7, 2007
    #9
  10. Thom Paine

    Thom Paine Guest

    Thom Paine, Feb 7, 2007
    #10
  11. Thom Paine

    Herb Martin Guest

    Including adding the 2003 DC to the Domain or Forest?

    This is about upgrading Forests which you seem to imply when
    you mention your Win2000 DC.
    Your DC is not properly registered in DNS.

    Show me the IPConfig /all from each DC.

    Check the _msdcs zone to make sure all DCs can resolve from it.

    Check that it is dynamic.

    Check that all DCs can find the "primary" (Master) and register themselves
    in that zone.

    After all this is correct, run "Netdiag /fix" or restart NetLogon service,
    and then retry DCDiag /C /D on every DC.
     
    Herb Martin, Feb 7, 2007
    #11
  12. Thom Paine

    Herb Martin Guest

    Herb Martin, Feb 7, 2007
    #12
  13. Thom Paine

    Thom Paine Guest

    This is a brand new dell server running 2003 r2.

    This is the only server on our lan. We decommissioned our 2000 server. The
    two servers were not on the lan at the same time. A new lan was built in a
    separate enviornment and then the client pc's were wiped and loaded on the
    new lan.

    There is only one DC.

    Windows IP Configuration
    Host Name . . . . . . . . . . . . : PDC-SCPS-2006
    Primary Dns Suffix . . . . . . . : scps.lan
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : scps.lan
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
    Connection
    Physical Address. . . . . . . . . : 00-13-72-56-E8-26
    DHCP Enabled. . . . . . . . . . . : No
    IP Address. . . . . . . . . . . . : 192.168.142.150
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.142.10
    DNS Servers . . . . . . . . . . . : 192.168.142.150
    Primary WINS Server . . . . . . . : 192.168.142.150

    I'm not sure how to check this since we only have one server.
    I ran the server setup wizard when we got the new server and added the roles
    I wanted it to do. This included active directory, dns, dhcp fileserver, and
    print server.
    Thanks Herb. I appreciate all this help.

    -=/>Thom
     
    Thom Paine, Feb 7, 2007
    #13
  14. Thom Paine

    Herb Martin Guest

    Did you properly DCPromo so that the old server was removed from the
    AD? (Otherwise you must do the NTDSUtil "metadata cleanup" procedure").
    This would cause 'failures' to replicate with the server that is no longer
    available.

    Do you have a GC? Many people who have decommisioned a DC have
    neglected to set the replacement as a GC. (Set a GC in AD Sites and
    Services.)

    What about your FSMO, or single master roles? Did you transfer them to
    the new DC? (If not you will need to seize those roles but this doesn't
    seem
    to be your issue.)
    Is _MSDCS a separate zone or not (previous messages were unclear on
    this point)?

    If separate is it DYNAMIC?
    As a new domain or did you join it to an older domain before removing your
    old DC?
    Did it work yet?
     
    Herb Martin, Feb 7, 2007
    #14
  15. Thom Paine

    Thom Paine Guest

    This is the only server on our lan. We decommissioned our 2000 server.
    We started from scratch. So basically we set up the new lan with the new
    server and manually input the users again. I guess you could say we just
    deployed this lan for the first time. I have the old server sitting here
    just for reference.


    It is a subzone of the scps.lan zone.
    I do not know how to tell if it is dynamic. I checked the properties on
    scps.lan and it says dynamic updates - secure only. Is that the right spot
    to check this?
    As a new domain. I migrated data with a thumbdrive since there was so
    little.
     
    Thom Paine, Feb 7, 2007
    #15
  16. Thom Paine

    Herb Martin Guest

    [ You confused the issue by bringing up your 2000 Server a few
    messages back in this thread. ]
    Then it is dynamic IF the main zone is dynamic. You might as well check
    that but they likely are dynamic since DCPromo does that IF you let DCPromo
    setup the DNS.

    Did you let DCPromo create the DNS or did you do it manually?
    (If you did it manually then you likely didn't make it dynamic OR you
    have it as a Secondary to the now missing Primary on your old server.)

    Look at the Zone properties for scps.lan zone properties, and tell me what
    TYPE of server it is, and if it is set to DYNAMIC updates allowed or not.
    (Type: Primary, AD Integrated, Secondary, or unlikely a Stub.)
    Did you setup DNS yourself or just let the DCPromo do that?

    Run NetDiag /Fix (again after each change).

    Then check (each time) DCDiag /c /d tell you now?

    You should always send DCDiag to a text file and open it in a text editor so
    that you can easily search for FAIL and WARN messages.
     
    Herb Martin, Feb 7, 2007
    #16
  17. Thom Paine

    Thom Paine Guest

    Here is the output from netdiag /fix and dcdiag /C /D.

    Netdiag:
    ........................................
    Computer Name: PDC-SCPS-2006
    DNS Host Name: PDC-SCPS-2006.scps.lan
    System info : Microsoft Windows Server 2003 R2 (Build 3790)
    Processor : x86 Family 15 Model 4 Stepping 3, GenuineIntel
    List of installed hotfixes :
    KB833407
    KB890046
    KB893756
    KB896358
    KB896422
    KB896424
    KB896428
    KB896688
    KB898715
    KB898792
    KB899587
    KB899588
    KB899589
    KB899591
    KB900725
    KB901017
    KB901214
    KB902400
    KB904706
    KB904942
    KB905414
    KB908519
    KB908531
    KB909520
    KB910437
    KB911280
    KB911562
    KB911567
    KB911897
    KB911927
    KB912919
    KB914388
    KB914389
    KB916281
    KB917159
    KB917344
    KB917422
    KB917537
    KB917734
    KB917953
    KB918439
    KB918899
    KB920213
    KB920214
    KB920670
    KB920683
    KB920685
    KB921398
    KB921883
    KB922582
    KB922616
    KB922760
    KB922819
    KB923191
    KB923414
    KB923689
    KB923694
    KB923980
    KB924191
    KB924496
    KB925398_WMP64
    KB925454
    KB925486
    KB929969
    Q147222
    Netcard queries test . . . . . . . : Passed
    Per interface results:
    Adapter : Local Area Connection
    Netcard queries test . . . : Passed
    Host Name. . . . . . . . . : PDC-SCPS-2006
    IP Address . . . . . . . . : 192.168.142.150
    Subnet Mask. . . . . . . . : 255.255.255.0
    Default Gateway. . . . . . : 192.168.142.10
    Primary WINS Server. . . . : 192.168.142.150
    Dns Servers. . . . . . . . : 192.168.142.150
    AutoConfiguration results. . . . . . : Passed
    Default gateway test . . . : Passed
    NetBT name test. . . . . . : Passed
    [WARNING] At least one of the <00> 'WorkStation Service', <03>
    'Messenger Service', <20> 'WINS' names is missing.
    WINS service test. . . . . : Passed
    Global results:
    Domain membership test . . . . . . : Passed
    NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
    NetBT_Tcpip_{116CE9C7-BA23-47D3-9B92-877898A08AD3}
    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
    Service', <03> 'Messenger Service', <20> 'WINS' names defined.
    Winsock test . . . . . . . . . . . : Passed
    DNS test . . . . . . . . . . . . . : Failed
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.scps.lan.
    re-registeration on DNS server '192.168.142.150' failed.
    DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.scps.lan.
    re-registeration on DNS server '192.168.142.150' failed.
    DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry
    _ldap._tcp.Default-First-Site._sites.gc._msdcs.scps.lan. re-registeration on
    DNS server '192.168.142.150' failed.
    DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry
    _ldap._tcp.2d42cc4c-e067-476f-8857-9ee03651b5f6.domains._msdcs.scps.lan.
    re-registeration on DNS server '192.168.142.150' failed.
    DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry
    ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan. re-registeration on
    DNS server '192.168.142.150' failed.
    DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.scps.lan.
    re-registeration on DNS server '192.168.142.150' failed.
    DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry
    _kerberos._tcp.Default-First-Site._sites.dc._msdcs.scps.lan.
    re-registeration on DNS server '192.168.142.150' failed.
    DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.scps.lan.
    re-registeration on DNS server '192.168.142.150' failed.
    DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry
    _ldap._tcp.Default-First-Site._sites.dc._msdcs.scps.lan. re-registeration on
    DNS server '192.168.142.150' failed.
    DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.scps.lan. re-registeration
    on DNS server '192.168.142.150' failed.
    DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
    [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries
    for this DC on DNS server '192.168.142.150'.
    [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_{116CE9C7-BA23-47D3-9B92-877898A08AD3}
    The redir is bound to 1 NetBt transport.
    List of NetBt transports currently bound to the browser
    NetBT_Tcpip_{116CE9C7-BA23-47D3-9B92-877898A08AD3}
    The browser is bound to 1 NetBt transport.
    DC discovery test. . . . . . . . . : Passed
    DC list test . . . . . . . . . . . : Passed
    Trust relationship test. . . . . . : Skipped
    Kerberos test. . . . . . . . . . . : Passed
    LDAP test. . . . . . . . . . . . . : Passed
    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







    Here is the output from dcdiag:
    Command Line: "dcdiag.exe /C /D"
    Domain Controller Diagnosis
    Performing initial setup:
    * Verifying that the local machine PDC-SCPS-2006, is a DC.
    * Connecting to directory service on server PDC-SCPS-2006.
    PDC-SCPS-2006.currentTime = 20070207190417.0Z
    PDC-SCPS-2006.highestCommittedUSN = 246229
    PDC-SCPS-2006.isSynchronized = 1
    PDC-SCPS-2006.isGlobalCatalogReady = 1
    * Collecting site info.
    * Identifying all servers.
    PDC-SCPS-2006.currentTime = 20070207190417.0Z
    PDC-SCPS-2006.highestCommittedUSN = 246229
    PDC-SCPS-2006.isSynchronized = 1
    PDC-SCPS-2006.isGlobalCatalogReady = 1
    * Identifying all NC cross-refs.
    * Found 1 DC(s). Testing 1 of them.
    Done gathering initial info.
    ===============================================Printing out pDsInfo
    GLOBAL:
    ulNumServers=1
    pszRootDomain=scps.lan
    pszNC=
    pszRootDomainFQDN=DC=scps,DC=lan
    pszConfigNc=CN=Configuration,DC=scps,DC=lan
    pszPartitionsDn=CN=Partitions,CN=Configuration,DC=scps,DC=lan
    iSiteOptions=0
    dwTombstoneLifeTimeDays=60
    dwForestBehaviorVersion=0
    HomeServer=0, PDC-SCPS-2006
    SERVER: pServer[0].pszName=PDC-SCPS-2006
    pServer[0].pszGuidDNSName=ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan
    pServer[0].pszDNSName=PDC-SCPS-2006.scps.lan
    pServer[0].pszDn=CN=NTDS
    Settings,CN=PDC-SCPS-2006,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=scps,DC=lan
    pServer[0].pszComputerAccountDn=CN=PDC-SCPS-2006,OU=Domain
    Controllers,DC=scps,DC=lan
    pServer[0].uuidObjectGuid=ef255104-5591-4517-af81-393e31ac9dcf
    pServer[0].uuidInvocationId=ef255104-5591-4517-af81-393e31ac9dcf
    pServer[0].iSite=0 (Default-First-Site)
    pServer[0].iOptions=1
    pServer[0].ftLocalAcquireTime=c3d5a630 01c74aea
    pServer[0].ftRemoteConnectTime=c3bb8e80 01c74aea
    pServer[0].ppszMasterNCs:
    ppszMasterNCs[0]=DC=TAPI3Directory,DC=scps,DC=lan
    ppszMasterNCs[1]=DC=ForestDnsZones,DC=scps,DC=lan
    ppszMasterNCs[2]=DC=DomainDnsZones,DC=scps,DC=lan
    ppszMasterNCs[3]=CN=Schema,CN=Configuration,DC=scps,DC=lan
    ppszMasterNCs[4]=CN=Configuration,DC=scps,DC=lan
    ppszMasterNCs[5]=DC=scps,DC=lan
    SITES: pSites[0].pszName=Default-First-Site
    pSites[0].pszSiteSettings=CN=NTDS Site
    Settings,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=scps,DC=lan
    pSites[0].pszISTG=CN=NTDS
    Settings,CN=PDC-SCPS-2006,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=scps,DC=lan
    pSites[0].iSiteOption=0
    pSites[0].cServers=1
    NC: pNCs[0].pszName=TAPI3Directory
    pNCs[0].pszDn=DC=TAPI3Directory,DC=scps,DC=lan
    pNCs[0].aCrInfo[0].dwFlags=0x00000201
    pNCs[0].aCrInfo[0].pszDn=CN=baf97838-4688-4276-879e-d10c771512e7,CN=Partitions,CN=Configuration,DC=scps,DC=lan
    pNCs[0].aCrInfo[0].pszDnsRoot=TAPI3Directory.scps.lan
    pNCs[0].aCrInfo[0].iSourceServer=0
    pNCs[0].aCrInfo[0].pszSourceServer=(null)
    pNCs[0].aCrInfo[0].ulSystemFlags=0x00000005
    pNCs[0].aCrInfo[0].bEnabled=TRUE
    pNCs[0].aCrInfo[0].ftWhenCreated=00000000 00000000
    pNCs[0].aCrInfo[0].pszSDReferenceDomain=(null)
    pNCs[0].aCrInfo[0].pszNetBiosName=(null)
    pNCs[0].aCrInfo[0].cReplicas=-1
    pNCs[0].aCrInfo[0].aszReplicas=
    NC: pNCs[1].pszName=ForestDnsZones
    pNCs[1].pszDn=DC=ForestDnsZones,DC=scps,DC=lan
    pNCs[1].aCrInfo[0].dwFlags=0x00000201
    pNCs[1].aCrInfo[0].pszDn=CN=1a6c5150-1f62-4e32-af2b-99f3416e7a34,CN=Partitions,CN=Configuration,DC=scps,DC=lan
    pNCs[1].aCrInfo[0].pszDnsRoot=ForestDnsZones.scps.lan
    pNCs[1].aCrInfo[0].iSourceServer=0
    pNCs[1].aCrInfo[0].pszSourceServer=(null)
    pNCs[1].aCrInfo[0].ulSystemFlags=0x00000005
    pNCs[1].aCrInfo[0].bEnabled=TRUE
    pNCs[1].aCrInfo[0].ftWhenCreated=00000000 00000000
    pNCs[1].aCrInfo[0].pszSDReferenceDomain=(null)
    pNCs[1].aCrInfo[0].pszNetBiosName=(null)
    pNCs[1].aCrInfo[0].cReplicas=-1
    pNCs[1].aCrInfo[0].aszReplicas=
    NC: pNCs[2].pszName=DomainDnsZones
    pNCs[2].pszDn=DC=DomainDnsZones,DC=scps,DC=lan
    pNCs[2].aCrInfo[0].dwFlags=0x00000201
    pNCs[2].aCrInfo[0].pszDn=CN=183585ed-3250-448d-ab58-73f068a0d89f,CN=Partitions,CN=Configuration,DC=scps,DC=lan
    pNCs[2].aCrInfo[0].pszDnsRoot=DomainDnsZones.scps.lan
    pNCs[2].aCrInfo[0].iSourceServer=0
    pNCs[2].aCrInfo[0].pszSourceServer=(null)
    pNCs[2].aCrInfo[0].ulSystemFlags=0x00000005
    pNCs[2].aCrInfo[0].bEnabled=TRUE
    pNCs[2].aCrInfo[0].ftWhenCreated=00000000 00000000
    pNCs[2].aCrInfo[0].pszSDReferenceDomain=(null)
    pNCs[2].aCrInfo[0].pszNetBiosName=(null)
    pNCs[2].aCrInfo[0].cReplicas=-1
    pNCs[2].aCrInfo[0].aszReplicas=
    NC: pNCs[3].pszName=Schema
    pNCs[3].pszDn=CN=Schema,CN=Configuration,DC=scps,DC=lan
    pNCs[3].aCrInfo[0].dwFlags=0x00000201
    pNCs[3].aCrInfo[0].pszDn=CN=Enterprise
    Schema,CN=Partitions,CN=Configuration,DC=scps,DC=lan
    pNCs[3].aCrInfo[0].pszDnsRoot=scps.lan
    pNCs[3].aCrInfo[0].iSourceServer=0
    pNCs[3].aCrInfo[0].pszSourceServer=(null)
    pNCs[3].aCrInfo[0].ulSystemFlags=0x00000001
    pNCs[3].aCrInfo[0].bEnabled=TRUE
    pNCs[3].aCrInfo[0].ftWhenCreated=00000000 00000000
    pNCs[3].aCrInfo[0].pszSDReferenceDomain=(null)
    pNCs[3].aCrInfo[0].pszNetBiosName=(null)
    pNCs[3].aCrInfo[0].cReplicas=-1
    pNCs[3].aCrInfo[0].aszReplicas=
    NC: pNCs[4].pszName=Configuration
    pNCs[4].pszDn=CN=Configuration,DC=scps,DC=lan
    pNCs[4].aCrInfo[0].dwFlags=0x00000201
    pNCs[4].aCrInfo[0].pszDn=CN=Enterprise
    Configuration,CN=Partitions,CN=Configuration,DC=scps,DC=lan
    pNCs[4].aCrInfo[0].pszDnsRoot=scps.lan
    pNCs[4].aCrInfo[0].iSourceServer=0
    pNCs[4].aCrInfo[0].pszSourceServer=(null)
    pNCs[4].aCrInfo[0].ulSystemFlags=0x00000001
    pNCs[4].aCrInfo[0].bEnabled=TRUE
    pNCs[4].aCrInfo[0].ftWhenCreated=00000000 00000000
    pNCs[4].aCrInfo[0].pszSDReferenceDomain=(null)
    pNCs[4].aCrInfo[0].pszNetBiosName=(null)
    pNCs[4].aCrInfo[0].cReplicas=-1
    pNCs[4].aCrInfo[0].aszReplicas=
    NC: pNCs[5].pszName=scps
    pNCs[5].pszDn=DC=scps,DC=lan
    pNCs[5].aCrInfo[0].dwFlags=0x00000201
    pNCs[5].aCrInfo[0].pszDn=CN=SCPS,CN=Partitions,CN=Configuration,DC=scps,DC=lan
    pNCs[5].aCrInfo[0].pszDnsRoot=scps.lan
    pNCs[5].aCrInfo[0].iSourceServer=0
    pNCs[5].aCrInfo[0].pszSourceServer=(null)
    pNCs[5].aCrInfo[0].ulSystemFlags=0x00000003
    pNCs[5].aCrInfo[0].bEnabled=TRUE
    pNCs[5].aCrInfo[0].ftWhenCreated=00000000 00000000
    pNCs[5].aCrInfo[0].pszSDReferenceDomain=(null)
    pNCs[5].aCrInfo[0].pszNetBiosName=(null)
    pNCs[5].aCrInfo[0].cReplicas=-1
    pNCs[5].aCrInfo[0].aszReplicas=
    6 NC TARGETS: TAPI3Directory, ForestDnsZones, DomainDnsZones, Schema,
    Configuration, scps,
    1 TARGETS: PDC-SCPS-2006,
    =============================================Done Printing pDsInfo
    Doing initial required tests
    Testing server: Default-First-Site\PDC-SCPS-2006
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    The host ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan could
    not be resolved to an
    IP address. Check the DNS server, DHCP, server name, etc
    Although the Guid DNS name
    (ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan) couldn't be
    resolved, the server name (PDC-SCPS-2006.scps.lan) resolved to the
    IP
    address (192.168.142.150) and was pingable. Check that the IP
    address
    is registered correctly with the DNS server.
    ......................... PDC-SCPS-2006 failed test Connectivity
    Doing primary tests
    Testing server: Default-First-Site\PDC-SCPS-2006
    Skipping all tests, because server PDC-SCPS-2006 is
    not responding to directory service requests
    DNS Tests are running and not hung. Please wait a few minutes...
    Running partition tests on : TAPI3Directory
    Starting test: CrossRefValidation
    ......................... TAPI3Directory passed test
    CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... TAPI3Directory passed test CheckSDRefDom

    Running partition tests on : ForestDnsZones
    Starting test: CrossRefValidation
    ......................... ForestDnsZones passed test
    CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... ForestDnsZones passed test CheckSDRefDom
    Running partition tests on : DomainDnsZones
    Starting test: CrossRefValidation
    ......................... DomainDnsZones passed test
    CrossRefValidation
    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 : scps
    Starting test: CrossRefValidation
    ......................... scps passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... scps passed test CheckSDRefDom
    Running enterprise tests on : scps.lan
    Starting test: Intersite
    Skipping site Default-First-Site, this site is outside the scope
    provided by the command line arguments provided.
    ......................... scps.lan passed test Intersite
    Starting test: FsmoCheck
    GC Name: \\PDC-SCPS-2006.scps.lan
    Locator Flags: 0xe00003fd
    PDC Name: \\PDC-SCPS-2006.scps.lan
    Locator Flags: 0xe00003fd
    Time Server Name: \\PDC-SCPS-2006.scps.lan
    Locator Flags: 0xe00003fd
    Preferred Time Server Name: \\PDC-SCPS-2006.scps.lan
    Locator Flags: 0xe00003fd
    KDC Name: \\PDC-SCPS-2006.scps.lan
    Locator Flags: 0xe00003fd
    ......................... scps.lan passed test FsmoCheck
    Starting test: DNS
    Test results for domain controllers:
    DC: PDC-SCPS-2006.scps.lan
    Domain: scps.lan
    TEST: Authentication (Auth)
    Authentication test: Successfully completed
    TEST: Basic (Basc)
    Error: No LDAP connectivity
    Microsoft(R) Windows(R) Server 2003, Standard Edition
    (Service Pack level: 1.0) is supported
    NETLOGON service is running
    kdc service is running
    DNSCACHE service is running
    DNS service is running
    DC is a DNS server
    Network adapters information:
    Adapter [00000007] Intel(R) PRO/1000 MT Network
    Connection:
    MAC address is 00:13:72:56:E8:26
    IP address is static
    IP address: 192.168.142.150
    DNS servers:
    192.168.142.150 (pdc-scps-2006.scps.lan.) [Valid]
    The A record for this DC was found
    The SOA record for the Active Directory zone was found
    The Active Directory zone on this DC/DNS server was found
    (primary)
    Root zone on this DC/DNS server was not found
    TEST: Forwarders/Root hints (Forw)
    Recursion is enabled
    Forwarders Information:
    204.101.248.21 (<name unavailable>) [Valid]
    204.101.248.22 (<name unavailable>) [Valid]

    TEST: Delegations (Del)
    Delegation information for the zone: scps.lan.
    Delegated domain name: _msdcs.scps.lan.
    Error: DNS server: pdc-scps-2006.scps.lan.
    IP:192.168.142.150 [Broken delegation]

    TEST: Dynamic update (Dyn)
    Dynamic update is enabled on the zone scps.lan.
    Test record _dcdiag_test_record added successfully in zone
    scps.lan.
    Test record _dcdiag_test_record deleted successfully in
    zone scps.lan.

    TEST: Records registration (RReg)
    Network Adapter [00000007] Intel(R) PRO/1000 MT Network
    Connection:
    Matching A record found at DNS server 192.168.142.150:
    PDC-SCPS-2006.scps.lan

    Error: Missing CNAME record at DNS server
    192.168.142.150 :
    ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan
    [Error details: 9002 (Type: Win32 - Description: DNS
    server failure.)]

    Error: Missing DC SRV record at DNS server
    192.168.142.150 :
    _ldap._tcp.dc._msdcs.scps.lan
    [Error details: 9002 (Type: Win32 - Description: DNS
    server failure.)]

    Error: Missing GC SRV record at DNS server
    192.168.142.150 :
    _ldap._tcp.gc._msdcs.scps.lan
    [Error details: 9002 (Type: Win32 - Description: DNS
    server failure.)]

    Error: Missing PDC SRV record at DNS server
    192.168.142.150 :
    _ldap._tcp.pdc._msdcs.scps.lan
    [Error details: 9002 (Type: Win32 - Description: DNS
    server failure.)]

    Error: Record registrations cannot be found for all the
    network adapters
    Total query time:0 min. 19 sec.. Total RPC connection time:0
    min. 0 sec.
    Total WMI connection time:0 min. 4 sec. Total Netuse
    connection time:0 min. 0 sec.

    Summary of test results for DNS servers used by the above domain
    controllers:

    DNS server: 192.168.142.150 (pdc-scps-2006.scps.lan.)
    1 test failure 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 _msdcs.scps.lan. on the
    DNS server 192.168.142.150
    [Error details: 9002 (Type: Win32 - Description: DNS server
    failure.) - Delegation is broken for the domain _msdcs.scps.lan. on the DNS
    server 192.168.142.150]
    Total query time:0 min. 3 sec., Total WMI connection time:0
    min. 0 sec.

    DNS server: 204.101.248.21 (<name unavailable>)
    All tests passed on this DNS server
    This is a valid DNS server.
    Total query time:0 min. 0 sec., Total WMI connection time:0
    min. 1 sec.

    DNS server: 204.101.248.22 (<name unavailable>)
    All tests passed on this DNS server
    This is a valid DNS server.
    Total query time:0 min. 0 sec., Total WMI connection time:0
    min. 1 sec.

    Summary of DNS test results:

    Auth Basc Forw Del Dyn RReg
    Ext
    ________________________________________________________________
    Domain: scps.lan
    PDC-SCPS-2006 PASS FAIL PASS FAIL PASS FAIL
    n/a

    Total Time taken to test all the DCs:0 min. 24 sec.
    ......................... scps.lan failed test DNS
     
    Thom Paine, Feb 7, 2007
    #17
  18. Thom Paine

    Thom Paine Guest

    [ You confused the issue by bringing up your 2000 Server a few
    Yes, I brought it up because I was comparing the old server setup to the new
    server setup. Sorry about that.

    It is AD Integrated. Set to Secure Updates only.
    I let the wizard set it up.
    Yes, I have been dumping these to a text file and reading them and copy
    pasting the information form them.

    Thanks.
     
    Thom Paine, Feb 7, 2007
    #18
  19. Thom Paine

    Thom Paine Guest

    What if I just stop the service, delete the DNS, and reinstall and start it
    over? Would that be easier at this point?

    Thanks.
     
    Thom Paine, Feb 7, 2007
    #19
  20. Thom Paine

    Herb Martin Guest

    But we still haven't fixed it, right?

    The last two messages I have asked you to re-rerun netdiag /fix and
    the dcdiag but you aren't giving clear indications that this is being done.

    (Yes, I know it is "implied" but when you have a TOUGH problem
    everything must be EXPLICIT. Yesterday I asked a guy to check
    something four times, he even said he did, and then it turned out he
    had done it backwards from what he claimed.)

    Notice that NetDIAG /fix is NOT the same as DCDiag /fix (for
    reasons I cannot imagine.)

    I don't recommend rebooting very often but you might try that too.

    Next will be a "repair Install". So check everything twice more
    around then get the original CDRom and to a repair install.

    Do a system state backup first. NTBackup can do this.

    That is a regular install but ensure you get the prompt to put the
    OS in the same directory AND REPAIR. Confirm that and do
    NOT stop that install half-way through.
     
    Herb Martin, Feb 7, 2007
    #20
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.