The distributed file system dfs client has been disabled 2008

The error code displayed as a decimal and error description fields further identify the reason for the failure. Evaluate the error code with the list below:. This error code usually indicates that the client computer cannot find the path specified in the event. This failure may be caused by the DFS Client not running. This error code usually indicates that the user or computer does not have the appropriate permissions to access the path specified in the event.

On the domain controller: Ensure the the user and computer have appropriate permission to read the path specified in the event. This error code usually indicates that the computer cannot resolve the name in the provided network path. The second thing you will want to do is take a look at the Event Viewer logs. Check if there are any event logs related to the Journal Wrapping error which was causing File Replication Services to fail on our domain controllers.

You can force the sysvol folder to synchronize from another DC. Use the nslookup and ping utility to check if your DNS server usually this is a domain controller is available and responding. You can find out the name of your domain controller with the command:.

Make sure both commands return a successful response. Try to reset the DNS resolver cache on affected computers:. Check the health of domain controllers and replication in Active Directory.

The RPC server is unavailable. Group Policy. Sign in to vote. I've searched and found problems with DCs but not for DCs. Does anyone have any ideas? Thanks Steve. Friday, July 30, AM. Hi Am I've also seen these instructions, do you not think this might be easier? Monday, August 2, PM. Hi Steve, Just to cover off on some of the basics first under the assumption this is a user configuration policy : Can you run a directory of the UNC you listed? If so, can you use type to display the contents of gpt.

Cheers, Lain. Additional Information: Error: The replicated folder has been offline for too long. Yikes, older than 60 days and nobody had even noticed. I set it to with this command:. It started syncing up and from looking in the Policies folder, I could see more folders turn up, including the original missing one from the gpupdate command. After all that, we tried this and it worked.

Thank you!! This site uses Akismet to reduce spam. Learn how your comment data is processed.