This object monitors the ability of DFS Namespaces to communicate with Active Directory domain controllers by looking for the presence of DfsSvc event 14523 in the System log.
The DFS Namespace service failed to contact a domain controller. This can occur for many reasons including:
Network connectivity issues
No domain controllers are currently available
To test network connectivity with the affected server, use the following procedure:
1. Open a command prompt window and then use the ping command to check basic network connectivity. If the ping command fails, it is likely that the server is not running, or has network problems that require local access to resolve. If Ping is blocked in your network environment, skip this step.
2. If the ping command is successful, test the server’s registration in DNS by using the nslookup command. If the nslookup command fails, there is a problem with DNS. Check the DNS server health or contact the DNS server administrator.
3. If the nslookup command succeeds, it is likely that the shared folder is offline (possibly for maintenance) or there are problems with the permissions on the shared folder.
If communication with a domain controller fails, or DFS metadata is inconsistent, restart the DFS Namespace service (Distributed File System on Windows Server 2003). To do so, open a command prompt window on the affected server and then type the following commands:
net stop dfs
net start dfs
If restarting the service doesn’t resolve the issue, you might need to restart the affected domain controller.
After detecting DfsSvc event 14508, this monitor resets to the Healthy state.