Advertisement
Isuress

2012 dns results

May 26th, 2016
47
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.53 KB | None | 0 0
  1.  
  2. Directory Server Diagnosis
  3.  
  4.  
  5. Performing initial setup:
  6.  
  7. Trying to find home server...
  8.  
  9. Home Server = MYCOMPANY-VM-DOMAIN
  10.  
  11. * Identified AD Forest.
  12. Done gathering initial info.
  13.  
  14.  
  15. Doing initial required tests
  16.  
  17.  
  18. Testing server: MYCOMPANY\MYCOMPANY-VM-DOMAIN
  19.  
  20. Starting test: Connectivity
  21.  
  22. ......................... MYCOMPANY-VM-DOMAIN passed test Connectivity
  23.  
  24.  
  25.  
  26. Doing primary tests
  27.  
  28.  
  29. Testing server: MYCOMPANY\MYCOMPANY-VM-DOMAIN
  30.  
  31. Starting test: Advertising
  32.  
  33. ......................... MYCOMPANY-VM-DOMAIN passed test Advertising
  34.  
  35. Starting test: FrsEvent
  36.  
  37. ......................... MYCOMPANY-VM-DOMAIN passed test FrsEvent
  38.  
  39. Starting test: DFSREvent
  40.  
  41. There are warning or error events within the last 24 hours after the
  42.  
  43. SYSVOL has been shared. Failing SYSVOL replication problems may cause
  44.  
  45. Group Policy problems.
  46. ......................... MYCOMPANY-VM-DOMAIN failed test DFSREvent
  47.  
  48. Starting test: SysVolCheck
  49.  
  50. ......................... MYCOMPANY-VM-DOMAIN passed test SysVolCheck
  51.  
  52. Starting test: KccEvent
  53.  
  54. ......................... MYCOMPANY-VM-DOMAIN passed test KccEvent
  55.  
  56. Starting test: KnowsOfRoleHolders
  57.  
  58. ......................... MYCOMPANY-VM-DOMAIN passed test KnowsOfRoleHolders
  59.  
  60. Starting test: MachineAccount
  61.  
  62. ......................... MYCOMPANY-VM-DOMAIN passed test MachineAccount
  63.  
  64. Starting test: NCSecDesc
  65.  
  66. ......................... MYCOMPANY-VM-DOMAIN passed test NCSecDesc
  67.  
  68. Starting test: NetLogons
  69.  
  70. ......................... MYCOMPANY-VM-DOMAIN passed test NetLogons
  71.  
  72. Starting test: ObjectsReplicated
  73.  
  74. ......................... MYCOMPANY-VM-DOMAIN passed test ObjectsReplicated
  75.  
  76. Starting test: Replications
  77.  
  78. ......................... MYCOMPANY-VM-DOMAIN passed test Replications
  79.  
  80. Starting test: RidManager
  81.  
  82. ......................... MYCOMPANY-VM-DOMAIN passed test RidManager
  83.  
  84. Starting test: Services
  85.  
  86. ......................... MYCOMPANY-VM-DOMAIN passed test Services
  87.  
  88. Starting test: SystemLog
  89.  
  90. A warning event occurred. EventID: 0x0000000C
  91.  
  92. Time Generated: 05/26/2016 13:47:05
  93.  
  94. Event String:
  95.  
  96. 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.
  97.  
  98. A warning event occurred. EventID: 0x00001696
  99.  
  100. Time Generated: 05/26/2016 13:47:25
  101.  
  102. Event String:
  103.  
  104. Dynamic registration or deregistration of one or more DNS records failed with the following error:
  105.  
  106.  
  107. A warning event occurred. EventID: 0xA004001B
  108.  
  109. Time Generated: 05/26/2016 13:47:25
  110.  
  111. EvtFormatMessage failed, error 15027 the message resource is present but the message is not found in the string/message table.
  112. (Event String (event log = System) could not be retrieved, error
  113.  
  114. 0x3ab3)
  115.  
  116. A warning event occurred. EventID: 0x000003F6
  117.  
  118. Time Generated: 05/26/2016 13:54:10
  119.  
  120. Event String:
  121.  
  122. Name resolution for the name _ldap._tcp.pdc._msdcs.ad.MYCOMPANY.com. timed out after none of the configured DNS servers responded.
  123.  
  124. A warning event occurred. EventID: 0x0000000C
  125.  
  126. Time Generated: 05/26/2016 13:54:20
  127.  
  128. Event String:
  129.  
  130. 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.
  131.  
  132. A warning event occurred. EventID: 0x000727AA
  133.  
  134. Time Generated: 05/26/2016 13:54:22
  135.  
  136. Event String:
  137.  
  138. The WinRM service failed to create the following SPNs: WSMAN/MYCOMPANY-VM-DOMAIN.ad.MYCOMPANY.com; WSMAN/MYCOMPANY-VM-DOMAIN.
  139.  
  140.  
  141. A warning event occurred. EventID: 0x00009016
  142.  
  143. Time Generated: 05/26/2016 13:59:56
  144.  
  145. Event String:
  146.  
  147. No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.
  148.  
  149. A warning event occurred. EventID: 0x00009016
  150.  
  151. Time Generated: 05/26/2016 13:59:56
  152.  
  153. Event String:
  154.  
  155. No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.
  156.  
  157. A warning event occurred. EventID: 0x00001695
  158.  
  159. Time Generated: 05/26/2016 14:19:01
  160.  
  161. Event String:
  162.  
  163. Dynamic registration or deletion of one or more DNS records associated with DNS domain 'ad.MYCOMPANY.com.' failed. These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).
  164.  
  165.  
  166. A warning event occurred. EventID: 0x00001695
  167.  
  168. Time Generated: 05/26/2016 14:19:01
  169.  
  170. Event String:
  171.  
  172. Dynamic registration or deletion of one or more DNS records associated with DNS domain 'DomainDnsZones.ad.MYCOMPANY.com.' failed. These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).
  173.  
  174.  
  175. A warning event occurred. EventID: 0x00001695
  176.  
  177. Time Generated: 05/26/2016 14:19:01
  178.  
  179. Event String:
  180.  
  181. Dynamic registration or deletion of one or more DNS records associated with DNS domain 'ForestDnsZones.ad.MYCOMPANY.com.' failed. These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).
  182.  
  183.  
  184. A warning event occurred. EventID: 0x00000090
  185.  
  186. Time Generated: 05/26/2016 14:28:04
  187.  
  188. Event String:
  189.  
  190. The time service has stopped advertising as a good time source.
  191.  
  192. ......................... MYCOMPANY-VM-DOMAIN passed test SystemLog
  193.  
  194. Starting test: VerifyReferences
  195.  
  196. ......................... MYCOMPANY-VM-DOMAIN passed test VerifyReferences
  197.  
  198.  
  199.  
  200. Running partition tests on : ForestDnsZones
  201.  
  202. Starting test: CheckSDRefDom
  203.  
  204. ......................... ForestDnsZones passed test CheckSDRefDom
  205.  
  206. Starting test: CrossRefValidation
  207.  
  208. ......................... ForestDnsZones passed test
  209.  
  210. CrossRefValidation
  211.  
  212.  
  213. Running partition tests on : DomainDnsZones
  214.  
  215. Starting test: CheckSDRefDom
  216.  
  217. ......................... DomainDnsZones passed test CheckSDRefDom
  218.  
  219. Starting test: CrossRefValidation
  220.  
  221. ......................... DomainDnsZones passed test
  222.  
  223. CrossRefValidation
  224.  
  225.  
  226. Running partition tests on : Schema
  227.  
  228. Starting test: CheckSDRefDom
  229.  
  230. ......................... Schema passed test CheckSDRefDom
  231.  
  232. Starting test: CrossRefValidation
  233.  
  234. ......................... Schema passed test CrossRefValidation
  235.  
  236.  
  237. Running partition tests on : Configuration
  238.  
  239. Starting test: CheckSDRefDom
  240.  
  241. ......................... Configuration passed test CheckSDRefDom
  242.  
  243. Starting test: CrossRefValidation
  244.  
  245. ......................... Configuration passed test CrossRefValidation
  246.  
  247.  
  248. Running partition tests on : ad
  249.  
  250. Starting test: CheckSDRefDom
  251.  
  252. ......................... ad passed test CheckSDRefDom
  253.  
  254. Starting test: CrossRefValidation
  255.  
  256. ......................... ad passed test CrossRefValidation
  257.  
  258.  
  259. Running enterprise tests on : ad.MYCOMPANY.com
  260.  
  261. Starting test: LocatorCheck
  262.  
  263. ......................... ad.MYCOMPANY.com passed test LocatorCheck
  264.  
  265. Starting test: Intersite
  266.  
  267. ......................... ad.MYCOMPANY.com passed test Intersite
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement