Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- dcdiag AD2
- Directory Server Diagnosis
- Performing initial setup:
- Trying to find home server...
- Home Server = AD2
- * Identified AD Forest.
- Done gathering initial info.
- Doing initial required tests
- Testing server: Default-First-Site-Name\AD2
- Starting test: Connectivity
- ......................... AD2 passed test Connectivity
- Doing primary tests
- Testing server: Default-First-Site-Name\AD2
- Starting test: Advertising
- Warning: DsGetDcName returned information for \\AD1.DOMAIN.local, when we were trying to reach AD2.
- SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
- ......................... AD2 failed test Advertising
- Starting test: FrsEvent
- ......................... AD2 passed test FrsEvent
- Starting test: DFSREvent
- There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL
- replication problems may cause Group Policy problems.
- ......................... AD2 failed test DFSREvent
- Starting test: SysVolCheck
- ......................... AD2 passed test SysVolCheck
- Starting test: KccEvent
- ......................... AD2 passed test KccEvent
- Starting test: KnowsOfRoleHolders
- ......................... AD2 passed test KnowsOfRoleHolders
- Starting test: MachineAccount
- ......................... AD2 passed test MachineAccount
- Starting test: NCSecDesc
- ......................... AD2 passed test NCSecDesc
- Starting test: NetLogons
- Unable to connect to the NETLOGON share! (\\AD2\netlogon)
- [AD2] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
- ......................... AD2 failed test NetLogons
- Starting test: ObjectsReplicated
- ......................... AD2 passed test ObjectsReplicated
- Starting test: Replications
- ......................... AD2 passed test Replications
- Starting test: RidManager
- ......................... AD2 passed test RidManager
- Starting test: Services
- ......................... AD2 passed test Services
- Starting test: SystemLog
- An error event occurred. EventID: 0x0000272C
- Time Generated: 06/20/2024 19:02:37
- Event String:
- DCOM was unable to communicate with the computer 103.74.211.195 using any of the configured protocols; requested by PID 20e8 (C:\Windows\system32\dcdiag.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.
- An error event occurred. EventID: 0x0000272C
- Time Generated: 06/20/2024 19:10:16
- Event String:
- DCOM was unable to communicate with the computer 103.74.211.195 using any of the configured protocols; requested by PID 2680 (C:\Windows\system32\dcdiag.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.
- An error event occurred. EventID: 0x0000272C
- Time Generated: 06/20/2024 19:13:20
- Event String:
- DCOM was unable to communicate with the computer 103.74.211.195 using any of the configured protocols; requested by PID 1a9c (C:\Windows\system32\dcdiag.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.
- An error event occurred. EventID: 0x0000272C
- Time Generated: 06/20/2024 19:13:52
- Event String:
- DCOM was unable to communicate with the computer 103.74.211.195 using any of the configured protocols; requested by PID 1e8 (C:\Windows\system32\dcdiag.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.
- An error event occurred. EventID: 0x0000272C
- Time Generated: 06/20/2024 19:16:25
- Event String:
- DCOM was unable to communicate with the computer 103.74.211.195 using any of the configured protocols; requested by PID 2444 (C:\Windows\system32\dcdiag.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.
- A warning event occurred. EventID: 0x000727A5
- Time Generated: 06/20/2024 19:16:37
- Event String: The WinRM service is not listening for WS-Management requests.
- A warning event occurred. EventID: 0x0000000F
- Time Generated: 06/20/2024 19:18:33
- Event String:
- Credential Guard and/or VBS Key Isolation are configured but the secure kernel is not running; continuing without them.
- A warning event occurred. EventID: 0x0000000C
- Time Generated: 06/20/2024 19:19:00
- Event String:
- Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.
- An error event occurred. EventID: 0x80000025
- Time Generated: 06/20/2024 19:19:16
- Event String:
- The Key Distribution Center (KDC) encountered a ticket that did not contain information about the account that requested the ticket while processing a request for another ticket. This prevented security checks from running and could open security vulnerabilities. See https://go.microsoft.com/fwlink/?linkid=2173051 to learn more.
- A warning event occurred. EventID: 0x00002720
- Time Generated: 06/20/2024 19:19:21
- Event String:
- The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
- An error event occurred. EventID: 0x0000272C
- Time Generated: 06/20/2024 19:21:05
- Event String:
- DCOM was unable to communicate with the computer 103.74.211.195 using any of the configured protocols; requested by PID c20 (C:\Windows\system32\dcdiag.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.
- An error event occurred. EventID: 0x0000272C
- Time Generated: 06/20/2024 19:41:35
- Event String:
- DCOM was unable to communicate with the computer 103.74.211.195 using any of the configured protocols; requested by PID 804 (C:\Windows\system32\dcdiag.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.
- ......................... AD2 failed test SystemLog
- Starting test: VerifyReferences
- ......................... AD2 passed test VerifyReferences
- 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 : DOMAIN
- Starting test: CheckSDRefDom
- ......................... DOMAIN passed test CheckSDRefDom
- Starting test: CrossRefValidation
- ......................... DOMAIN 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
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement