SceCli 1202 0x534 events...but accounts not resolving to SIDs aren't missing/mistyped!

Question

I have two DCs in a small WS2012R2 AD setup. My DCs are throwing event 1202s (lots of them), complaining that during GPO processing some accounts aren't resolving to SIDs.
When I issue a "FIND /I "Cannot find" %SYSTEMROOT%\Security\Logs\winlogon.log" message (after enabling that log via registry) and investigate which accounts aren't resolving, the users in question are not "missing accounts"
or "mistyped" as all of the troubleshooting docs I've seen suggest. Rather, the accounts in question are central, primary accounts that emphatically DO exist:
"C:\Users\Administrator.AD>FIND /I "Cannot find" %SYSTEMROOT%\Security\Logs\winl
ogon.log
---------- C:\WINDOWS\SECURITY\LOGS\WINLOGON.LOG
Warning 2: The system cannot find the file specified.
Cannot find Administrators.
Warning 2: The system cannot find the file specified.
Cannot find AD\Domain Admins.
Cannot find AD\Enterprise Admins.
Warning 2: The system cannot find the file specified.
Cannot find Administrators.
Warning 2: The system cannot find the file specified.
Cannot find AD\Domain Admins.
Cannot find AD\Enterprise Admins.
Warning 2: The system cannot find the file specified.
Cannot find Administrators.
Warning 2: The system cannot find the file specified.
Cannot find AD\Domain Admins.
Cannot find AD\Enterprise Admins.
Warning 2: The system cannot find the file specified.
Cannot find Administrators.
Warning 2: The system cannot find the file specified.
Cannot find AD\Domain Admins.
Cannot find AD\Enterprise Admins.
Warning 2: The system cannot find the file specified.
Cannot find Administrators.
Cannot find AD\Domain Admins.
Cannot find AD\Enterprise Admins.
Warning 2: The system cannot find the file specified.
Cannot find Administrators.
Cannot find AD\Domain Admins.
Cannot find AD\Enterprise Admins.
Warning 2: The system cannot find the file specified.
Cannot find Administrators.
Cannot find AD\Domain Admins.
Cannot find AD\Enterprise Admins.
Warning 2: The system cannot find the file specified.
Cannot find Administrators.
Cannot find AD\Domain Admins.
Cannot find AD\Enterprise Admins.
Warning 2: The system cannot find the file specified.
Cannot find Administrators.
Cannot find AD\Domain Admins.
Cannot find AD\Enterprise Admins.
Warning 2: The system cannot find the file specified.
Cannot find Administrators.
Cannot find AD\Domain Admins.
Cannot find AD\Enterprise Admins.
Warning 2: The system cannot find the file specified.
Cannot find Administrators.
Cannot find AD\Domain Admins.
Cannot find AD\Enterprise Admins.
Warning 2: The system cannot find the file specified.
Cannot find Administrators.
Cannot find AD\Domain Admins.
Cannot find AD\Enterprise Admins.
Warning 2: The system cannot find the file specified.
Cannot find Administrators.
Cannot find AD\Domain Admins.
Cannot find AD\Enterprise Admins."
Clearly, all of those accounts do exist. There are no apparent problems with AD replication, DNS, and I am confident that the GPOs that are set up are proper, and aren't doing much at all: I've got a policy enabling local admins, another specifying updates
behavior, etc. Nothing weird.
Clearly there is a real problem, but it's confusing and I could use some guidance.

Answer 1

Update:
When reviewing GPOs for possible issues, I'm experiencing something I've not seen before: selecting domain user groups for inclusion in a GPO, I get the message "specified domain either does not exist or could not be contacted." 
This is occurring on the primary DC itself.
SYSVOL and NETLOGON both exist as shares from both DCs.
I am pasting dcdiag /c /v /test:dns /dnsall below. Note that the DFSR issue noted by dcidag is from an earlier reboot, and shouldn't be an issue. There is the obviously concerning "The system cannot find the file specified." in the "Query
Trusted Domain" test. There is also a " Root zone on this DC/DNS server was not found" that is obviously an issue. Need assistance in remedying, clearly. Beating head against wall.
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
* Verifying that the local machine Johnson, is a Directory Server.
Home Server = Johnson
* Connecting to directory service on server Johnson.
* Identified AD Forest.
Collecting AD specific global data
* Collecting site info.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
The previous call succeeded
Iterating through the sites
Looking at base site object: CN=NTDS Site Settings,CN=FISKE-MAIN,CN=Sites,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
Getting ISTG and options for the site
* Identifying all servers.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
The previous call succeeded....
The previous call succeeded
Iterating through the list of servers
Getting information for the server CN=NTDS Settings,CN=JOHNSON,CN=Servers,CN=FISKE-MAIN,CN=Sites,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
Getting information for the server CN=NTDS Settings,CN=KENNEDY,CN=Servers,CN=FISKE-MAIN,CN=Sites,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: FISKE-MAIN\JOHNSON
Starting test: Connectivity
* Active Directory LDAP Services Check
Determining IP4 connectivity
* Active Directory RPC Services Check
......................... JOHNSON passed test Connectivity
Doing primary tests
Testing server: FISKE-MAIN\JOHNSON
Starting test: Advertising
The DC JOHNSON is advertising itself as a DC and having a DS.
The DC JOHNSON is advertising as an LDAP server
The DC JOHNSON is advertising as having a writeable directory
The DC JOHNSON is advertising as a Key Distribution Center
The DC JOHNSON is advertising as a time server
The DS JOHNSON is advertising as a GC.
......................... JOHNSON passed test Advertising
Starting test: CheckSecurityError
* Dr Auth: Beginning security errors check!
Found KDC JOHNSON for domain ad.fiske.colorado.edu in site FISKE-MAIN
Checking machine account for DC JOHNSON on DC JOHNSON.
* SPN found :LDAP/Johnson.ad.fiske.colorado.edu/ad.fiske.colorado.edu
* SPN found :LDAP/Johnson.ad.fiske.colorado.edu
* SPN found :LDAP/JOHNSON
* SPN found :LDAP/Johnson.ad.fiske.colorado.edu/AD
* SPN found :LDAP/76a8cdf6-3de8-4cfe-8c00-a73691ed59ae._msdcs.ad.fiske.colorado.edu
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/76a8cdf6-3de8-4cfe-8c00-a73691ed59ae/ad.fiske.colorado.edu
* SPN found :HOST/Johnson.ad.fiske.colorado.edu/ad.fiske.colorado.edu
* SPN found :HOST/Johnson.ad.fiske.colorado.edu
* SPN found :HOST/JOHNSON
* SPN found :HOST/Johnson.ad.fiske.colorado.edu/AD
* SPN found :GC/Johnson.ad.fiske.colorado.edu/ad.fiske.colorado.edu
[JOHNSON] No security related replication errors were found on this
DC! To target the connection to a specific source DC use
/ReplSource:<DC>.
......................... JOHNSON passed test CheckSecurityError
Starting test: CutoffServers
* Configuration Topology Aliveness Check
* Analyzing the alive system replication topology for DC=ForestDnsZones,DC=ad,DC=fiske,DC=colorado,DC=edu.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for DC=DomainDnsZones,DC=ad,DC=fiske,DC=colorado,DC=edu.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for DC=ad,DC=fiske,DC=colorado,DC=edu.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... JOHNSON passed test CutoffServers
Starting test: FrsEvent
* The File Replication Service Event log test
Skip the test because the server is running DFSR.
......................... JOHNSON passed test FrsEvent
Starting test: DFSREvent
The DFS Replication Event Log.
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
A warning event occurred. EventID: 0x80001396
Time Generated: 04/02/2015 04:30:20
Event String:
The DFS Replication service is stopping communication with partner KENNEDY for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: AF82B734-65B3-4FE3-A99F-A1AD85BB51E3
Replication Group ID: 400916F0-03E9-4311-AA01-26F1BF190DDD
A warning event occurred. EventID: 0x800008A4
Time Generated: 04/02/2015 09:38:05
Event String:
The DFS Replication service has detected an unexpected shutdown on volume C:. This can occur if the service terminated abnormally (due to a power loss, for example) or an error occurred on the volume. The service has automatically initiated a recovery process.
The service will rebuild the database if it determines it cannot reliably recover. No user action is required.
Additional Information:
Volume: C:
GUID: AA62886D-CDBD-11E4-80B5-806E6F6E6963
......................... JOHNSON passed test DFSREvent
Starting test: SysVolCheck
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... JOHNSON passed test SysVolCheck
Starting test: FrsSysVol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... JOHNSON passed test FrsSysVol
Starting test: KccEvent
* The KCC Event log test
Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
......................... JOHNSON passed test KccEvent
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=JOHNSON,CN=Servers,CN=FISKE-MAIN,CN=Sites,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
Role Domain Owner = CN=NTDS Settings,CN=JOHNSON,CN=Servers,CN=FISKE-MAIN,CN=Sites,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
Role PDC Owner = CN=NTDS Settings,CN=JOHNSON,CN=Servers,CN=FISKE-MAIN,CN=Sites,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
Role Rid Owner = CN=NTDS Settings,CN=JOHNSON,CN=Servers,CN=FISKE-MAIN,CN=Sites,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
Role Infrastructure Update Owner = CN=NTDS Settings,CN=JOHNSON,CN=Servers,CN=FISKE-MAIN,CN=Sites,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
......................... JOHNSON passed test KnowsOfRoleHolders
Starting test: MachineAccount
Checking machine account for DC JOHNSON on DC JOHNSON.
* SPN found :LDAP/Johnson.ad.fiske.colorado.edu/ad.fiske.colorado.edu
* SPN found :LDAP/Johnson.ad.fiske.colorado.edu
* SPN found :LDAP/JOHNSON
* SPN found :LDAP/Johnson.ad.fiske.colorado.edu/AD
* SPN found :LDAP/76a8cdf6-3de8-4cfe-8c00-a73691ed59ae._msdcs.ad.fiske.colorado.edu
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/76a8cdf6-3de8-4cfe-8c00-a73691ed59ae/ad.fiske.colorado.edu
* SPN found :HOST/Johnson.ad.fiske.colorado.edu/ad.fiske.colorado.edu
* SPN found :HOST/Johnson.ad.fiske.colorado.edu
* SPN found :HOST/JOHNSON
* SPN found :HOST/Johnson.ad.fiske.colorado.edu/AD
* SPN found :GC/Johnson.ad.fiske.colorado.edu/ad.fiske.colorado.edu
......................... JOHNSON passed test MachineAccount
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC JOHNSON.
* Security Permissions Check for
DC=ForestDnsZones,DC=ad,DC=fiske,DC=colorado,DC=edu
(NDNC,Version 3)
* Security Permissions Check for
DC=DomainDnsZones,DC=ad,DC=fiske,DC=colorado,DC=edu
(NDNC,Version 3)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
(Schema,Version 3)
* Security Permissions Check for
CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
(Configuration,Version 3)
* Security Permissions Check for
DC=ad,DC=fiske,DC=colorado,DC=edu
(Domain,Version 3)
......................... JOHNSON passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\JOHNSON\netlogon
Verified share \\JOHNSON\sysvol
......................... JOHNSON passed test NetLogons
Starting test: ObjectsReplicated
JOHNSON is in domain DC=ad,DC=fiske,DC=colorado,DC=edu
Checking for CN=JOHNSON,OU=Domain Controllers,DC=ad,DC=fiske,DC=colorado,DC=edu in domain DC=ad,DC=fiske,DC=colorado,DC=edu on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=JOHNSON,CN=Servers,CN=FISKE-MAIN,CN=Sites,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu in domain CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu on 1 servers
Object is up-to-date on all servers.
......................... JOHNSON passed test ObjectsReplicated
Starting test: OutboundSecureChannels
* The Outbound Secure Channels test
The server JOHNSON is the PDC for the ad.fiske.colorado.edu domain. It
is not supposed to have a secure channel to this domain. The test is
skipped.
* Secure channel from [KENNEDY] to [\\Johnson.ad.fiske.colorado.edu] is working properly.
Could not Query Trusted Domain [ad.fiske.colorado.edu]: error 0x2
"The system cannot find the file specified."
......................... JOHNSON passed test OutboundSecureChannels
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=ForestDnsZones,DC=ad,DC=fiske,DC=colorado,DC=edu
Latency information for 3 entries in the vector were ignored.
3 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=DomainDnsZones,DC=ad,DC=fiske,DC=colorado,DC=edu
Latency information for 4 entries in the vector were ignored.
4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Schema,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
Latency information for 3 entries in the vector were ignored.
3 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
Latency information for 3 entries in the vector were ignored.
3 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=ad,DC=fiske,DC=colorado,DC=edu
Latency information for 4 entries in the vector were ignored.
4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
......................... JOHNSON passed test Replications
Starting test: RidManager
* Available RID Pool for the Domain is 14101 to 1073741823
* Johnson.ad.fiske.colorado.edu is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 12101 to 12600
* rIDPreviousAllocationPool is 12101 to 12600
* rIDNextRID: 12146
......................... JOHNSON passed test RidManager
Starting test: Services
* Checking Service: EventSystem
* Checking Service: RpcSs
* Checking Service: NTDS
* Checking Service: DnsCache
* Checking Service: DFSR
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: w32time
* Checking Service: NETLOGON
......................... JOHNSON passed test Services
Starting test: SystemLog
* The System Event log test
An error event occurred. EventID: 0x0000272C
Time Generated: 04/02/2015 12:29:10
Event String:
DCOM was unable to communicate with the computer 128.138.129.76 using any of the configured protocols; requested by PID 1458 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 04/02/2015 12:29:31
Event String:
DCOM was unable to communicate with the computer 128.138.130.30 using any of the configured protocols; requested by PID 1458 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 04/02/2015 12:29:52
Event String:
DCOM was unable to communicate with the computer 128.138.240.1 using any of the configured protocols; requested by PID 1458 (C:\Windows\system32\dcdiag.exe).
......................... JOHNSON failed test SystemLog
Starting test: Topology
* Configuration Topology Integrity Check
* Analyzing the connection topology for DC=ForestDnsZones,DC=ad,DC=fiske,DC=colorado,DC=edu.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for DC=DomainDnsZones,DC=ad,DC=fiske,DC=colorado,DC=edu.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for CN=Schema,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for DC=ad,DC=fiske,DC=colorado,DC=edu.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... JOHNSON passed test Topology
Starting test: VerifyEnterpriseReferences
......................... JOHNSON passed test
VerifyEnterpriseReferences
Starting test: VerifyReferences
The system object reference (serverReference)
CN=JOHNSON,OU=Domain Controllers,DC=ad,DC=fiske,DC=colorado,DC=edu and
backlink on
CN=JOHNSON,CN=Servers,CN=FISKE-MAIN,CN=Sites,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
are correct.
The system object reference (serverReferenceBL)
CN=JOHNSON,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=ad,DC=fiske,DC=colorado,DC=edu
and backlink on
CN=NTDS Settings,CN=JOHNSON,CN=Servers,CN=FISKE-MAIN,CN=Sites,CN=Configuration,DC=ad,DC=fiske,DC=colorado,DC=edu
are correct.
The system object reference (msDFSR-ComputerReferenceBL)
CN=JOHNSON,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=ad,DC=fiske,DC=colorado,DC=edu
and backlink on
CN=JOHNSON,OU=Domain Controllers,DC=ad,DC=fiske,DC=colorado,DC=edu are
correct.
......................... JOHNSON passed test VerifyReferences
Starting test: VerifyReplicas
......................... JOHNSON passed test VerifyReplicas
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
See DNS test in enterprise tests section for results
......................... JOHNSON passed test DNS
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : ad
Starting test: CheckSDRefDom
......................... ad passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ad passed test CrossRefValidation
Running enterprise tests on : ad.fiske.colorado.edu
Starting test: DNS
Test results for domain controllers:
DC: Johnson.ad.fiske.colorado.edu
Domain: ad.fiske.colorado.edu
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
The OS
Microsoft Windows Server 2012 R2 Standard (Service Pack level: 0.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 [00000010] Microsoft Hyper-V Network Adapter:
MAC address is 00:15:5D:03:E4:0E
IP Address is static
IP address: 192.168.3.101, fe80::3da0:bff8:222c:bc7
DNS servers:
192.168.3.102 (KENNEDY) [Valid]
192.168.3.101 (johnson.ad.fiske.colorado.edu.) [Valid]
The A host record(s) 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:
128.138.129.76 (<name unavailable>) [Valid]
128.138.130.30 (<name unavailable>) [Valid]
128.138.240.1 (<name unavailable>) [Valid]
TEST: Delegations (Del)
Delegation information for the zone: ad.fiske.colorado.edu.
Delegated domain name: _msdcs.ad.fiske.colorado.edu.
DNS server: johnson.ad.fiske.colorado.edu. IP:192.168.3.101 [Valid]
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone ad.fiske.colorado.edu
Test record dcdiag-test-record deleted successfully in zone ad.fiske.colorado.edu
TEST: Records registration (RReg)
Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
Matching CNAME record found at DNS server 192.168.3.102:
76a8cdf6-3de8-4cfe-8c00-a73691ed59ae._msdcs.ad.fiske.colorado.edu
Matching A record found at DNS server 192.168.3.102:
Johnson.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_ldap._tcp.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_ldap._tcp.fac5c331-84e9-4ba0-be74-c107c8b21250.domains._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_kerberos._tcp.dc._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_ldap._tcp.dc._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_kerberos._tcp.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_kerberos._udp.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_kpasswd._tcp.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_ldap._tcp.FISKE-MAIN._sites.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_kerberos._tcp.FISKE-MAIN._sites.dc._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_ldap._tcp.FISKE-MAIN._sites.dc._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_kerberos._tcp.FISKE-MAIN._sites.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_ldap._tcp.gc._msdcs.ad.fiske.colorado.edu
Matching A record found at DNS server 192.168.3.102:
gc._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_gc._tcp.FISKE-MAIN._sites.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_ldap._tcp.FISKE-MAIN._sites.gc._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.102:
_ldap._tcp.pdc._msdcs.ad.fiske.colorado.edu
Matching CNAME record found at DNS server 192.168.3.101:
76a8cdf6-3de8-4cfe-8c00-a73691ed59ae._msdcs.ad.fiske.colorado.edu
Matching A record found at DNS server 192.168.3.101:
Johnson.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_ldap._tcp.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_ldap._tcp.fac5c331-84e9-4ba0-be74-c107c8b21250.domains._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_kerberos._tcp.dc._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_ldap._tcp.dc._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_kerberos._tcp.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_kerberos._udp.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_kpasswd._tcp.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_ldap._tcp.FISKE-MAIN._sites.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_kerberos._tcp.FISKE-MAIN._sites.dc._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_ldap._tcp.FISKE-MAIN._sites.dc._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_kerberos._tcp.FISKE-MAIN._sites.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_ldap._tcp.gc._msdcs.ad.fiske.colorado.edu
Matching A record found at DNS server 192.168.3.101:
gc._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_gc._tcp.FISKE-MAIN._sites.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_ldap._tcp.FISKE-MAIN._sites.gc._msdcs.ad.fiske.colorado.edu
Matching SRV record found at DNS server 192.168.3.101:
_ldap._tcp.pdc._msdcs.ad.fiske.colorado.edu
TEST: External name resolution (Ext)
Internet name www.microsoft.com was resolved successfully
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 128.138.129.76 (<name unavailable>)
All tests passed on this DNS server
DNS server: 128.138.130.30 (<name unavailable>)
All tests passed on this DNS server
DNS server: 128.138.240.1 (<name unavailable>)
All tests passed on this DNS server
DNS server: 192.168.3.101 (johnson.ad.fiske.colorado.edu.)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
DNS delegation for the domain _msdcs.ad.fiske.colorado.edu. is operational on IP 192.168.3.101
DNS server: 192.168.3.102 (KENNEDY)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
Domain: ad.fiske.colorado.edu
Johnson PASS PASS PASS PASS PASS PASS PASS
......................... ad.fiske.colorado.edu passed test DNS
Starting test: LocatorCheck
GC Name: \\Johnson.ad.fiske.colorado.edu
Locator Flags: 0xe000f1fd
PDC Name: \\Johnson.ad.fiske.colorado.edu
Locator Flags: 0xe000f1fd
Time Server Name: \\Johnson.ad.fiske.colorado.edu
Locator Flags: 0xe000f1fd
Preferred Time Server Name: \\Johnson.ad.fiske.colorado.edu
Locator Flags: 0xe000f1fd
KDC Name: \\Johnson.ad.fiske.colorado.edu
Locator Flags: 0xe000f1fd
......................... ad.fiske.colorado.edu passed test
LocatorCheck
Starting test: FsmoCheck
GC Name: \\Johnson.ad.fiske.colorado.edu
Locator Flags: 0xe000f1fd
PDC Name: \\Johnson.ad.fiske.colorado.edu
Locator Flags: 0xe000f1fd
Time Server Name: \\Johnson.ad.fiske.colorado.edu
Locator Flags: 0xe000f1fd
Preferred Time Server Name: \\Johnson.ad.fiske.colorado.edu
Locator Flags: 0xe000f1fd
KDC Name: \\Johnson.ad.fiske.colorado.edu
Locator Flags: 0xe000f1fd
......................... ad.fiske.colorado.edu passed test FsmoCheck
Starting test: Intersite
Skipping site FISKE-MAIN, this site is outside the scope provided by
the command line arguments provided.
......................... ad.fiske.colorado.edu passed test Intersite