Advertisement
Guest User

Untitled

a guest
Nov 25th, 2014
147
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.92 KB | None | 0 0
  1. Directory Server Diagnosis
  2.  
  3. Performing initial setup:
  4. Trying to find home server...
  5. Home Server = AOBVADC002
  6. * Identified AD Forest.
  7. Done gathering initial info.
  8.  
  9. Doing initial required tests
  10.  
  11. Testing server: Col-DCAOBVADC002
  12. Starting test: Connectivity
  13. ......................... AOBVADC002 passed test Connectivity
  14.  
  15. Doing primary tests
  16.  
  17. Testing server: Col-DCAOBVADC002
  18. Starting test: Advertising
  19. ......................... AOBVADC002 passed test Advertising
  20. Starting test: FrsEvent
  21. There are warning or error events within the last 24 hours after the
  22. SYSVOL has been shared. Failing SYSVOL replication problems may cause
  23. Group Policy problems.
  24. Starting test: SystemLog
  25. Contact the administrator to install the driver before you log in again.
  26. A warning event occurred. EventID: 0x000016AF
  27. Time Generated: 11/25/2014 08:15:40
  28. Event String:
  29. During the past 4.24 hours there have been 145 connections to this D
  30. omain Controller from client machines whose IP addresses don't map to any of the
  31. existing sites in the enterprise. Those clients, therefore, have undefined site
  32. s and may connect to any Domain Controller including those that are in far dista
  33. nt locations from the clients. A client's site is determined by the mapping of i
  34. ts subnet to one of the existing sites. To move the above clients to one of the
  35. sites, please consider creating subnet object(s) covering the above IP addresses
  36. with mapping to one of the existing sites. The names and IP addresses of the c
  37. lients in question have been logged on this computer in the following log file '
  38. %SystemRoot%debugnetlogon.log' and, potentially, in the log file '%SystemRoot%
  39. debugnetlogon.bak' created if the former log becomes full. The log(s) may cont
  40. ain additional unrelated debugging information. To filter out the needed informa
  41. tion, please search for lines which contain text 'NO_CLIENT_SITE:'. The first wo
  42. rd after this string is the client name and the second word is the client IP add
  43. ress. The maximum size of the log(s) is controlled by the following registry DWO
  44. RD value 'HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNetlogonParamete
  45. rsLogFileMaxSize'; the default is 20000000 bytes. The current maximum size is
  46. 20000000 bytes. To set a different maximum size, create the above registry valu
  47. e and set the desired maximum size in bytes.
  48. ......................... AOBVADC002 failed test SystemLog
  49.  
  50. irectory Server Diagnosis
  51.  
  52. Performing initial setup:
  53. Trying to find home server...
  54. Home Server = AOBVADC002
  55. * Identified AD Forest.
  56. Done gathering initial info.
  57.  
  58. Doing initial required tests
  59.  
  60. Testing server: Col-DCAOBVADC002
  61. Starting test: Connectivity
  62. ......................... AOBVADC002 passed test Connectivity
  63.  
  64. Doing primary tests
  65.  
  66. Testing server: Col-DCAOBVADC002
  67. Starting test: Advertising
  68. ......................... AOBVADC002 passed test Advertising
  69. Starting test: FrsEvent
  70. There are warning or error events within the last 24 hours after the
  71. SYSVOL has been shared. Failing SYSVOL replication problems may cause
  72. Group Policy problems.
  73. Starting test: SystemLog
  74. Contact the administrator to install the driver before you log in again.
  75. A warning event occurred. EventID: 0x000016AF
  76. Time Generated: 11/25/2014 08:15:40
  77. Event String:
  78. During the past 4.24 hours there have been 145 connections to this D
  79. omain Controller from client machines whose IP addresses don't map to any of the
  80. existing sites in the enterprise. Those clients, therefore, have undefined site
  81. s and may connect to any Domain Controller including those that are in far dista
  82. nt locations from the clients. A client's site is determined by the mapping of i
  83. ts subnet to one of the existing sites. To move the above clients to one of the
  84. sites, please consider creating subnet object(s) covering the above IP addresses
  85. with mapping to one of the existing sites. The names and IP addresses of the c
  86. lients in question have been logged on this computer in the following log file '
  87. %SystemRoot%debugnetlogon.log' and, potentially, in the log file '%SystemRoot%
  88. debugnetlogon.bak' created if the former log becomes full. The log(s) may cont
  89. ain additional unrelated debugging information. To filter out the needed informa
  90. tion, please search for lines which contain text 'NO_CLIENT_SITE:'. The first wo
  91. rd after this string is the client name and the second word is the client IP add
  92. ress. The maximum size of the log(s) is controlled by the following registry DWO
  93. RD value 'HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNetlogonParamete
  94. rsLogFileMaxSize'; the default is 20000000 bytes. The current maximum size is
  95. 20000000 bytes. To set a different maximum size, create the above registry valu
  96. e and set the desired maximum size in bytes.
  97. ......................... AOBVADC002 failed test SystemLog
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement