DCDiag GUID Error

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

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.



>>> Your DC is not properly registered in DNS.
>>>
>>> Show me the IPConfig /all from each DC.
>>
>> 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
>>
>>
>>>
>>> Check the _msdcs zone to make sure all DCs can resolve from it.
>> I'm not sure how to check this since we only have one server.
>
> Is _MSDCS a separate zone or not (previous messages were unclear on
> this point)?
>
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?

> If separate is it DYNAMIC?
>
>>> Check that it is dynamic.
>>> Check that all DCs can find the "primary" (Master) and register
>>> themselves
>>> in that zone.
>>>
>> 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.
>
> As a new domain or did you join it to an older domain before removing your
> old DC?
>

As a new domain. I migrated data with a thumbdrive since there was so
little.

>>> After all this is correct, run "Netdiag /fix" or restart NetLogon
>>> service,
>>> and then retry DCDiag /C /D on every DC.
>>
>> Thanks Herb. I appreciate all this help.
>
> Did it work yet?
>
>
>

"Thom Paine" <painethom@hotmail.com> wrote in message
news:%230MX2luSHHA.412@TK2MSFTNGP02.phx.gbl...

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

[ You confused the issue by bringing up your 2000 Server a few
messages back in this thread. ]

>>>> Your DC is not properly registered in DNS.


>>> There is only one DC.
>>> Windows IP Configuration
>>> Host Name . . . . . . . . . . . . : PDC-SCPS-2006
>>> Primary Dns Suffix . . . . . . . : scps.lan
>>> 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

>>>> Check the _msdcs zone to make sure all DCs can resolve from it.
>>> I'm not sure how to check this since we only have one server.
>>
>> Is _MSDCS a separate zone or not (previous messages were unclear on
>> this point)?

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

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

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

>>> 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.
> As a new domain. I migrated data with a thumbdrive since there was so
> little.

Did you setup DNS yourself or just let the DCPromo do that?

>>>> After all this is correct, run "Netdiag /fix" or restart NetLogon
>>>> service, and then retry DCDiag /C /D on every DC.
>>>
>>> Thanks Herb. I appreciate all this help.
>>
>> Did it work yet?

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, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)

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

> [ You confused the issue by bringing up your 2000 Server a few
> messages back in this thread. ]
>

Yes, I brought it up because I was comparing the old server setup to the new
server setup. Sorry about that.


>>>>> Your DC is not properly registered in DNS.
>
>
>>>> There is only one DC.
>>>> Windows IP Configuration
>>>> Host Name . . . . . . . . . . . . : PDC-SCPS-2006
>>>> Primary Dns Suffix . . . . . . . : scps.lan
>>>> 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
>
>>>>> Check the _msdcs zone to make sure all DCs can resolve from it.
>>>> I'm not sure how to check this since we only have one server.
>>>
>>> Is _MSDCS a separate zone or not (previous messages were unclear on
>>> this point)?
>
>> 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?
>
> 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.)
>

It is AD Integrated. Set to Secure Updates only.

>>>>> Check that it is dynamic.
>>>>> Check that all DCs can find the "primary" (Master) and register
>>>>> themselves in that zone.
>
>>>> 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.
>> As a new domain. I migrated data with a thumbdrive since there was so
>> little.
>
> Did you setup DNS yourself or just let the DCPromo do that?

I let the wizard set it up.

>
>>>>> After all this is correct, run "Netdiag /fix" or restart NetLogon
>>>>> service, and then retry DCDiag /C /D on every DC.
>>>>
>>>> Thanks Herb. I appreciate all this help.
>>>
>>> Did it work yet?
>
> 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.
>

Yes, I have been dumping these to a text file and reading them and copy
pasting the information form them.

Thanks.

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" <painethom@hotmail.com> wrote in message
news:OAm6I9uSHHA.4028@TK2MSFTNGP02.phx.gbl...
>> [ You confused the issue by bringing up your 2000 Server a few
>> messages back in this thread. ]

>>
>> 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.
>>
>
> Yes, I have been dumping these to a text file and reading them and copy
> pasting the information form them.
>
> Thanks.

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

>> Run NetDiag /Fix (again after each change).
>> Then check (each time) DCDiag /c /d tell you now?

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, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)

"Thom Paine" <painethom@hotmail.com> wrote in message
news:OkSB5HvSHHA.4764@TK2MSFTNGP05.phx.gbl...
> What if I just stop the service, delete the DNS, and reinstall and start
> it over? Would that be easier at this point?

Not particularly. If you DNS is right, it is right. If you re-install it
then
you are likely to do it wrong -- best you could do is get it back right
again.

"Thom Paine" <painethom@hotmail.com> wrote in message
news:%23oyOq2uSHHA.2212@TK2MSFTNGP02.phx.gbl...
> Here is the output from netdiag /fix and dcdiag /C /D.

Changed my mind -- you DNS service is giving fatal errors.

Go ahead and uninstall the DNS service, add it back, create the
zone (Primary + Dynamic).

Repeat NetDiag /fix and DCDiag /c /d

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)

I think that has it fixed.

I had to remove DNS, then reinstall it, but I got a 'zone already exists'.
So I deleted the zone, and then started the zone wizard.

Here is a dump of dcdiag /C /D.

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 = 20070207204212.0Z
PDC-SCPS-2006.highestCommittedUSN = 246472
PDC-SCPS-2006.isSynchronized = 1
PDC-SCPS-2006.isGlobalCatalogReady = 1
* Collecting site info.
* Identifying all servers.
PDC-SCPS-2006.currentTime = 20070207204212.0Z
PDC-SCPS-2006.highestCommittedUSN = 246472
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=71eef8e0 01c74af8

pServer[0].ftRemoteConnectTime=71816a00 01c74af8

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
Failure Analysis: PDC-SCPS-2006 ... OK.
* Active Directory RPC Services Check
......................... PDC-SCPS-2006 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site\PDC-SCPS-2006
Starting test: Replications
* Replications Check
DC=TAPI3Directory,DC=scps,DC=lan has 1 cursors.
DC=ForestDnsZones,DC=scps,DC=lan has 1 cursors.
DC=DomainDnsZones,DC=scps,DC=lan has 1 cursors.
CN=Schema,CN=Configuration,DC=scps,DC=lan has 1 cursors.
CN=Configuration,DC=scps,DC=lan has 1 cursors.
DC=scps,DC=lan has 1 cursors.
* Replication Latency Check
* Replication Site Latency Check
Site Settings = CN=NTDS Site
Settings,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=scps,DC=lan
[0x904de,v=7066,t=2007-02-07
15:23:06,g=ef255104-5591-4517-af81-393e31ac9dcf,orig=246316,local=246316]
Elapsed time (sec) = 1146
......................... PDC-SCPS-2006 passed test Replications
Starting test: Topology
* Configuration Topology Integrity Check
* Analyzing the connection topology for
DC=TAPI3Directory,DC=scps,DC=lan.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for
DC=ForestDnsZones,DC=scps,DC=lan.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for
DC=DomainDnsZones,DC=scps,DC=lan.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for
CN=Schema,CN=Configuration,DC=scps,DC=lan.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for
CN=Configuration,DC=scps,DC=lan.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for DC=scps,DC=lan.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... PDC-SCPS-2006 passed test Topology
Starting test: CutoffServers
* Configuration Topology Aliveness Check
* Analyzing the alive system replication topology for
DC=TAPI3Directory,DC=scps,DC=lan.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for
DC=ForestDnsZones,DC=scps,DC=lan.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for
DC=DomainDnsZones,DC=scps,DC=lan.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for
CN=Schema,CN=Configuration,DC=scps,DC=lan.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for
CN=Configuration,DC=scps,DC=lan.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for
DC=scps,DC=lan.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... PDC-SCPS-2006 passed test CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC PDC-SCPS-2006.
* Security Permissions Check for
DC=TAPI3Directory,DC=scps,DC=lan
(NDNC,Version 2)
* Security Permissions Check for
DC=ForestDnsZones,DC=scps,DC=lan
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=scps,DC=lan
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=scps,DC=lan
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=scps,DC=lan
(Configuration,Version 2)
* Security Permissions Check for
DC=scps,DC=lan
(Domain,Version 2)
......................... PDC-SCPS-2006 passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\PDC-SCPS-2006\netlogon
Verified share \\PDC-SCPS-2006\sysvol
......................... PDC-SCPS-2006 passed test NetLogons
Starting test: Advertising
The DC PDC-SCPS-2006 is advertising itself as a DC and having a DS.
The DC PDC-SCPS-2006 is advertising as an LDAP server
The DC PDC-SCPS-2006 is advertising as having a writeable directory
The DC PDC-SCPS-2006 is advertising as a Key Distribution Center
The DC PDC-SCPS-2006 is advertising as a time server
The DS PDC-SCPS-2006 is advertising as a GC.
......................... PDC-SCPS-2006 passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=PDC-SCPS-2006,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=scps,DC=lan
Role Domain Owner = CN=NTDS
Settings,CN=PDC-SCPS-2006,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=scps,DC=lan
Role PDC Owner = CN=NTDS
Settings,CN=PDC-SCPS-2006,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=scps,DC=lan
Role Rid Owner = CN=NTDS
Settings,CN=PDC-SCPS-2006,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=scps,DC=lan
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=PDC-SCPS-2006,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=scps,DC=lan
......................... PDC-SCPS-2006 passed test
KnowsOfRoleHolders
Starting test: RidManager
ridManagerReference = CN=RID Manager$,CN=System,DC=scps,DC=lan
* Available RID Pool for the Domain is 1603 to 1073741823
fSMORoleOwner = CN=NTDS
Settings,CN=PDC-SCPS-2006,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=scps,DC=lan
* PDC-SCPS-2006.scps.lan is the RID Master
* DsBind with RID Master was successful
rIDSetReferences = CN=RID Set,CN=PDC-SCPS-2006,OU=Domain
Controllers,DC=scps,DC=lan
* rIDAllocationPool is 1103 to 1602
* rIDPreviousAllocationPool is 1103 to 1602
* rIDNextRID: 1225
......................... PDC-SCPS-2006 passed test RidManager
Starting test: MachineAccount
Checking machine account for DC PDC-SCPS-2006 on DC PDC-SCPS-2006.
* SPN found :LDAP/PDC-SCPS-2006.scps.lan/scps.lan
* SPN found :LDAP/PDC-SCPS-2006.scps.lan
* SPN found :LDAP/PDC-SCPS-2006
* SPN found :LDAP/PDC-SCPS-2006.scps.lan/SCPS
* SPN found
:LDAP/ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/ef255104-5591-4517-af81-393e31ac9dcf/scps.lan
* SPN found :HOST/PDC-SCPS-2006.scps.lan/scps.lan
* SPN found :HOST/PDC-SCPS-2006.scps.lan
* SPN found :HOST/PDC-SCPS-2006
* SPN found :HOST/PDC-SCPS-2006.scps.lan/SCPS
* SPN found :GC/PDC-SCPS-2006.scps.lan/scps.lan
......................... PDC-SCPS-2006 passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... PDC-SCPS-2006 passed test Services
Starting test: OutboundSecureChannels
* The Outbound Secure Channels test
** Did not run Outbound Secure Channels test
because /testdomain: was not entered
......................... PDC-SCPS-2006 passed test
OutboundSecureChannels
Starting test: ObjectsReplicated
PDC-SCPS-2006 is in domain DC=scps,DC=lan
Checking for CN=PDC-SCPS-2006,OU=Domain Controllers,DC=scps,DC=lan
in domain DC=scps,DC=lan on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=PDC-SCPS-2006,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=scps,DC=lan
in domain CN=Configuration,DC=scps,DC=lan on 1 servers
Object is up-to-date on all servers.
......................... PDC-SCPS-2006 passed test
ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... PDC-SCPS-2006 passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... PDC-SCPS-2006 passed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15
minutes.
......................... PDC-SCPS-2006 passed test kccevent
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/07/2007 14:43:42
Event String: The dynamic registration of the DNS record

'_ldap._tcp.gc._msdcs.scps.lan. 600 IN SRV 0 100 3268
PDC-SCPS-2006.scps.lan.'

failed on the following DNS server:



DNS server IP address: <UNAVAILABLE>

Returned Response Code (RCODE): 0

Returned Status Code: 0



For computers and users to locate this domain

controller, this record must be registered in

DNS.



USER ACTION

Determine what might have caused this failure,

resolve the problem, and initiate registration of

the DNS records by the domain controller. To

determine what might have caused this failure,

run DCDiag.exe. You can find this program on the

Windows Server 2003 installation CD in

Support\Tools\support.cab. To learn more about

DCDiag.exe, see Help and Support Center. To

initiate registration of the DNS records by this

domain controller, run 'nltest.exe /dsregdns'

from the command prompt on the domain controller

or restart Net Logon service. Nltest.exe is

available in the Microsoft Windows Server

Resource Kit CD.

Or, you can manually add this record to DNS,

but it is not recommended.



ADDITIONAL DATA

Error Value: %%4294967196
......................... PDC-SCPS-2006 failed test systemlog
Starting test: VerifyReplicas
......................... PDC-SCPS-2006 passed test VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)

CN=PDC-SCPS-2006,OU=Domain Controllers,DC=scps,DC=lan and backlink
on

CN=PDC-SCPS-2006,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=scps,DC=lan

are correct.
The system object reference (frsComputerReferenceBL)

CN=PDC-SCPS-2006,CN=Domain System Volume (SYSVOL share),CN=File
Replication Service,CN=System,DC=scps,DC=lan

and backlink on CN=PDC-SCPS-2006,OU=Domain
Controllers,DC=scps,DC=lan

are correct.
The system object reference (serverReferenceBL)

CN=PDC-SCPS-2006,CN=Domain System Volume (SYSVOL share),CN=File
Replication Service,CN=System,DC=scps,DC=lan

and backlink on

CN=NTDS
Settings,CN=PDC-SCPS-2006,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=scps,DC=lan

are correct.
......................... PDC-SCPS-2006 passed test
VerifyReferences
Starting test: VerifyEnterpriseReferences
......................... PDC-SCPS-2006 passed test
VerifyEnterpriseReferences
Starting test: CheckSecurityError
* Dr Auth: Beginning security errors check!
Found KDC PDC-SCPS-2006 for domain scps.lan in site
Default-First-Site
Checking machine account for DC PDC-SCPS-2006 on DC PDC-SCPS-2006.
* SPN found :LDAP/PDC-SCPS-2006.scps.lan/scps.lan
* SPN found :LDAP/PDC-SCPS-2006.scps.lan
* SPN found :LDAP/PDC-SCPS-2006
* SPN found :LDAP/PDC-SCPS-2006.scps.lan/SCPS
* SPN found
:LDAP/ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/ef255104-5591-4517-af81-393e31ac9dcf/scps.lan
* SPN found :HOST/PDC-SCPS-2006.scps.lan/scps.lan
* SPN found :HOST/PDC-SCPS-2006.scps.lan
* SPN found :HOST/PDC-SCPS-2006
* SPN found :HOST/PDC-SCPS-2006.scps.lan/SCPS
* SPN found :GC/PDC-SCPS-2006.scps.lan/scps.lan
[PDC-SCPS-2006] No security related replication errors were found
on this DC! To target the connection to a specific source DC use
/ReplSource:<DC>.
......................... PDC-SCPS-2006 passed test
CheckSecurityError

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)
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 (<name unavailable>) [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 are not configured on this DNS server
Root hint Information:
Name: a.root-servers.net. IP: 198.41.0.4 [Invalid]
Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
Name: c.root-servers.net. IP: 192.33.4.12 [Invalid]
Name: d.root-servers.net. IP: 128.8.10.90 [Invalid]
Name: e.root-servers.net. IP: 192.203.230.10 [Invalid]
Name: f.root-servers.net. IP: 192.5.5.241 [Invalid]
Name: g.root-servers.net. IP: 192.112.36.4 [Invalid]
Name: h.root-servers.net. IP: 128.63.2.53 [Invalid]
Name: i.root-servers.net. IP: 192.36.148.17 [Invalid]
Name: j.root-servers.net. IP: 192.58.128.30 [Invalid]
Name: k.root-servers.net. IP: 193.0.14.129 [Invalid]
Name: l.root-servers.net. IP: 198.32.64.12 [Invalid]
Name: m.root-servers.net. IP: 202.12.27.33 [Invalid]

TEST: Delegations (Del)
No delegations were found in this zone on this DNS server

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

Matching CNAME record found at DNS server
192.168.142.150:
ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan

Matching DC SRV record found at DNS server
192.168.142.150:
_ldap._tcp.dc._msdcs.scps.lan

Matching GC SRV record found at DNS server
192.168.142.150:
_ldap._tcp.gc._msdcs.scps.lan

Matching PDC SRV record found at DNS server
192.168.142.150:
_ldap._tcp.pdc._msdcs.scps.lan

Total query time:0 min. 1 sec.. Total RPC connection time:0
min. 0 sec.
Total WMI connection time:0 min. 0 sec. Total Netuse
connection time:0 min. 0 sec.

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
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 128.63.2.53
[Error details: 9003 (Type: Win32 - Description: DNS name
does not exist.)]
Total query time:0 min. 0 sec., Total WMI connection time:0
min. 0 sec.

DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90
[Error details: 9003 (Type: Win32 - Description: DNS name
does not exist.)]
Total query time:0 min. 0 sec., Total WMI connection time:0
min. 0 sec.

DNS server: 192.112.36.4 (g.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 192.112.36.4
[Error details: 9002 (Type: Win32 - Description: DNS server
failure.)]
Total query time:0 min. 0 sec., Total WMI connection time:0
min. 0 sec.

DNS server: 192.203.230.10 (e.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 192.203.230.10
[Error details: 9003 (Type: Win32 - Description: DNS name
does not exist.)]
Total query time:0 min. 0 sec., Total WMI connection time:0
min. 0 sec.

DNS server: 192.33.4.12 (c.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 192.33.4.12
[Error details: 9003 (Type: Win32 - Description: DNS name
does not exist.)]
Total query time:0 min. 0 sec., Total WMI connection time:0
min. 0 sec.

DNS server: 192.36.148.17 (i.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 192.36.148.17
[Error details: 9003 (Type: Win32 - Description: DNS name
does not exist.)]
Total query time:0 min. 0 sec., Total WMI connection time:0
min. 0 sec.

DNS server: 192.5.5.241 (f.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 192.5.5.241
[Error details: 9003 (Type: Win32 - Description: DNS name
does not exist.)]
Total query time:0 min. 0 sec., Total WMI connection time:0
min. 0 sec.

DNS server: 192.58.128.30 (j.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 192.58.128.30
[Error details: 9002 (Type: Win32 - Description: DNS server
failure.)]
Total query time:0 min. 0 sec., Total WMI connection time:0
min. 0 sec.

DNS server: 193.0.14.129 (k.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 193.0.14.129
[Error details: 9003 (Type: Win32 - Description: DNS name
does not exist.)]
Total query time:0 min. 0 sec., Total WMI connection time:0
min. 0 sec.

DNS server: 198.32.64.12 (l.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 198.32.64.12
[Error details: 9002 (Type: Win32 - Description: DNS server
failure.)]
Total query time:0 min. 0 sec., Total WMI connection time:0
min. 0 sec.

DNS server: 198.41.0.4 (a.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 198.41.0.4
[Error details: 9003 (Type: Win32 - Description: DNS name
does not exist.)]
Total query time:0 min. 0 sec., Total WMI connection time:0
min. 0 sec.

DNS server: 202.12.27.33 (m.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 202.12.27.33
[Error details: 9003 (Type: Win32 - Description: DNS name
does not exist.)]
Total query time:0 min. 0 sec., Total WMI connection time:0
min. 0 sec.

DNS server: 192.168.142.150 (<name unavailable>)
All tests passed 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
Total query time:0 min. 0 sec., Total WMI connection time:0
min. 0 sec.

DNS server: 192.228.79.201 (b.root-servers.net.)
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. 0 sec.

Summary of DNS test results:

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

Total Time taken to test all the DCs:0 min. 1 sec.
......................... scps.lan passed test DNS

"Thom Paine" <painethom@hotmail.com> wrote in message
news:uZdUGkvSHHA.4252@TK2MSFTNGP05.phx.gbl...
>I think that has it fixed.
>
> I had to remove DNS, then reinstall it, but I got a 'zone already exists'.
> So I deleted the zone, and then started the zone wizard.
>
> Here is a dump of dcdiag /C /D.
>
> Command Line: "dcdiag.exe /C /D"


You didn't delete the zone (or convert it to primary) so it is still in AD.

AD Integrated Zones are stored in AD on the DC.

Does the zone now exist?

What DNS(NS records) are listed in this zone (hint: sort by record
type).

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)

Thom Paine wrote:
> Here is a screnshot of my dns. Maybe that will help.
>

I can see exactly what the problem is, the _msdcs sub zone is actually a
delegation (it is supposed to be a delegation) and the _msdcs.scps.lan zone
does not exist, (at least on this server), did you delete this zone?

Click on the _msdcs subzone, it should show NS records in the right hand
pane of all DNS server with the full _msdcs.scps.lan zone, and make sure the
zone exists on all servers with NS records in the delegation. Now, since
this is a Win2k3 DNS it (the _msdcs.scps.lan zone) should be on this server,
and there should be an NS record for it.

Create a new forward lookup zone named _msdcs.scps.lan stored in AD, and
allow dynamic updates. run dcdiag /fix and netdiag /fix and make sure the NS
record for this server gets created in the delegation.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
Send IM: http://www.icq.com/people/webmsg.php?to=296095728
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

Thom Paine wrote:
> Here is a screnshot of my dns. Maybe that will help.

You did not post the second image in the doc but it has a link in the next
post.
OK, it has the NS record for this server, all you need to do is create the
forward lookup zone named "_msdcs.scps.lan" and run dciag /fix and netdiag
/fix. You might through in a ipconfig /flushdns before these commands

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
Send IM: http://www.icq.com/people/webmsg.php?to=296095728
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

Here is a screenshot of the dns screen.

http://i160.photobucket.com/albums/t.../dns-fixed.jpg

Thanks Herb for all your assistance.

-=/>Thom

"Thom Paine" <painethom@hotmail.com> wrote in message
news:%23vFDZ94SHHA.3316@TK2MSFTNGP02.phx.gbl...
> Here is a screenshot of the dns screen.
>
> http://i160.photobucket.com/albums/t.../dns-fixed.jpg
>
> Thanks Herb for all your assistance.

Ok, but I can only see that generally you have the _underscore subdomains.