API tools faq
paste
Advertisement
Guest User

Itai Ganot - DC's not replicating

a guest
Feb 12th, 2013
159
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 33.11 KB | None | 0 0
raw download clone embed print report diff
  1.  
  2. Directory Server Diagnosis
  3.  
  4.  
  5. Performing initial setup:
  6.  
  7. Trying to find home server...
  8.  
  9. * Verifying that the local machine DR, is a Directory Server.
  10. Home Server = DR
  11.  
  12. * Connecting to directory service on server DR.
  13.  
  14. * Identified AD Forest.
  15. Collecting AD specific global data
  16. * Collecting site info.
  17.  
  18. Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
  19. The previous call succeeded
  20. Iterating through the sites
  21. Looking at base site object: CN=NTDS Site Settings,CN=office,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  22. Getting ISTG and options for the site
  23. Looking at base site object: CN=NTDS Site Settings,CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  24. Getting ISTG and options for the site
  25. * Identifying all servers.
  26.  
  27. Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
  28. The previous call succeeded....
  29. The previous call succeeded
  30. Iterating through the list of servers
  31. Getting information for the server CN=NTDS Settings,CN=DC3,CN=Servers,CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  32. objectGuid obtained
  33. InvocationID obtained
  34. dnsHostname obtained
  35. site info obtained
  36. All the info for the server collected
  37. Getting information for the server CN=NTDS Settings,CN=DR,CN=Servers,CN=office,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  38. objectGuid obtained
  39. InvocationID obtained
  40. dnsHostname obtained
  41. site info obtained
  42. All the info for the server collected
  43. Getting information for the server CN=NTDS Settings,CN=DC2,CN=Servers,CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  44. objectGuid obtained
  45. InvocationID obtained
  46. dnsHostname obtained
  47. site info obtained
  48. All the info for the server collected
  49. * Identifying all NC cross-refs.
  50.  
  51. * Found 3 DC(s). Testing 1 of them.
  52.  
  53. Done gathering initial info.
  54.  
  55.  
  56. Doing initial required tests
  57.  
  58.  
  59. Testing server: office\DR
  60.  
  61. Starting test: Connectivity
  62.  
  63. * Active Directory LDAP Services Check
  64. Determining IP4 connectivity
  65. * Active Directory RPC Services Check
  66. ......................... DR passed test Connectivity
  67.  
  68.  
  69.  
  70. Doing primary tests
  71.  
  72.  
  73. Testing server: office\DR
  74.  
  75. Starting test: Advertising
  76.  
  77. The DC DR is advertising itself as a DC and having a DS.
  78. The DC DR is advertising as an LDAP server
  79. The DC DR is advertising as having a writeable directory
  80. The DC DR is advertising as a Key Distribution Center
  81. Warning: DR is not advertising as a time server.
  82.  
  83. The DS DR is advertising as a GC.
  84. ......................... DR failed test Advertising
  85.  
  86. Test omitted by user request: CheckSecurityError
  87.  
  88. Test omitted by user request: CutoffServers
  89.  
  90. Starting test: FrsEvent
  91.  
  92. * The File Replication Service Event log test
  93. There are warning or error events within the last 24 hours after the
  94.  
  95. SYSVOL has been shared. Failing SYSVOL replication problems may cause
  96.  
  97. Group Policy problems.
  98. A warning event occurred. EventID: 0x800034C4
  99.  
  100. Time Generated: 02/12/2013 10:32:09
  101.  
  102. Event String:
  103.  
  104. The File Replication Service is having trouble enabling replication from DC3 to DR for d:\sysvol\domain using the DNS name DC3.DOMAIN.com. FRS will keep retrying.
  105.  
  106. Following are some of the reasons you would see this warning.
  107.  
  108.  
  109.  
  110. [1] FRS can not correctly resolve the DNS name DC3.DOMAIN.com from this computer.
  111.  
  112. [2] FRS is not running on DC3.DOMAIN.com.
  113.  
  114. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
  115.  
  116.  
  117.  
  118. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
  119.  
  120. A warning event occurred. EventID: 0x800034C4
  121.  
  122. Time Generated: 02/12/2013 10:32:09
  123.  
  124. Event String:
  125.  
  126. The File Replication Service is having trouble enabling replication from DC2 to DR for d:\sysvol\domain using the DNS name DC2.DOMAIN.com. FRS will keep retrying.
  127.  
  128. Following are some of the reasons you would see this warning.
  129.  
  130.  
  131.  
  132. [1] FRS can not correctly resolve the DNS name DC2.DOMAIN.com from this computer.
  133.  
  134. [2] FRS is not running on DC2.DOMAIN.com.
  135.  
  136. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
  137.  
  138.  
  139.  
  140. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
  141.  
  142. A warning event occurred. EventID: 0x800034C4
  143.  
  144. Time Generated: 02/12/2013 12:46:53
  145.  
  146. Event String:
  147.  
  148. The File Replication Service is having trouble enabling replication from DC3 to DR for d:\sysvol\domain using the DNS name DC3.DOMAIN.com. FRS will keep retrying.
  149.  
  150. Following are some of the reasons you would see this warning.
  151.  
  152.  
  153.  
  154. [1] FRS can not correctly resolve the DNS name DC3.DOMAIN.com from this computer.
  155.  
  156. [2] FRS is not running on DC3.DOMAIN.com.
  157.  
  158. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
  159.  
  160.  
  161.  
  162. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
  163.  
  164. A warning event occurred. EventID: 0x800034C4
  165.  
  166. Time Generated: 02/12/2013 12:46:53
  167.  
  168. Event String:
  169.  
  170. The File Replication Service is having trouble enabling replication from DC2 to DR for d:\sysvol\domain using the DNS name DC2.DOMAIN.com. FRS will keep retrying.
  171.  
  172. Following are some of the reasons you would see this warning.
  173.  
  174.  
  175.  
  176. [1] FRS can not correctly resolve the DNS name DC2.DOMAIN.com from this computer.
  177.  
  178. [2] FRS is not running on DC2.DOMAIN.com.
  179.  
  180. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
  181.  
  182.  
  183.  
  184. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
  185.  
  186. ......................... DR passed test FrsEvent
  187.  
  188. Starting test: DFSREvent
  189.  
  190. The DFS Replication Event Log.
  191. Skip the test because the server is running FRS.
  192.  
  193. ......................... DR passed test DFSREvent
  194.  
  195. Starting test: SysVolCheck
  196.  
  197. * The File Replication Service SYSVOL ready test
  198. File Replication Service's SYSVOL is ready
  199. ......................... DR passed test SysVolCheck
  200.  
  201. Starting test: KccEvent
  202.  
  203. * The KCC Event log test
  204. A warning event occurred. EventID: 0x8000061E
  205.  
  206. Time Generated: 02/12/2013 14:54:02
  207.  
  208. Event String:
  209.  
  210. All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.
  211.  
  212.  
  213.  
  214. Site:
  215.  
  216. CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  217.  
  218. Directory partition:
  219.  
  220. DC=DOMAIN,DC=com
  221.  
  222. Transport:
  223.  
  224. CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  225.  
  226. An error event occurred. EventID: 0xC000051F
  227.  
  228. Time Generated: 02/12/2013 14:54:02
  229.  
  230. Event String:
  231.  
  232. The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
  233.  
  234.  
  235.  
  236. Directory partition:
  237.  
  238. DC=DOMAIN,DC=com
  239.  
  240.  
  241.  
  242. There is insufficient site connectivity information for the KCC to create a spanning tree replication topology. Or, one or more directory servers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible directory servers.
  243.  
  244.  
  245.  
  246. User Action
  247.  
  248. Perform one of the following actions:
  249.  
  250. - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.
  251.  
  252. - Add a Connection object to a directory service that contains the directory partition in this site from a directory service that contains the same directory partition in another site.
  253.  
  254.  
  255.  
  256. If neither of the tasks correct this condition, see previous events logged by the KCC that identify the inaccessible directory servers.
  257.  
  258. A warning event occurred. EventID: 0x80000749
  259.  
  260. Time Generated: 02/12/2013 14:54:02
  261.  
  262. Event String:
  263.  
  264. The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.
  265.  
  266.  
  267.  
  268. Sites:
  269.  
  270. CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  271.  
  272.  
  273.  
  274.  
  275.  
  276.  
  277.  
  278.  
  279.  
  280.  
  281.  
  282.  
  283.  
  284.  
  285.  
  286. A warning event occurred. EventID: 0x8000061E
  287.  
  288. Time Generated: 02/12/2013 14:54:02
  289.  
  290. Event String:
  291.  
  292. All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.
  293.  
  294.  
  295.  
  296. Site:
  297.  
  298. CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  299.  
  300. Directory partition:
  301.  
  302. DC=DomainDnsZones,DC=DOMAIN,DC=com
  303.  
  304. Transport:
  305.  
  306. CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  307.  
  308. An error event occurred. EventID: 0xC000051F
  309.  
  310. Time Generated: 02/12/2013 14:54:02
  311.  
  312. Event String:
  313.  
  314. The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
  315.  
  316.  
  317.  
  318. Directory partition:
  319.  
  320. DC=DomainDnsZones,DC=DOMAIN,DC=com
  321.  
  322.  
  323.  
  324. There is insufficient site connectivity information for the KCC to create a spanning tree replication topology. Or, one or more directory servers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible directory servers.
  325.  
  326.  
  327.  
  328. User Action
  329.  
  330. Perform one of the following actions:
  331.  
  332. - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.
  333.  
  334. - Add a Connection object to a directory service that contains the directory partition in this site from a directory service that contains the same directory partition in another site.
  335.  
  336.  
  337.  
  338. If neither of the tasks correct this condition, see previous events logged by the KCC that identify the inaccessible directory servers.
  339.  
  340. A warning event occurred. EventID: 0x80000749
  341.  
  342. Time Generated: 02/12/2013 14:54:02
  343.  
  344. Event String:
  345.  
  346. The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.
  347.  
  348.  
  349.  
  350. Sites:
  351.  
  352. CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  353.  
  354.  
  355.  
  356.  
  357.  
  358.  
  359.  
  360.  
  361.  
  362.  
  363.  
  364.  
  365.  
  366.  
  367.  
  368. A warning event occurred. EventID: 0x8000061E
  369.  
  370. Time Generated: 02/12/2013 14:54:02
  371.  
  372. Event String:
  373.  
  374. All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.
  375.  
  376.  
  377.  
  378. Site:
  379.  
  380. CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  381.  
  382. Directory partition:
  383.  
  384. DC=ForestDnsZones,DC=DOMAIN,DC=com
  385.  
  386. Transport:
  387.  
  388. CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  389.  
  390. An error event occurred. EventID: 0xC000051F
  391.  
  392. Time Generated: 02/12/2013 14:54:02
  393.  
  394. Event String:
  395.  
  396. The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
  397.  
  398.  
  399.  
  400. Directory partition:
  401.  
  402. DC=ForestDnsZones,DC=DOMAIN,DC=com
  403.  
  404.  
  405.  
  406. There is insufficient site connectivity information for the KCC to create a spanning tree replication topology. Or, one or more directory servers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible directory servers.
  407.  
  408.  
  409.  
  410. User Action
  411.  
  412. Perform one of the following actions:
  413.  
  414. - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.
  415.  
  416. - Add a Connection object to a directory service that contains the directory partition in this site from a directory service that contains the same directory partition in another site.
  417.  
  418.  
  419.  
  420. If neither of the tasks correct this condition, see previous events logged by the KCC that identify the inaccessible directory servers.
  421.  
  422. A warning event occurred. EventID: 0x80000749
  423.  
  424. Time Generated: 02/12/2013 14:54:02
  425.  
  426. Event String:
  427.  
  428. The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.
  429.  
  430.  
  431.  
  432. Sites:
  433.  
  434. CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  435.  
  436.  
  437.  
  438.  
  439.  
  440.  
  441.  
  442.  
  443.  
  444.  
  445.  
  446.  
  447.  
  448.  
  449.  
  450. A warning event occurred. EventID: 0x8000061E
  451.  
  452. Time Generated: 02/12/2013 14:54:02
  453.  
  454. Event String:
  455.  
  456. All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.
  457.  
  458.  
  459.  
  460. Site:
  461.  
  462. CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  463.  
  464. Directory partition:
  465.  
  466. CN=Configuration,DC=DOMAIN,DC=com
  467.  
  468. Transport:
  469.  
  470. CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  471.  
  472. An error event occurred. EventID: 0xC000051F
  473.  
  474. Time Generated: 02/12/2013 14:54:02
  475.  
  476. Event String:
  477.  
  478. The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
  479.  
  480.  
  481.  
  482. Directory partition:
  483.  
  484. CN=Configuration,DC=DOMAIN,DC=com
  485.  
  486.  
  487.  
  488. There is insufficient site connectivity information for the KCC to create a spanning tree replication topology. Or, one or more directory servers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible directory servers.
  489.  
  490.  
  491.  
  492. User Action
  493.  
  494. Perform one of the following actions:
  495.  
  496. - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.
  497.  
  498. - Add a Connection object to a directory service that contains the directory partition in this site from a directory service that contains the same directory partition in another site.
  499.  
  500.  
  501.  
  502. If neither of the tasks correct this condition, see previous events logged by the KCC that identify the inaccessible directory servers.
  503.  
  504. A warning event occurred. EventID: 0x80000749
  505.  
  506. Time Generated: 02/12/2013 14:54:02
  507.  
  508. Event String:
  509.  
  510. The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.
  511.  
  512.  
  513.  
  514. Sites:
  515.  
  516. CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  517.  
  518.  
  519.  
  520.  
  521.  
  522.  
  523.  
  524.  
  525.  
  526.  
  527.  
  528.  
  529.  
  530.  
  531.  
  532. ......................... DR failed test KccEvent
  533.  
  534. Starting test: KnowsOfRoleHolders
  535.  
  536. Role Schema Owner = CN=NTDS Settings,CN=DR,CN=Servers,CN=office,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  537. Role Domain Owner = CN=NTDS Settings,CN=DR,CN=Servers,CN=office,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  538. Role PDC Owner = CN=NTDS Settings,CN=DC2,CN=Servers,CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  539. Role Rid Owner = CN=NTDS Settings,CN=DC2,CN=Servers,CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  540. Role Infrastructure Update Owner = CN=NTDS Settings,CN=DC2,CN=Servers,CN=production,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  541. ......................... DR passed test KnowsOfRoleHolders
  542.  
  543. Starting test: MachineAccount
  544.  
  545. Checking machine account for DC DR on DC DR.
  546. * SPN found :LDAP/DR.DOMAIN.com/DOMAIN.com
  547. * SPN found :LDAP/DR.DOMAIN.com
  548. * SPN found :LDAP/DR
  549. * SPN found :LDAP/DR.DOMAIN.com/INT
  550. * SPN found :LDAP/39126a95-8c44-484b-9b45-60440dfc8f4c._msdcs.DOMAIN.com
  551. * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/39126a95-8c44-484b-9b45-60440dfc8f4c/DOMAIN.com
  552. * SPN found :HOST/DR.DOMAIN.com/DOMAIN.com
  553. * SPN found :HOST/DR.DOMAIN.com
  554. * SPN found :HOST/DR
  555. * SPN found :HOST/DR.DOMAIN.com/INT
  556. * SPN found :GC/DR.DOMAIN.com/DOMAIN.com
  557. ......................... DR passed test MachineAccount
  558.  
  559. Starting test: NCSecDesc
  560.  
  561. * Security Permissions check for all NC's on DC DR.
  562. * Security Permissions Check for
  563.  
  564. DC=ForestDnsZones,DC=DOMAIN,DC=com
  565. (NDNC,Version 3)
  566. * Security Permissions Check for
  567.  
  568. DC=DomainDnsZones,DC=DOMAIN,DC=com
  569. (NDNC,Version 3)
  570. * Security Permissions Check for
  571.  
  572. CN=Schema,CN=Configuration,DC=DOMAIN,DC=com
  573. (Schema,Version 3)
  574. * Security Permissions Check for
  575.  
  576. CN=Configuration,DC=DOMAIN,DC=com
  577. (Configuration,Version 3)
  578. * Security Permissions Check for
  579.  
  580. DC=DOMAIN,DC=com
  581. (Domain,Version 3)
  582. ......................... DR passed test NCSecDesc
  583.  
  584. Starting test: NetLogons
  585.  
  586. * Network Logons Privileges Check
  587. Verified share \\DR\netlogon
  588. Verified share \\DR\sysvol
  589. ......................... DR passed test NetLogons
  590.  
  591. Starting test: ObjectsReplicated
  592.  
  593. DR is in domain DC=DOMAIN,DC=com
  594. Checking for CN=DR,OU=Domain Controllers,DC=DOMAIN,DC=com in domain DC=DOMAIN,DC=com on 1 servers
  595. Object is up-to-date on all servers.
  596. Checking for CN=NTDS Settings,CN=DR,CN=Servers,CN=office,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com in domain CN=Configuration,DC=DOMAIN,DC=com on 1 servers
  597. Object is up-to-date on all servers.
  598. ......................... DR passed test ObjectsReplicated
  599.  
  600. Test omitted by user request: OutboundSecureChannels
  601.  
  602. Starting test: Replications
  603.  
  604. * Replications Check
  605. [Replications Check,Replications Check] Inbound replication is
  606.  
  607. disabled.
  608.  
  609. To correct, run "repadmin /options DR -DISABLE_INBOUND_REPL"
  610.  
  611. [Replications Check,DR] Outbound replication is disabled.
  612.  
  613. To correct, run "repadmin /options DR -DISABLE_OUTBOUND_REPL"
  614.  
  615. ......................... DR failed test Replications
  616.  
  617. Starting test: RidManager
  618.  
  619. * Available RID Pool for the Domain is 4103 to 1073741823
  620. * DC2.DOMAIN.com is the RID Master
  621. * DsBind with RID Master was successful
  622. * rIDAllocationPool is 3103 to 3602
  623. * rIDPreviousAllocationPool is 3103 to 3602
  624. * rIDNextRID: 3169
  625. ......................... DR passed test RidManager
  626.  
  627. Starting test: Services
  628.  
  629. * Checking Service: EventSystem
  630. * Checking Service: RpcSs
  631. * Checking Service: NTDS
  632. * Checking Service: DnsCache
  633. * Checking Service: DFSR
  634. * Checking Service: IsmServ
  635. * Checking Service: kdc
  636. * Checking Service: SamSs
  637. * Checking Service: LanmanServer
  638. * Checking Service: LanmanWorkstation
  639. * Checking Service: w32time
  640. w32time Service is stopped on [DR]
  641.  
  642. * Checking Service: NETLOGON
  643. ......................... DR failed test Services
  644.  
  645. Starting test: SystemLog
  646.  
  647. * The System Event log test
  648. An error event occurred. EventID: 0x80000003
  649.  
  650. Time Generated: 02/12/2013 14:04:42
  651.  
  652. Event String:
  653.  
  654. A Kerberos Error Message was received:
  655.  
  656. on logon session
  657.  
  658. Client Time:
  659.  
  660. Server Time: 12:4:42.0000 2/12/2013 Z
  661.  
  662. Error Code: 0xd KDC_ERR_BADOPTION
  663.  
  664. Extended Error: 0xc00000bb KLIN(0)
  665.  
  666. Client Realm:
  667.  
  668. Client Name:
  669.  
  670. Server Realm: DOMAIN.COM
  671.  
  672. Server Name: drakh$@DOMAIN.COM
  673.  
  674. Target Name: drakh$@DOMAIN.COM@DOMAIN.COM
  675.  
  676. Error Text:
  677.  
  678. File: 9
  679.  
  680. Line: efb
  681.  
  682. Error Data is in record data.
  683.  
  684. An error event occurred. EventID: 0x80000003
  685.  
  686. Time Generated: 02/12/2013 14:19:43
  687.  
  688. Event String:
  689.  
  690. A Kerberos Error Message was received:
  691.  
  692. on logon session
  693.  
  694. Client Time:
  695.  
  696. Server Time: 12:19:43.0000 2/12/2013 Z
  697.  
  698. Error Code: 0xd KDC_ERR_BADOPTION
  699.  
  700. Extended Error: 0xc00000bb KLIN(0)
  701.  
  702. Client Realm:
  703.  
  704. Client Name:
  705.  
  706. Server Realm: DOMAIN.COM
  707.  
  708. Server Name: drakh$@DOMAIN.COM
  709.  
  710. Target Name: drakh$@DOMAIN.COM@DOMAIN.COM
  711.  
  712. Error Text:
  713.  
  714. File: 9
  715.  
  716. Line: efb
  717.  
  718. Error Data is in record data.
  719.  
  720. An error event occurred. EventID: 0x80000003
  721.  
  722. Time Generated: 02/12/2013 14:34:27
  723.  
  724. Event String:
  725.  
  726. A Kerberos Error Message was received:
  727.  
  728. on logon session DOMAIN.com\itaig_admin
  729.  
  730. Client Time:
  731.  
  732. Server Time: 12:34:27.0000 2/12/2013 Z
  733.  
  734. Error Code: 0x19 KDC_ERR_PREAUTH_REQUIRED
  735.  
  736. Extended Error:
  737.  
  738. Client Realm:
  739.  
  740. Client Name:
  741.  
  742. Server Realm: DOMAIN.com
  743.  
  744. Server Name: krbtgt/DOMAIN.com
  745.  
  746. Target Name: krbtgt/DOMAIN.com@DOMAIN.com
  747.  
  748. Error Text:
  749.  
  750. File: e
  751.  
  752. Line: 9fe
  753.  
  754. Error Data is in record data.
  755.  
  756. An error event occurred. EventID: 0x00000457
  757.  
  758. Time Generated: 02/12/2013 14:34:33
  759.  
  760. Event String:
  761.  
  762. Driver Color MF30-1 PCL6 Mono required for printer !!printsrv-ta01!BLACK is unknown. Contact the administrator to install the driver before you log in again.
  763.  
  764. An error event occurred. EventID: 0x00000457
  765.  
  766. Time Generated: 02/12/2013 14:34:34
  767.  
  768. Event String:
  769.  
  770. Driver Color MF30-1 PCL6 required for printer !!printsrv-ta01!COLOR is unknown. Contact the administrator to install the driver before you log in again.
  771.  
  772. An error event occurred. EventID: 0x00000457
  773.  
  774. Time Generated: 02/12/2013 14:34:34
  775.  
  776. Event String:
  777.  
  778. Driver Send To Microsoft OneNote 2010 Driver required for printer Send To OneNote 2010 is unknown. Contact the administrator to install the driver before you log in again.
  779.  
  780. An error event occurred. EventID: 0x00000457
  781.  
  782. Time Generated: 02/12/2013 14:34:35
  783.  
  784. Event String:
  785.  
  786. Driver Color MF30-1 PCL6 required for printer !!printsrv-ta01!Marketing Printer is unknown. Contact the administrator to install the driver before you log in again.
  787.  
  788. An error event occurred. EventID: 0x00000457
  789.  
  790. Time Generated: 02/12/2013 14:34:39
  791.  
  792. Event String:
  793.  
  794. Driver Color MF30-1 PCL6 required for printer !!PRINTSRV-TA01!CONFROOM RED is unknown. Contact the administrator to install the driver before you log in again.
  795.  
  796. An error event occurred. EventID: 0x80000003
  797.  
  798. Time Generated: 02/12/2013 14:34:43
  799.  
  800. Event String:
  801.  
  802. A Kerberos Error Message was received:
  803.  
  804. on logon session
  805.  
  806. Client Time:
  807.  
  808. Server Time: 12:34:43.0000 2/12/2013 Z
  809.  
  810. Error Code: 0xd KDC_ERR_BADOPTION
  811.  
  812. Extended Error: 0xc00000bb KLIN(0)
  813.  
  814. Client Realm:
  815.  
  816. Client Name:
  817.  
  818. Server Realm: DOMAIN.COM
  819.  
  820. Server Name: drakh$@DOMAIN.COM
  821.  
  822. Target Name: drakh$@DOMAIN.COM@DOMAIN.COM
  823.  
  824. Error Text:
  825.  
  826. File: 9
  827.  
  828. Line: efb
  829.  
  830. Error Data is in record data.
  831.  
  832. An error event occurred. EventID: 0x0000165B
  833.  
  834. Time Generated: 02/12/2013 14:47:15
  835.  
  836. Event String:
  837.  
  838. The session setup from computer 'APP-HANSOLO-LOC' failed because the security database does not contain a trust account 'APP-HANSOLO-LOC$' referenced by the specified computer.
  839.  
  840.  
  841.  
  842. USER ACTION
  843.  
  844. If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. If this is a Read-Only Domain Controller and 'APP-HANSOLO-LOC$' is a legitimate machine account for the computer 'APP-HANSOLO-LOC' then 'APP-HANSOLO-LOC' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem:
  845.  
  846.  
  847.  
  848. If 'APP-HANSOLO-LOC$' is a legitimate machine account for the computer 'APP-HANSOLO-LOC', then 'APP-HANSOLO-LOC' should be rejoined to the domain.
  849.  
  850.  
  851.  
  852. If 'APP-HANSOLO-LOC$' is a legitimate interdomain trust account, then the trust should be recreated.
  853.  
  854.  
  855.  
  856. Otherwise, assuming that 'APP-HANSOLO-LOC$' is not a legitimate account, the following action should be taken on 'APP-HANSOLO-LOC':
  857.  
  858.  
  859.  
  860. If 'APP-HANSOLO-LOC' is a Domain Controller, then the trust associated with 'APP-HANSOLO-LOC$' should be deleted.
  861.  
  862.  
  863.  
  864. If 'APP-HANSOLO-LOC' is not a Domain Controller, it should be disjoined from the domain.
  865.  
  866. A warning event occurred. EventID: 0x8000001C
  867.  
  868. Time Generated: 02/12/2013 14:47:25
  869.  
  870. Event String:
  871.  
  872. When generating a cross realm referal from domain OFFICE.DOMAIN.COM the KDC was not able to find the suitable key to verify the ticket. The ticket key version in the request was 14 and the available key version was 13. This most common reason for this error is a delay in replicating the keys. In order to remove this problem try forcing replication or wait for the replication of keys to occur.
  873.  
  874. An error event occurred. EventID: 0x80000003
  875.  
  876. Time Generated: 02/12/2013 14:49:44
  877.  
  878. Event String:
  879.  
  880. A Kerberos Error Message was received:
  881.  
  882. on logon session
  883.  
  884. Client Time:
  885.  
  886. Server Time: 12:49:44.0000 2/12/2013 Z
  887.  
  888. Error Code: 0xd KDC_ERR_BADOPTION
  889.  
  890. Extended Error: 0xc00000bb KLIN(0)
  891.  
  892. Client Realm:
  893.  
  894. Client Name:
  895.  
  896. Server Realm: DOMAIN.COM
  897.  
  898. Server Name: drakh$@DOMAIN.COM
  899.  
  900. Target Name: drakh$@DOMAIN.COM@DOMAIN.COM
  901.  
  902. Error Text:
  903.  
  904. File: 9
  905.  
  906. Line: efb
  907.  
  908. Error Data is in record data.
  909.  
  910. An error event occurred. EventID: 0x000016AD
  911.  
  912. Time Generated: 02/12/2013 14:50:24
  913.  
  914. Event String:
  915.  
  916. The session setup from the computer APP-HANSOLO-LOC failed to authenticate. The following error occurred:
  917.  
  918. Access is denied.
  919.  
  920. ......................... DR failed test SystemLog
  921.  
  922. Test omitted by user request: Topology
  923.  
  924. Test omitted by user request: VerifyEnterpriseReferences
  925.  
  926. Starting test: VerifyReferences
  927.  
  928. The system object reference (serverReference)
  929.  
  930. CN=DR,OU=Domain Controllers,DC=DOMAIN,DC=com and
  931.  
  932. backlink on
  933.  
  934. CN=DR,CN=Servers,CN=office,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  935.  
  936. are correct.
  937. The system object reference (serverReferenceBL)
  938.  
  939. CN=DR,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=DOMAIN,DC=com
  940.  
  941. and backlink on
  942.  
  943. CN=NTDS Settings,CN=DR,CN=Servers,CN=office,CN=Sites,CN=Configuration,DC=DOMAIN,DC=com
  944.  
  945. are correct.
  946. The system object reference (frsComputerReferenceBL)
  947.  
  948. CN=DR,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=DOMAIN,DC=com
  949.  
  950. and backlink on
  951.  
  952. CN=DR,OU=Domain Controllers,DC=DOMAIN,DC=com are
  953.  
  954. correct.
  955. ......................... DR passed test VerifyReferences
  956.  
  957. Test omitted by user request: VerifyReplicas
  958.  
  959.  
  960. Test omitted by user request: DNS
  961.  
  962. Test omitted by user request: DNS
  963.  
  964.  
  965. Running partition tests on : ForestDnsZones
  966.  
  967. Starting test: CheckSDRefDom
  968.  
  969. ......................... ForestDnsZones passed test CheckSDRefDom
  970.  
  971. Starting test: CrossRefValidation
  972.  
  973. ......................... ForestDnsZones passed test
  974.  
  975. CrossRefValidation
  976.  
  977.  
  978. Running partition tests on : DomainDnsZones
  979.  
  980. Starting test: CheckSDRefDom
  981.  
  982. ......................... DomainDnsZones passed test CheckSDRefDom
  983.  
  984. Starting test: CrossRefValidation
  985.  
  986. ......................... DomainDnsZones passed test
  987.  
  988. CrossRefValidation
  989.  
  990.  
  991. Running partition tests on : Schema
  992.  
  993. Starting test: CheckSDRefDom
  994.  
  995. ......................... Schema passed test CheckSDRefDom
  996.  
  997. Starting test: CrossRefValidation
  998.  
  999. ......................... Schema passed test CrossRefValidation
  1000.  
  1001.  
  1002. Running partition tests on : Configuration
  1003.  
  1004. Starting test: CheckSDRefDom
  1005.  
  1006. ......................... Configuration passed test CheckSDRefDom
  1007.  
  1008. Starting test: CrossRefValidation
  1009.  
  1010. ......................... Configuration passed test CrossRefValidation
  1011.  
  1012.  
  1013. Running partition tests on : int
  1014.  
  1015. Starting test: CheckSDRefDom
  1016.  
  1017. ......................... int passed test CheckSDRefDom
  1018.  
  1019. Starting test: CrossRefValidation
  1020.  
  1021. ......................... int passed test CrossRefValidation
  1022.  
  1023.  
  1024. Running enterprise tests on : DOMAIN.com
  1025.  
  1026. Test omitted by user request: DNS
  1027.  
  1028. Test omitted by user request: DNS
  1029.  
  1030. Starting test: LocatorCheck
  1031.  
  1032. GC Name: \\DR.DOMAIN.com
  1033.  
  1034. Locator Flags: 0xe00031bc
  1035. PDC Name: \\DC2.DOMAIN.com
  1036. Locator Flags: 0xe000337d
  1037. Time Server Name: \\DC2.DOMAIN.com
  1038. Locator Flags: 0xe000337d
  1039. Preferred Time Server Name: \\DC2.DOMAIN.com
  1040. Locator Flags: 0xe000337d
  1041. KDC Name: \\DR.DOMAIN.com
  1042. Locator Flags: 0xe00031bc
  1043. ......................... DOMAIN.com passed test LocatorCheck
  1044.  
  1045. Starting test: Intersite
  1046.  
  1047. Skipping site office, this site is outside the scope provided by the
  1048.  
  1049. command line arguments provided.
  1050. Skipping site production, this site is outside the scope provided by
  1051.  
  1052. the command line arguments provided.
  1053. ......................... DOMAIN.com passed test Intersite
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!