[Samba] DCdiag tests
James
lingpanda101 at gmail.com
Wed Feb 25 10:43:35 MST 2015
Directory Server Diagnosis
Performing initial setup:
* Identified AD Forest.
Got error while checking if the DC is using FRS or DFSR. Error:
A device attached to the system is not functioning.The VerifyReferences,
FrsEvent and DfsrEvent tests might fail because of this error.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\pfsambadc1
Starting test: Connectivity
......................... pfsambadc1 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\pfsambadc1
Starting test: Advertising
......................... pfsambadc1 passed test Advertising
Starting test: FrsEvent
......................... pfsambadc1 passed test FrsEvent
Starting test: DFSREvent
......................... pfsambadc1 passed test DFSREvent
Starting test: SysVolCheck
The SysVol is not ready. This can cause the DC to not advertise
itself as a DC for netlogon after dcpromo. Also trouble with FRS
SysVol replication can cause Group Policy problems. Check the FRS
event log on this DC.
......................... pfsambadc1 failed test SysVolCheck
Starting test: KccEvent
......................... pfsambadc1 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... pfsambadc1 passed test
KnowsOfRoleHolders
Starting test: MachineAccount
......................... pfsambadc1 passed test MachineAccount
Starting test: NCSecDesc
......................... pfsambadc1 passed test NCSecDesc
Starting test: NetLogons
......................... pfsambadc1 passed test NetLogons
Starting test: ObjectsReplicated
Failed to read object metadata on pfsambadc1, error
The request is not supported.
Failed to read object metadata on pfsambadc1, error
The request is not supported.
......................... pfsambadc1 passed test ObjectsReplicated
Starting test: Replications
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
pfsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
pfsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
pfsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
pfsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
pfsambadc2.
REPLICATION-RECEIVED LATENCY WARNING
pfsambadc1: Current time is 2015-02-25 12:27:35.
CN=Configuration,DC=domain,DC=local
Last replication received from pfsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
CN=Schema,CN=Configuration,DC=domain,DC=local
Last replication received from pfsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
DC=domain,DC=local
Last replication received from pfsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
DC=ForestDnsZones,DC=domain,DC=local
Last replication received from pfsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
DC=DomainDnsZones,DC=domain,DC=local
Last replication received from pfsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
......................... pfsambadc1 passed test Replications
Starting test: RidManager
......................... pfsambadc1 passed test RidManager
Starting test: Services
Could not open EventSystem Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
Could not open RpcSs Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
Could not open NTDS Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
Could not open DnsCache Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
Could not open DFSR Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
Could not open IsmServ Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
Could not open kdc Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
Could not open SamSs Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
Could not open LanmanServer Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
Could not open LanmanWorkstation Service on pfsambadc1,
error 0x8
"Not enough storage is available to process this command."
Could not open w32time Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
Invalid service type: NETLOGON on pfsambadc1, current value
WIN32_OWN_PROCESS, expected value WIN32_SHARE_PROCESS
Invalid service startup type: NETLOGON on pfsambadc1,
current value
DEMAND_START, expected value AUTO_START
......................... pfsambadc1 failed test Services
Starting test: SystemLog
......................... pfsambadc1 passed test SystemLog
Starting test: VerifyReferences
Some objects relating to the DC pfsambadc1 have problems:
[1] Problem: Missing Expected Value
Base Object:
CN=NTDS
Settings,CN=pfsambadc1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
Base Object Description: "DSA Object"
Value Object Attribute Name: serverReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
[1] Problem: Missing Expected Value
Base Object: CN=pfsambadc1,OU=Domain
Controllers,DC=domain,DC=local
Base Object Description: "DC Account Object"
Value Object Attribute Name: frsComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
......................... pfsambadc1 failed test VerifyReferences
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration 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 : domain
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
The application directory partition
DC=ForestDnsZones,DC=domain,DC=local is missing a security
descriptor
reference domain. The administrator should set the
msDS-SD-Reference-Domain attribute on the cross reference
object
CN=c5859e2d-a2f2-4ad6-ac72-437dd556864c,CN=Partitions,CN=Configuration,DC=domain,DC=local
to the DN of a domain.
......................... ForestDnsZones failed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
The application directory partition
DC=DomainDnsZones,DC=domain,DC=local is missing a security
descriptor
reference domain. The administrator should set the
msDS-SD-Reference-Domain attribute on the cross reference
object
CN=601416b0-143d-42e7-89b8-5892d265a460,CN=Partitions,CN=Configuration,DC=domain,DC=local
to the DN of a domain.
......................... DomainDnsZones failed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running enterprise tests on : domain.local
Starting test: LocatorCheck
......................... domain.local passed test LocatorCheck
Starting test: Intersite
......................... domain.local passed test Intersite
Directory Server Diagnosis
Performing initial setup:
* Connecting to directory service on server pfsambadc1.
* Identified AD Forest.
Collecting AD specific global data
* Collecting site info.
Calling
ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=domain,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
The previous call succeeded
Iterating through the sites
Looking at base site object: CN=NTDS Site
Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
Getting ISTG and options for the site
Looking at base site object: CN=NTDS Site
Settings,CN=south,CN=Sites,CN=Configuration,DC=domain,DC=local
Getting ISTG and options for the site
Looking at base site object: CN=NTDS Site
Settings,CN=north,CN=Sites,CN=Configuration,DC=domain,DC=local
Getting ISTG and options for the site
* Identifying all servers.
Calling
ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=domain,DC=local,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=pfsambadc1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
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=pfsambadc2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
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=solsambadc1,CN=Servers,CN=south,CN=Sites,CN=Configuration,DC=domain,DC=local
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=solsambadc2,CN=Servers,CN=south,CN=Sites,CN=Configuration,DC=domain,DC=local
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=dusambadc1,CN=Servers,CN=north,CN=Sites,CN=Configuration,DC=domain,DC=local
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=dusambadc2,CN=Servers,CN=north,CN=Sites,CN=Configuration,DC=domain,DC=local
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
* Identifying all NC cross-refs.
Got error while checking if the DC is using FRS or DFSR. Error:
A device attached to the system is not functioning.The VerifyReferences,
FrsEvent and DfsrEvent tests might fail because of this error.
* Found 6 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\pfsambadc1
Starting test: Connectivity
* Active Directory LDAP Services Check
Determining IP4 connectivity
* Active Directory RPC Services Check
......................... pfsambadc1 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\pfsambadc1
Starting test: Advertising
The DC pfsambadc1 is advertising itself as a DC and having a DS.
The DC pfsambadc1 is advertising as an LDAP server
The DC pfsambadc1 is advertising as having a writeable directory
The DC pfsambadc1 is advertising as a Key Distribution Center
The DC pfsambadc1 is advertising as a time server
The DS pfsambadc1 is advertising as a GC.
......................... pfsambadc1 passed test Advertising
Test omitted by user request: CheckSecurityError
Test omitted by user request: CutoffServers
Starting test: FrsEvent
* The File Replication Service Event log test
......................... pfsambadc1 passed test FrsEvent
Starting test: DFSREvent
The DFS Replication Event Log.
Skip the test because the server is running FRS.
......................... pfsambadc1 passed test DFSREvent
Starting test: SysVolCheck
* The File Replication Service SYSVOL ready test
The SysVol is not ready. This can cause the DC to not advertise
itself as a DC for netlogon after dcpromo. Also trouble with FRS
SysVol replication can cause Group Policy problems. Check the FRS
event log on this DC.
......................... pfsambadc1 failed test SysVolCheck
Starting test: KccEvent
* The KCC Event log test
Found no KCC errors in "Directory Service" Event log in the
last 15 minutes.
......................... pfsambadc1 passed test KccEvent
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=pfsambadc1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
Role Domain Owner = CN=NTDS
Settings,CN=pfsambadc1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
Role PDC Owner = CN=NTDS
Settings,CN=pfsambadc1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
Role Rid Owner = CN=NTDS
Settings,CN=pfsambadc1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=pfsambadc1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
......................... pfsambadc1 passed test
KnowsOfRoleHolders
Starting test: MachineAccount
Checking machine account for DC pfsambadc1 on DC pfsambadc1.
* SPN found :LDAP/pfsambadc1.domain.local/domain.local
* SPN found :LDAP/pfsambadc1.domain.local
* SPN found :LDAP/pfsambadc1
* SPN found :LDAP/pfsambadc1.domain.local/domain
* SPN found
:LDAP/acc2392f-9567-450f-bcb3-4fb1034b8753._msdcs.domain.local
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/acc2392f-9567-450f-bcb3-4fb1034b8753/domain.local
* SPN found :HOST/pfsambadc1.domain.local/domain.local
* SPN found :HOST/pfsambadc1.domain.local
* SPN found :HOST/pfsambadc1
* SPN found :HOST/pfsambadc1.domain.local/domain
* SPN found :GC/pfsambadc1.domain.local/domain.local
......................... pfsambadc1 passed test MachineAccount
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC pfsambadc1.
* Security Permissions Check for
CN=Configuration,DC=domain,DC=local
(Configuration,Version 3)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=domain,DC=local
(Schema,Version 3)
* Security Permissions Check for
DC=domain,DC=local
(Domain,Version 3)
* Security Permissions Check for
DC=ForestDnsZones,DC=domain,DC=local
(NDNC,Version 3)
* Security Permissions Check for
DC=DomainDnsZones,DC=domain,DC=local
(NDNC,Version 3)
......................... pfsambadc1 passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\pfsambadc1\netlogon
Verified share \\pfsambadc1\sysvol
......................... pfsambadc1 passed test NetLogons
Starting test: ObjectsReplicated
pfsambadc1 is in domain DC=domain,DC=local
Checking for CN=pfsambadc1,OU=Domain
Controllers,DC=domain,DC=local in domain DC=domain,DC=local on 1 servers
Failed to read object metadata on pfsambadc1, error
The request is not supported.
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=pfsambadc1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
in domain CN=Configuration,DC=domain,DC=local on 1 servers
Failed to read object metadata on pfsambadc1, error
The request is not supported.
Object is up-to-date on all servers.
......................... pfsambadc1 passed test ObjectsReplicated
Test omitted by user request: OutboundSecureChannels
Starting test: Replications
* Replications Check
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
pfsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
pfsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
pfsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
pfsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc1.
ERROR: Unexpected number of reps-to neighbors returned from
solsambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
dusambadc2.
ERROR: Unexpected number of reps-to neighbors returned from
pfsambadc2.
* Replication Latency Check
REPLICATION-RECEIVED LATENCY WARNING
pfsambadc1: Current time is 2015-02-25 12:28:41.
CN=Configuration,DC=domain,DC=local
Last replication received from pfsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Latency information for 1 entries in the vector were
ignored.
1 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=domain,DC=local
Last replication received from pfsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Latency information for 1 entries in the vector were
ignored.
1 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=domain,DC=local
Last replication received from pfsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Latency information for 1 entries in the vector were
ignored.
1 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=ForestDnsZones,DC=domain,DC=local
Last replication received from pfsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Latency information for 1 entries in the vector were
ignored.
1 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=domain,DC=local
Last replication received from pfsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from solsambadc2 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Last replication received from dusambadc1 at
1969-12-31 19:00:00
WARNING: This latency is over the Tombstone Lifetime of 180
days!
Latency information for 1 entries in the vector were
ignored.
1 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).
......................... pfsambadc1 passed test Replications
Starting test: RidManager
* Available RID Pool for the Domain is 4600 to 1073741823
* pfsambadc1.domain.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1100 to 1599
* rIDPreviousAllocationPool is 1100 to 1599
* rIDNextRID: 1325
......................... pfsambadc1 passed test RidManager
Starting test: Services
* Checking Service: EventSystem
Could not open EventSystem Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
* Checking Service: RpcSs
Could not open RpcSs Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
* Checking Service: NTDS
Could not open NTDS Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
* Checking Service: DnsCache
Could not open DnsCache Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
* Checking Service: DFSR
Could not open DFSR Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
* Checking Service: IsmServ
Could not open IsmServ Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
* Checking Service: kdc
Could not open kdc Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
* Checking Service: SamSs
Could not open SamSs Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
* Checking Service: LanmanServer
Could not open LanmanServer Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
* Checking Service: LanmanWorkstation
Could not open LanmanWorkstation Service on pfsambadc1,
error 0x8
"Not enough storage is available to process this command."
* Checking Service: w32time
Could not open w32time Service on pfsambadc1, error 0x8
"Not enough storage is available to process this command."
* Checking Service: NETLOGON
Invalid service type: NETLOGON on pfsambadc1, current value
WIN32_OWN_PROCESS, expected value WIN32_SHARE_PROCESS
Invalid service startup type: NETLOGON on pfsambadc1,
current value
DEMAND_START, expected value AUTO_START
......................... pfsambadc1 failed test Services
Starting test: SystemLog
* The System Event log test
Found no errors in "System" Event log in the last 60 minutes.
......................... pfsambadc1 passed test SystemLog
Test omitted by user request: Topology
Test omitted by user request: VerifyEnterpriseReferences
Starting test: VerifyReferences
The system object reference (serverReference)
CN=pfsambadc1,OU=Domain Controllers,DC=domain,DC=local and
backlink on
CN=pfsambadc1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
are correct.
Some objects relating to the DC pfsambadc1 have problems:
[1] Problem: Missing Expected Value
Base Object:
CN=NTDS
Settings,CN=pfsambadc1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=local
Base Object Description: "DSA Object"
Value Object Attribute Name: serverReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
[1] Problem: Missing Expected Value
Base Object: CN=pfsambadc1,OU=Domain
Controllers,DC=domain,DC=local
Base Object Description: "DC Account Object"
Value Object Attribute Name: frsComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
......................... pfsambadc1 failed test VerifyReferences
Test omitted by user request: VerifyReplicas
Test omitted by user request: DNS
Test omitted by user request: DNS
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration 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 : domain
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
The application directory partition
DC=ForestDnsZones,DC=domain,DC=local is missing a security
descriptor
reference domain. The administrator should set the
msDS-SD-Reference-Domain attribute on the cross reference
object
CN=c5859e2d-a2f2-4ad6-ac72-437dd556864c,CN=Partitions,CN=Configuration,DC=domain,DC=local
to the DN of a domain.
......................... ForestDnsZones failed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
The application directory partition
DC=DomainDnsZones,DC=domain,DC=local is missing a security
descriptor
reference domain. The administrator should set the
msDS-SD-Reference-Domain attribute on the cross reference
object
CN=601416b0-143d-42e7-89b8-5892d265a460,CN=Partitions,CN=Configuration,DC=domain,DC=local
to the DN of a domain.
......................... DomainDnsZones failed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running enterprise tests on : domain.local
Test omitted by user request: DNS
Test omitted by user request: DNS
Starting test: LocatorCheck
GC Name: \\pfsambadc1.domain.local
Locator Flags: 0xe00013fd
PDC Name: \\pfsambadc1.domain.local
Locator Flags: 0xe00013fd
Time Server Name: \\pfsambadc1.domain.local
Locator Flags: 0xe00013fd
Preferred Time Server Name: \\pfsambadc1.domain.local
Locator Flags: 0xe00013fd
KDC Name: \\pfsambadc1.domain.local
Locator Flags: 0xe00013fd
......................... domain.local passed test LocatorCheck
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside
the scope
provided by the command line arguments provided.
Skipping site south, this site is outside the scope provided
by the
command line arguments provided.
Skipping site north, this site is outside the scope provided
by the
command line arguments provided.
......................... domain.local passed test Intersite
On 2/25/2015 12:06 PM, Tim wrote:
> Hey all,
>
> has anyone done dcdiag against his DC yet? It's made from a windows client on command line: dcdiag /s:<servername> What are your results?
>
> With me some of the tests were not successful, e.g. ForestDNSDomain. My dcdiag is German so its output would not be so helpful for the mailing list. So somebody else can do a check to compare?
>
> Thanks in advance
> Tim
--
-James
More information about the samba
mailing list