This object monitors the ability of a namespace server to access namespace data in Active Directory Domain Services (AD DS) by looking for the presence of DfsSvc event 14530. If this object detects the event, it sets the health state of the monitor to Warning.
A namespace server can fail to access AD DS for a number of reasons including the following:
When running a namespace server in a virtual machine, the DFS Namespace service can get disrupted if the host operating system changes the clock of the guest operating system after being out of sync by more than approximately five minutes.
Network connectivity problems are preventing the namespace server from reaching a domain controller.
If the namespace server is running in a virtual machine, restart the DFS Namespace service (Distributed File System on Windows Server 2003) after the host operating system resets the system clock. To do so, open a command prompt window on the affected server and then type the following commands:
net stop dfs
net start dfs
To test communication with AD DS, use the dfsdiag /testdcs command. Confirm that all domain controllers report healthy results.
If communication with a domain controller fails, or DFS metadata is inconsistent, try restarting the DFS Namespace service (Distributed File System on Windows Server 2003). If restarting the DFS Namespace service doesn’t help, you might need to restart the affected domain controller.
After detecting DfsSvc event 14532, this monitor resets to the Healthy state.