asked on Domain controller not updating SYSVOL
Hi,
I have a network with:
1 x 2012R2 DC
1 x 2008 DC
1 x 2003 DC
The 2003 DC is working fine and is in the process of being retired and will be correctly DCPromo soon.
I am having issues with the 2008 DC though.
The group policy managements is showing that this DC is not in sync and is inaccessbile.
I can browse to the SYSVOL folder of that server from the other DC's.
I have checked the metadata cleanup to make sure there are no old servers lying around and all looks ok.
DCDIAG is fine on both the other servers.
If i run it on the 2008 server i just get FRS events.
thanks
I have a network with:
1 x 2012R2 DC
1 x 2008 DC
1 x 2003 DC
The 2003 DC is working fine and is in the process of being retired and will be correctly DCPromo soon.
I am having issues with the 2008 DC though.
The group policy managements is showing that this DC is not in sync and is inaccessbile.
I can browse to the SYSVOL folder of that server from the other DC's.
I have checked the metadata cleanup to make sure there are no old servers lying around and all looks ok.
DCDIAG is fine on both the other servers.
If i run it on the 2008 server i just get FRS events.
thanks
Windows Server 2008Windows Server 2012Windows Server 2003
Last Comment
timb551
FRS is file replication service which could be why your sysvol is not working. Could you post results of dcdiag?
ASKER
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>dcdiag
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = server2008dc
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: SITE\server2008dc
Starting test: Connectivity
......................... server2008dc passed test Connectivity
Doing primary tests
Testing server: SITE\server2008dc
Starting test: Advertising
......................... server2008dc passed test Advertising
Starting test: CheckSecurityError
[server2008dc] No security related replication errors were found on this
DC! To target the connection to a specific source DC use
/ReplSource:<DC>.
......................... server2008dc passed test CheckSecurityError
Starting test: CutoffServers
......................... server2008dc passed test CutoffServers
Starting test: FrsEvent
......................... server2008dc passed test FrsEvent
Starting test: DFSREvent
......................... server2008dc passed test DFSREvent
Starting test: SysVolCheck
......................... server2008dc passed test SysVolCheck
Starting test: FrsSysVol
......................... server2008dc passed test FrsSysVol
Starting test: KccEvent
......................... server2008dc passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... server2008dc passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... server2008dc passed test MachineAccount
Starting test: NCSecDesc
......................... server2008dc passed test NCSecDesc
Starting test: NetLogons
......................... server2008dc passed test NetLogons
Starting test: ObjectsReplicated
......................... server2008dc passed test ObjectsReplicated
Starting test: OutboundSecureChannels
** Did not run Outbound Secure Channels test because /testdomain: was
not entered
......................... server2008dc passed test OutboundSecureChannels
Starting test: Replications
......................... server2008dc passed test Replications
Starting test: RidManager
......................... server2008dc passed test RidManager
Starting test: Services
......................... server2008dc passed test Services
Starting test: SystemLog
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 11:57:14
Event String:
DCOM was unable to communicate with the computer serverDC03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 11:57:14
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:02:14
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:02:14
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:07:16
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:07:16
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:12:18
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:12:18
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:17:18
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:17:18
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:22:20
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:22:20
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:27:22
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:27:22
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:32:22
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:32:22
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0x40000004
Time Generated: 07/20/2015 12:34:55
Event String:
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the se
rver pc-026$. The target name used was cifs/pc-010.domain.local. This indicate
s that the target server failed to decrypt the ticket provided by the client. Th
is can occur when the target server principal name (SPN) is registered on an acc
ount other than the account the target service is using. Please ensure that the
target SPN is registered on, and only registered on, the account used by the ser
ver. This error can also happen when the target service is using a different pas
sword for the target service account than what the Kerberos Key Distribution Cen
ter (KDC) has for the target service account. Please ensure that the service on
the server and the KDC are both updated to use the current password. If the serv
er name is not fully qualified, and the target domain (domain.local) is different
from the client domain (domain.local), check if there are identically named server
accounts in these two domains, or use the fully-qualified name to identify the
server.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:37:24
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local
al using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:37:24
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0x00009017
Time Generated: 07/20/2015 12:42:00
Event String: The following fatal alert was received: 42.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:42:24
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:42:24
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:47:26
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:47:26
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:52:30
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:52:30
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
......................... server2008dc failed test SystemLog
Starting test: Topology
......................... server2008dc passed test Topology
Starting test: VerifyEnterpriseReferences
......................... server2008dc passed test
VerifyEnterpriseReferences
Starting test: VerifyReferences
......................... server2008dc passed test VerifyReferences
Starting test: VerifyReplicas
......................... server2008dc passed test VerifyReplicas
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... server2008dc passed test DNS
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : domain
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Running enterprise tests on : domain.local
Starting test: DNS
......................... domain.local passed test DNS
Starting test: LocatorCheck
......................... domain.local passed test LocatorCheck
Starting test: FsmoCheck
......................... domain.local passed test FsmoCheck
Starting test: Intersite
......................... domain.local passed test Intersite
C:\Windows\system32>
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>dcdiag
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = server2008dc
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: SITE\server2008dc
Starting test: Connectivity
......................... server2008dc passed test Connectivity
Doing primary tests
Testing server: SITE\server2008dc
Starting test: Advertising
......................... server2008dc passed test Advertising
Starting test: CheckSecurityError
[server2008dc] No security related replication errors were found on this
DC! To target the connection to a specific source DC use
/ReplSource:<DC>.
......................... server2008dc passed test CheckSecurityError
Starting test: CutoffServers
......................... server2008dc passed test CutoffServers
Starting test: FrsEvent
......................... server2008dc passed test FrsEvent
Starting test: DFSREvent
......................... server2008dc passed test DFSREvent
Starting test: SysVolCheck
......................... server2008dc passed test SysVolCheck
Starting test: FrsSysVol
......................... server2008dc passed test FrsSysVol
Starting test: KccEvent
......................... server2008dc passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... server2008dc passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... server2008dc passed test MachineAccount
Starting test: NCSecDesc
......................... server2008dc passed test NCSecDesc
Starting test: NetLogons
......................... server2008dc passed test NetLogons
Starting test: ObjectsReplicated
......................... server2008dc passed test ObjectsReplicated
Starting test: OutboundSecureChannels
** Did not run Outbound Secure Channels test because /testdomain: was
not entered
......................... server2008dc passed test OutboundSecureChannels
Starting test: Replications
......................... server2008dc passed test Replications
Starting test: RidManager
......................... server2008dc passed test RidManager
Starting test: Services
......................... server2008dc passed test Services
Starting test: SystemLog
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 11:57:14
Event String:
DCOM was unable to communicate with the computer serverDC03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 11:57:14
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:02:14
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:02:14
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:07:16
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:07:16
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:12:18
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:12:18
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:17:18
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:17:18
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:22:20
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:22:20
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:27:22
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:27:22
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:32:22
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:32:22
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0x40000004
Time Generated: 07/20/2015 12:34:55
Event String:
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the se
rver pc-026$. The target name used was cifs/pc-010.domain.local. This indicate
s that the target server failed to decrypt the ticket provided by the client. Th
is can occur when the target server principal name (SPN) is registered on an acc
ount other than the account the target service is using. Please ensure that the
target SPN is registered on, and only registered on, the account used by the ser
ver. This error can also happen when the target service is using a different pas
sword for the target service account than what the Kerberos Key Distribution Cen
ter (KDC) has for the target service account. Please ensure that the service on
the server and the KDC are both updated to use the current password. If the serv
er name is not fully qualified, and the target domain (domain.local) is different
from the client domain (domain.local), check if there are identically named server
accounts in these two domains, or use the fully-qualified name to identify the
server.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:37:24
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local
al using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:37:24
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0x00009017
Time Generated: 07/20/2015 12:42:00
Event String: The following fatal alert was received: 42.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:42:24
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:42:24
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:47:26
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:47:26
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:52:30
Event String:
DCOM was unable to communicate with the computer serverdc03.domain.local
using any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 07/20/2015 12:52:30
Event String:
DCOM was unable to communicate with the computer serverHYPV01.domain.local using any of the configured protocols.
......................... server2008dc failed test SystemLog
Starting test: Topology
......................... server2008dc passed test Topology
Starting test: VerifyEnterpriseReferences
......................... server2008dc passed test
VerifyEnterpriseReferences
Starting test: VerifyReferences
......................... server2008dc passed test VerifyReferences
Starting test: VerifyReplicas
......................... server2008dc passed test VerifyReplicas
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... server2008dc passed test DNS
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : domain
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Running enterprise tests on : domain.local
Starting test: DNS
......................... domain.local passed test DNS
Starting test: LocatorCheck
......................... domain.local passed test LocatorCheck
Starting test: FsmoCheck
......................... domain.local passed test FsmoCheck
Starting test: Intersite
......................... domain.local passed test Intersite
C:\Windows\system32>
Cna you login to the 2008R2 DC and open a command prompt and then type net share make sure that they are shared out. Also check the Directory Service Logs on this DC specifically.
Will.
Will.
ASKER
The share in there in net share
I checked the logs and there is nothing from that last week but there was this from a week ago.
This is the replication status for the following directory partition on this directory server.
Directory partition:
CN=Schema,CN=Configuration
This directory server has not received replication information from a number of directory servers within the configured latency interval.
Latency Interval (Hours):
24
Number of directory servers in all sites:
1
Number of directory servers in this site:
1
The latency interval can be modified with the following registry key.
Registry Key:
HKLM\System\CurrentControl
To identify the directory servers by name, use the dcdiag.exe tool.
You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
I checked the logs and there is nothing from that last week but there was this from a week ago.
This is the replication status for the following directory partition on this directory server.
Directory partition:
CN=Schema,CN=Configuration
This directory server has not received replication information from a number of directory servers within the configured latency interval.
Latency Interval (Hours):
24
Number of directory servers in all sites:
1
Number of directory servers in this site:
1
The latency interval can be modified with the following registry key.
Registry Key:
HKLM\System\CurrentControl
To identify the directory servers by name, use the dcdiag.exe tool.
You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Found solutions and posted link.