Hi Daisy, by "it did not work" I mean that when I shut down DC1, the DC2 does not authenticate when I try to login to domain as well as I cant browse the internet. I need to bring back DC1 so I can work. Also, as I said, issuing nslookup against DC2 always errors and responds with unknown.
Here is the output of repadmin /showrepl > C:\rep1.txt which indicates everything is successful
Repadmin: running command /showrepl against full DC localhost Default-First-Site-Name\SALAMMAIN-DC02 DSA Options: IS_GC Site Options: (none) DSA object GUID: f6f0aec0-7246-4cf6-92bf-891f95e53242 DSA invocationID: c122370e-3bdd-4b72-bc4c-cd97ecac5743 ==== INBOUND NEIGHBORS ====================================== DC=salam,DC=net Default-First-Site-Name\SALAMMAIN via RPC DSA object GUID: 29c8443d-0f97-4f29-8027-3e1a00a62d07 Last attempt @ 2024-03-06 09:37:18 was successful. CN=Configuration,DC=salam,DC=net Default-First-Site-Name\SALAMMAIN via RPC DSA object GUID: 29c8443d-0f97-4f29-8027-3e1a00a62d07 Last attempt @ 2024-03-05 22:50:17 was successful.
CN=Schema,CN=Configuration,DC=salam,DC=net Default-First-Site-Name\SALAMMAIN via RPC DSA object GUID: 29c8443d-0f97-4f29-8027-3e1a00a62d07 Last attempt @ 2024-03-05 22:50:17 was successful.
DC=DomainDnsZones,DC=salam,DC=net Default-First-Site-Name\SALAMMAIN via RPC DSA object GUID: 29c8443d-0f97-4f29-8027-3e1a00a62d07 Last attempt @ 2024-03-06 09:37:00 was successful. DC=ForestDnsZones,DC=salam,DC=net Default-First-Site-Name\SALAMMAIN via RPC DSA object GUID: 29c8443d-0f97-4f29-8027-3e1a00a62d07 Last attempt @ 2024-03-05 22:50:18 was successful.
Output for repadmin /showrepl * /csv >c:\repsum.csv
howrepl_COLUMNS,Destination DSA Site,Destination DSA,Naming Context,Source DSA Site,Source DSA,Transport Type,Number of Failures,Last Failure Time,Last Success Time,Last Failure Status
showrepl_INFO,Default-First-Site-Name,SALAMMAIN,"DC=salam,DC=net",Default-First-Site-Name,SALAMMAIN-DC02,RPC,0,0,2024-03-06 09:37:14,0
showrepl_INFO,Default-First-Site-Name,SALAMMAIN,"CN=Configuration,DC=salam,DC=net",Default-First-Site-Name,SALAMMAIN-DC02,RPC,0,0,2024-03-06 09:38:46,0
showrepl_INFO,Default-First-Site-Name,SALAMMAIN,"CN=Schema,CN=Configuration,DC=salam,DC=net",Default-First-Site-Name,SALAMMAIN-DC02,RPC,1,2024-03-06 09:23:26,2024-03-05 22:53:15,8524
showrepl_INFO,Default-First-Site-Name,SALAMMAIN,"DC=DomainDnsZones,DC=salam,DC=net",Default-First-Site-Name,SALAMMAIN-DC02,RPC,0,0,2024-03-06 09:45:17,0
showrepl_INFO,Default-First-Site-Name,SALAMMAIN,"DC=ForestDnsZones,DC=salam,DC=net",Default-First-Site-Name,SALAMMAIN-DC02,RPC,0,0,2024-03-06 09:45:14,0
showrepl_INFO,Default-First-Site-Name,SALAMMAIN-DC02,"DC=salam,DC=net",Default-First-Site-Name,SALAMMAIN,RPC,0,0,2024-03-06 09:44:30,0
showrepl_INFO,Default-First-Site-Name,SALAMMAIN-DC02,"CN=Configuration,DC=salam,DC=net",Default-First-Site-Name,SALAMMAIN,RPC,0,0,2024-03-06 09:38:31,0
showrepl_INFO,Default-First-Site-Name,SALAMMAIN-DC02,"CN=Schema,CN=Configuration,DC=salam,DC=net",Default-First-Site-Name,SALAMMAIN,RPC,0,0,2024-03-06 09:38:32,0
showrepl_INFO,Default-First-Site-Name,SALAMMAIN-DC02,"DC=DomainDnsZones,DC=salam,DC=net",Default-First-Site-Name,SALAMMAIN,RPC,0,0,2024-03-06 09:45:02,0
showrepl_INFO,Default-First-Site-Name,SALAMMAIN-DC02,"DC=ForestDnsZones,DC=salam,DC=net",Default-First-Site-Name,SALAMMAIN,RPC,0,0,2024-03-06 09:44:59,0
However, for repadmin /replsum >C:\rep2.txt, it indicates 1 fail out of 5 operations
Replication Summary Start Time: 2024-03-06 09:45:18 Beginning data collection for replication summary, this may take awhile: .....
Source DSA largest delta fails/total %% error SALAMMAIN 06m:47s 0 / 5 0 SALAMMAIN-DC02 10h:52m:03s 1 / 5 20 (8524) The DSA operation is unable to proceed because of a DNS lookup failure.
Destination DSA largest delta fails/total %% error SALAMMAIN 10h:52m:03s 1 / 5 20 (8524) The DSA operation is unable to proceed because of a DNS lookup failure. SALAMMAIN-DC02 06m:47s 0 / 5 0
For dcdiag /v, most test tests are passed except a couple of warninings/errors regarding sysvol ()
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
* Verifying that the local machine salammain-dc02, is a Directory Server.
Home Server = salammain-dc02
* Connecting to directory service on server salammain-dc02.
* Identified AD Forest.
Collecting AD specific global data
* Collecting site info.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=salam,DC=net,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
The previous call succeeded
Iterating through the sites
Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=salam,DC=net
Getting ISTG and options for the site
* Identifying all servers.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=salam,DC=net,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
The previous call succeeded....
The previous call succeeded
Iterating through the list of servers
Getting information for the server CN=NTDS Settings,CN=SALAMMAIN,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=salam,DC=net
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
Getting information for the server CN=NTDS Settings,CN=SALAMMAIN-DC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=salam,DC=net
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SALAMMAIN-DC02
Starting test: Connectivity
\* Active Directory LDAP Services Check
Determining IP4 connectivity
\* Active Directory RPC Services Check
......................... SALAMMAIN-DC02 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SALAMMAIN-DC02
Starting test: Advertising
Warning: DsGetDcName returned information for \\SALAMMAIN.salam.net,
when we were trying to reach SALAMMAIN-DC02.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
......................... SALAMMAIN-DC02 failed test Advertising
Test omitted by user request: CheckSecurityError
Test omitted by user request: CutoffServers
Starting test: FrsEvent
\* The File Replication Service Event log test
Skip the test because the server is running DFSR.
......................... SALAMMAIN-DC02 passed test FrsEvent
Starting test: DFSREvent
The DFS Replication Event Log.
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.
A warning event occurred. EventID: 0x80001396
Time Generated: 03/05/2024 14:58:55
Event String:
The DFS Replication service is stopping communication with partner SALAMMAIN for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 1722 (The RPC server is unavailable.)
Connection ID: C79DEF37-01A2-4594-BDAE-10D9E403AEC3
Replication Group ID: 7DCB147C-6418-4860-A791-5A65EFA40277
An error event occurred. EventID: 0xC000138A
Time Generated: 03/05/2024 14:59:09
Event String:
The DFS Replication service encountered an error communicating with partner SALAMMAIN for replication group Domain System Volume.
Partner DNS address: SALAMMAIN.salam.net
Optional data if available:
Partner WINS Address: SALAMMAIN
Partner IP Address: 192.168.1.13
The service will retry the connection periodically.
Additional Information:
Error: 1825 (A security package specific error occurred.)
Connection ID: C79DEF37-01A2-4594-BDAE-10D9E403AEC3
Replication Group ID: 7DCB147C-6418-4860-A791-5A65EFA40277
An error event occurred. EventID: 0xC0001204
Time Generated: 03/05/2024 14:59:09
Event String:
The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner SALAMMAIN.salam.net. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
Additional Information:
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: 82E8AEE2-1577-4FBD-A5B3-2564BEFABB9F
Replication Group Name: Domain System Volume
Replication Group ID: C79DEF37-01A2-4594-BDAE-10D9E403AEC3
Member ID: FBB5D769-3E8B-4FCA-9C84-D6C1AD6CC205
Read-Only: 0
An error event occurred. EventID: 0xC000138A
Time Generated: 03/05/2024 15:07:26
Event String:
The DFS Replication service encountered an error communicating with partner SALAMMAIN for replication group Domain System Volume.
Partner DNS address: SALAMMAIN.salam.net
Optional data if available:
Partner WINS Address: SALAMMAIN
Partner IP Address: 192.168.1.13
The service will retry the connection periodically.
Additional Information:
Error: 1825 (A security package specific error occurred.)
Connection ID: C79DEF37-01A2-4594-BDAE-10D9E403AEC3
Replication Group ID: 7DCB147C-6418-4860-A791-5A65EFA40277
An error event occurred. EventID: 0xC0001204
Time Generated: 03/05/2024 15:07:26
Event String:
The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner SALAMMAIN.salam.net. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
Additional Information:
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: 82E8AEE2-1577-4FBD-A5B3-2564BEFABB9F
Replication Group Name: Domain System Volume
Replication Group ID: C79DEF37-01A2-4594-BDAE-10D9E403AEC3
Member ID: FBB5D769-3E8B-4FCA-9C84-D6C1AD6CC205
Read-Only: 0
A warning event occurred. EventID: 0x80001396
Time Generated: 03/05/2024 16:24:32
Event String:
The DFS Replication service is stopping communication with partner SALAMMAIN for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 1722 (The RPC server is unavailable.)
Connection ID: 2CDB071D-6CCC-4ACF-8995-A9EF756260C7
Replication Group ID: 7DCB147C-6418-4860-A791-5A65EFA40277
An error event occurred. EventID: 0xC0001390
Time Generated: 03/05/2024 16:27:35
Event String:
The DFS Replication service failed to communicate with partner SALAMMAIN for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.
Partner DNS Address: SALAMMAIN.salam.net
Optional data if available:
Partner WINS Address: SALAMMAIN
Partner IP Address: 192.168.1.13
The service will retry the connection periodically.
Additional Information:
Error: 1722 (The RPC server is unavailable.)
Connection ID: 2CDB071D-6CCC-4ACF-8995-A9EF756260C7
Replication Group ID: 7DCB147C-6418-4860-A791-5A65EFA40277
An error event occurred. EventID: 0xC0001204
Time Generated: 03/05/2024 16:27:35
Event String:
The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner SALAMMAIN.salam.net. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
Additional Information:
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: 82E8AEE2-1577-4FBD-A5B3-2564BEFABB9F
Replication Group Name: Domain System Volume
Replication Group ID: 2CDB071D-6CCC-4ACF-8995-A9EF756260C7
Member ID: FBB5D769-3E8B-4FCA-9C84-D6C1AD6CC205
Read-Only: 0
An error event occurred. EventID: 0xC0001390
Time Generated: 03/05/2024 16:34:23
Event String:
The DFS Replication service failed to communicate with partner SALAMMAIN for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.
Partner DNS Address: SALAMMAIN.salam.net
Optional data if available:
Partner WINS Address: SALAMMAIN
Partner IP Address: 192.168.1.13
The service will retry the connection periodically.
Additional Information:
Error: 1722 (The RPC server is unavailable.)
Connection ID: 2CDB071D-6CCC-4ACF-8995-A9EF756260C7
Replication Group ID: 7DCB147C-6418-4860-A791-5A65EFA40277
An error event occurred. EventID: 0xC0001204
Time Generated: 03/05/2024 16:34:23
Event String:
The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner SALAMMAIN.salam.net. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
Additional Information:
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: 82E8AEE2-1577-4FBD-A5B3-2564BEFABB9F
Replication Group Name: Domain System Volume
Replication Group ID: 2CDB071D-6CCC-4ACF-8995-A9EF756260C7
Member ID: FBB5D769-3E8B-4FCA-9C84-D6C1AD6CC205
Read-Only: 0
An error event occurred. EventID: 0xC0001390
Time Generated: 03/05/2024 16:50:45
Event String:
The DFS Replication service failed to communicate with partner SALAMMAIN for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.
Partner DNS Address: SALAMMAIN.salam.net
Optional data if available:
Partner WINS Address: SALAMMAIN
Partner IP Address: 192.168.1.13
The service will retry the connection periodically.
Additional Information:
Error: 1722 (The RPC server is unavailable.)
Connection ID: 2CDB071D-6CCC-4ACF-8995-A9EF756260C7
Replication Group ID: 7DCB147C-6418-4860-A791-5A65EFA40277
An error event occurred. EventID: 0xC0001204
Time Generated: 03/05/2024 16:50:45
Event String:
The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner SALAMMAIN.salam.net. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
Additional Information:
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: 82E8AEE2-1577-4FBD-A5B3-2564BEFABB9F
Replication Group Name: Domain System Volume
Replication Group ID: 2CDB071D-6CCC-4ACF-8995-A9EF756260C7
Member ID: FBB5D769-3E8B-4FCA-9C84-D6C1AD6CC205
Read-Only: 0
An error event occurred. EventID: 0xC0001390
Time Generated: 03/05/2024 17:53:28
Event String:
The DFS Replication service failed to communicate with partner SALAMMAIN for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.
Partner DNS Address: SALAMMAIN.salam.net
Optional data if available:
Partner WINS Address: SALAMMAIN
Partner IP Address: 192.168.1.13
The service will retry the connection periodically.
Additional Information:
Error: 1722 (The RPC server is unavailable.)
Connection ID: 2CDB071D-6CCC-4ACF-8995-A9EF756260C7
Replication Group ID: 7DCB147C-6418-4860-A791-5A65EFA40277
An error event occurred. EventID: 0xC0001204
Time Generated: 03/05/2024 17:53:28
Event String:
The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner SALAMMAIN.salam.net. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
Additional Information:
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: 82E8AEE2-1577-4FBD-A5B3-2564BEFABB9F
Replication Group Name: Domain System Volume
Replication Group ID: 2CDB071D-6CCC-4ACF-8995-A9EF756260C7
Member ID: FBB5D769-3E8B-4FCA-9C84-D6C1AD6CC205
Read-Only: 0
A warning event occurred. EventID: 0x80001396
Time Generated: 03/06/2024 09:37:57
Event String:
The DFS Replication service is stopping communication with partner SALAMMAIN for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 1726 (The remote procedure call failed.)
Connection ID: 2CDB071D-6CCC-4ACF-8995-A9EF756260C7
Replication Group ID: 7DCB147C-6418-4860-A791-5A65EFA40277
......................... SALAMMAIN-DC02 failed test DFSREvent
Starting test: SysVolCheck
\* The File Replication Service SYSVOL ready test
The registry lookup failed to determine the state of the SYSVOL. The
error returned was 0x0 "The operation completed successfully.".
Check the FRS event log to see if the SYSVOL has successfully been
shared.
......................... SALAMMAIN-DC02 passed test SysVolCheck
Starting test: KccEvent
\* The KCC Event log test
Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
......................... SALAMMAIN-DC02 passed test KccEvent
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=SALAMMAIN,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=salam,DC=net
Role Domain Owner = CN=NTDS Settings,CN=SALAMMAIN,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=salam,DC=net
Role PDC Owner = CN=NTDS Settings,CN=SALAMMAIN,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=salam,DC=net
Role Rid Owner = CN=NTDS Settings,CN=SALAMMAIN,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=salam,DC=net
Role Infrastructure Update Owner = CN=NTDS Settings,CN=SALAMMAIN,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=salam,DC=net
......................... SALAMMAIN-DC02 passed test
KnowsOfRoleHolders
Starting test: MachineAccount
Checking machine account for DC SALAMMAIN-DC02 on DC SALAMMAIN-DC02.
\* SPN found :LDAP/salammain-dc02.salam.net/salam.net
\* SPN found :LDAP/salammain-dc02.salam.net
\* SPN found :LDAP/SALAMMAIN-DC02
\* SPN found :LDAP/salammain-dc02.salam.net/SALAM
\* SPN found :LDAP/f6f0aec0-7246-4cf6-92bf-891f95e53242.\_msdcs.salam.net
\* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/f6f0aec0-7246-4cf6-92bf-891f95e53242/salam.net
\* SPN found :HOST/salammain-dc02.salam.net/salam.net
\* SPN found :HOST/salammain-dc02.salam.net
\* SPN found :HOST/SALAMMAIN-DC02
\* SPN found :HOST/salammain-dc02.salam.net/SALAM
\* SPN found :GC/salammain-dc02.salam.net/salam.net
......................... SALAMMAIN-DC02 passed test MachineAccount
Starting test: NCSecDesc
\* Security Permissions check for all NC's on DC SALAMMAIN-DC02.
\* Security Permissions Check for
DC=ForestDnsZones,DC=salam,DC=net
(NDNC,Version 3)
\* Security Permissions Check for
DC=DomainDnsZones,DC=salam,DC=net
(NDNC,Version 3)
\* Security Permissions Check for
CN=Schema,CN=Configuration,DC=salam,DC=net
(Schema,Version 3)
\* Security Permissions Check for
CN=Configuration,DC=salam,DC=net
(Configuration,Version 3)
\* Security Permissions Check for
DC=salam,DC=net
(Domain,Version 3)
......................... SALAMMAIN-DC02 passed test NCSecDesc
Starting test: NetLogons
\* Network Logons Privileges Check
Unable to connect to the NETLOGON share! (\\SALAMMAIN-DC02\netlogon)
[SALAMMAIN-DC02] An net use or LsaPolicy operation failed with error
67, The network name cannot be found..
......................... SALAMMAIN-DC02 failed test NetLogons
Starting test: ObjectsReplicated
SALAMMAIN-DC02 is in domain DC=salam,DC=net
Checking for CN=SALAMMAIN-DC02,OU=Domain Controllers,DC=salam,DC=net in domain DC=salam,DC=net on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=SALAMMAIN-DC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=salam,DC=net in domain CN=Configuration,DC=salam,DC=net on 1 servers
Object is up-to-date on all servers.
......................... SALAMMAIN-DC02 passed test ObjectsReplicated
Test omitted by user request: OutboundSecureChannels
Starting test: Replications
\* Replications Check
\* Replication Latency Check
DC=ForestDnsZones,DC=salam,DC=net
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=DomainDnsZones,DC=salam,DC=net
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Schema,CN=Configuration,DC=salam,DC=net
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Configuration,DC=salam,DC=net
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=salam,DC=net
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
......................... SALAMMAIN-DC02 passed test Replications
Starting test: RidManager
\* Available RID Pool for the Domain is 2600 to 1073741823
\* SALAMMAIN.salam.net is the RID Master
\* DsBind with RID Master was successful
\* rIDAllocationPool is 2100 to 2599
\* rIDPreviousAllocationPool is 2100 to 2599
\* rIDNextRID: 2100
......................... SALAMMAIN-DC02 passed test RidManager
Starting test: Services
\* Checking Service: EventSystem
\* Checking Service: RpcSs
\* Checking Service: NTDS
\* Checking Service: DnsCache
\* Checking Service: DFSR
\* Checking Service: IsmServ
\* Checking Service: kdc
\* Checking Service: SamSs
\* Checking Service: LanmanServer
\* Checking Service: LanmanWorkstation
\* Checking Service: w32time
\* Checking Service: NETLOGON
......................... SALAMMAIN-DC02 passed test Services
Starting test: SystemLog
\* The System Event log test
A warning event occurred. EventID: 0x00000024
Time Generated: 03/06/2024 09:36:41
Event String:
The time service has not synchronized the system time for the last 38010 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients after 60429 seconds. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization. You can control the frequency of the time source rediscovery using ClockHoldoverPeriod W32time config setting. Modify the EventLogFlags W32time config setting if you wish to disable this message.
A warning event occurred. EventID: 0x00000081
Time Generated: 03/06/2024 09:36:43
Event String:
NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: The entry is not found. (0x800706E1)
A warning event occurred. EventID: 0x00000081
Time Generated: 03/06/2024 09:37:25
Event String:
NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: The entry is not found. (0x800706E1)
Found no
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
