Advertisement
Guest User

Untitled

a guest
Jun 20th, 2024
22
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.51 KB | None | 0 0
  1.  
  2.  
  3. dcdiag AD2
  4.  
  5. Directory Server Diagnosis
  6.  
  7. Performing initial setup:
  8. Trying to find home server...
  9. Home Server = AD2
  10. * Identified AD Forest.
  11. Done gathering initial info.
  12.  
  13. Doing initial required tests
  14.  
  15. Testing server: Default-First-Site-Name\AD2
  16. Starting test: Connectivity
  17. ......................... AD2 passed test Connectivity
  18.  
  19. Doing primary tests
  20.  
  21. Testing server: Default-First-Site-Name\AD2
  22. Starting test: Advertising
  23. Warning: DsGetDcName returned information for \\AD1.DOMAIN.local, when we were trying to reach AD2.
  24. SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
  25. ......................... AD2 failed test Advertising
  26. Starting test: FrsEvent
  27. ......................... AD2 passed test FrsEvent
  28. Starting test: DFSREvent
  29. There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL
  30. replication problems may cause Group Policy problems.
  31. ......................... AD2 failed test DFSREvent
  32. Starting test: SysVolCheck
  33. ......................... AD2 passed test SysVolCheck
  34. Starting test: KccEvent
  35. ......................... AD2 passed test KccEvent
  36. Starting test: KnowsOfRoleHolders
  37. ......................... AD2 passed test KnowsOfRoleHolders
  38. Starting test: MachineAccount
  39. ......................... AD2 passed test MachineAccount
  40. Starting test: NCSecDesc
  41. ......................... AD2 passed test NCSecDesc
  42. Starting test: NetLogons
  43. Unable to connect to the NETLOGON share! (\\AD2\netlogon)
  44. [AD2] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
  45. ......................... AD2 failed test NetLogons
  46. Starting test: ObjectsReplicated
  47. ......................... AD2 passed test ObjectsReplicated
  48. Starting test: Replications
  49. ......................... AD2 passed test Replications
  50. Starting test: RidManager
  51. ......................... AD2 passed test RidManager
  52. Starting test: Services
  53. ......................... AD2 passed test Services
  54. Starting test: SystemLog
  55. An error event occurred. EventID: 0x0000272C
  56. Time Generated: 06/20/2024 19:02:37
  57. Event String:
  58. 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}.
  59. An error event occurred. EventID: 0x0000272C
  60. Time Generated: 06/20/2024 19:10:16
  61. Event String:
  62. 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}.
  63. An error event occurred. EventID: 0x0000272C
  64. Time Generated: 06/20/2024 19:13:20
  65. Event String:
  66. 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}.
  67. An error event occurred. EventID: 0x0000272C
  68. Time Generated: 06/20/2024 19:13:52
  69. Event String:
  70. 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}.
  71. An error event occurred. EventID: 0x0000272C
  72. Time Generated: 06/20/2024 19:16:25
  73. Event String:
  74. 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}.
  75. A warning event occurred. EventID: 0x000727A5
  76. Time Generated: 06/20/2024 19:16:37
  77. Event String: The WinRM service is not listening for WS-Management requests.
  78. A warning event occurred. EventID: 0x0000000F
  79. Time Generated: 06/20/2024 19:18:33
  80. Event String:
  81. Credential Guard and/or VBS Key Isolation are configured but the secure kernel is not running; continuing without them.
  82. A warning event occurred. EventID: 0x0000000C
  83. Time Generated: 06/20/2024 19:19:00
  84. Event String:
  85. 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.
  86. An error event occurred. EventID: 0x80000025
  87. Time Generated: 06/20/2024 19:19:16
  88. Event String:
  89. 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.
  90. A warning event occurred. EventID: 0x00002720
  91. Time Generated: 06/20/2024 19:19:21
  92. Event String:
  93. The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
  94. An error event occurred. EventID: 0x0000272C
  95. Time Generated: 06/20/2024 19:21:05
  96. Event String:
  97. 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}.
  98. An error event occurred. EventID: 0x0000272C
  99. Time Generated: 06/20/2024 19:41:35
  100. Event String:
  101. 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}.
  102. ......................... AD2 failed test SystemLog
  103. Starting test: VerifyReferences
  104. ......................... AD2 passed test VerifyReferences
  105.  
  106.  
  107. Running partition tests on : ForestDnsZones
  108. Starting test: CheckSDRefDom
  109. ......................... ForestDnsZones passed test CheckSDRefDom
  110. Starting test: CrossRefValidation
  111. ......................... ForestDnsZones passed test CrossRefValidation
  112.  
  113. Running partition tests on : DomainDnsZones
  114. Starting test: CheckSDRefDom
  115. ......................... DomainDnsZones passed test CheckSDRefDom
  116. Starting test: CrossRefValidation
  117. ......................... DomainDnsZones passed test CrossRefValidation
  118.  
  119. Running partition tests on : Schema
  120. Starting test: CheckSDRefDom
  121. ......................... Schema passed test CheckSDRefDom
  122. Starting test: CrossRefValidation
  123. ......................... Schema passed test CrossRefValidation
  124.  
  125. Running partition tests on : Configuration
  126. Starting test: CheckSDRefDom
  127. ......................... Configuration passed test CheckSDRefDom
  128. Starting test: CrossRefValidation
  129. ......................... Configuration passed test CrossRefValidation
  130.  
  131. Running partition tests on : DOMAIN
  132. Starting test: CheckSDRefDom
  133. ......................... DOMAIN passed test CheckSDRefDom
  134. Starting test: CrossRefValidation
  135. ......................... DOMAIN passed test CrossRefValidation
  136.  
  137. Running enterprise tests on : DOMAIN.local
  138. Starting test: LocatorCheck
  139. ......................... DOMAIN.local passed test LocatorCheck
  140. Starting test: Intersite
  141. ......................... DOMAIN.local passed test Intersite
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement