Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
DFS could not access its private data from the Active Directory. Please manually check network connectivity security access and/or consistency of DFS information in the Active Directory. This error occurred on root <root>.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is DFS?
The first step in troubleshooting this is to verify if the DNS is properly configured. Other useful troubleshooting recommendations:
- EV100494 (Top 10 Common Causes of Slow Replication with DFSR)
- T962143 (Supporting Dfs - includes troubleshooting and tools)
- ME975440 (How to troubleshoot Distributed File System Namespace)
- EV100495 (DFS Replication Troubleshooting)
- EV100496 (Five ways to check your DFS-Namespaces)
One user reported this problem fixed by a server reboot.
If the DFS root that’s listed in the event details does not exist in the Active Directory ("AD Users & Computers\System\Dfs-Configuration") then go to “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dfs\Roots” and find the domain or standalone root that's causing you problems and delete the respective key. Restart DFS Service for the action to take effect.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated