Sysvol replication not working

[JohnnyR1Red]

Hi,

 

I have a domain with 2 2008R2 DCs and 1 2012R2 DC. I noticed yesterday that my group policies were not applying and when I do a gpupdate /force I get replication errors.

 

After a bit of digging it seems that only one of my 2008 servers has anything is sysvol and has a netlogon folder. My 2012 server has nothing either.

 

I can't browse to the sysvol folder from a PC but I can from any server. I am seeing lots of GP errors in event viewer on the servers and PCs

 

This is the PC error:

The processing of Group Policy failed. Windows attempted to read the file \\contorso.local\SysVol\contorso.local\Policies\{597EB0BB-CBEF-4C71-AA2C-C32FCCAA1D07}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:

a) Name Resolution/Network Connectivity to the current domain controller.

b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).

c) The Distributed File System (DFS) client has been disabled.

 

I've checked the firewall settings and it's ok so I'm struggling. I have ran a dcdiag /v /q on all 3 servers and all give errors.

 

This is part of the dcdiag on the server with a working sysvol:

 

 

Anyone able to offer me any help?

[SpaceInvader83]

Network locations aren't messed up are they on the affected servers? Showing as Public instead of Domain?

Have you checked DNS is working correctly? Can clients do an nslookup on the affected servers and return the correct IP and vice versa?

Also probably worth running AD Rep Status Tool - https://www.microsoft.com/en-us/download/details.aspx?id=30005

Edited February 1, 2018 by SpaceInvader83

[JohnnyR1Red]

Network locations aren't messed up are they on the affected servers? Showing as Public instead of Domain?

Have you checked DNS is working correctly? Can clients do an nslookup on the affected servers and return the correct IP and vice versa?

Also probably worth running AD Rep Status Tool - https://www.microsoft.com/en-us/download/details.aspx?id=30005

 

DNS seems to be fine but I will double check this tomorrow, I'm back there in the morning.

 

Cheers