DFS-N: Namespace Server AD DS Connectivity Monitor

  • ID:  Microsoft.Windows.FileServer.DFSN.6.2.RootTargetADConnectivity
  • Description:  This object monitors the ability of a namespace server to access namespace data in Active Directory Domain Services (AD DS) and creates an alert if the namespace server cannot access AD DS.
  • Target:  DFS Namespace Server (Windows Server 2012)
  • Enabled:  Yes

Operational States

Name State Description
FirstEventRaised Warning  
SecondEventRaised Success  

Alert Details

Monitor State Message Priority Severity Auto Resolution
FirstEventRaised (Warning) DFS-N: Namespace Server Cannot Access Data in AD DS Medium Warning Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

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 DFS Namespaces event 14530. If this object detects the event, it sets the health state of the monitor to Warning.

Causes

A namespace server can fail to access AD DS for a number of reasons, including the following:

  • When running a namespace server on 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.

Resolutions

Restart the DFS Namespace service on the Virtual machine

If the namespace server is running in a virtual machine, restart the DFS Namespace service after the host operating system resets the system clock.

Note To restart a service, you must be a member of the local Administrators group on the affected server.

To restart the service, use the Services snap-in, the Windows PowerShell Start-Service and Stop-Service cmdlets, or command-line tools such as net stop and net start. To restart the service remotely by using the sc command, open a command prompt window and then do the following:

1.To stop the service, type the following command, where <ServerName> is the Universal Naming Convention (UNC) path to the remote server:

sc <ServerName> stop dfs

2.To confirm that the service is in the STOPPED state, type the following command:

sc <ServerName> query dfs

3.To restart the service, type the following command:

sc <ServerName> start dfs

Test communication with AD DS

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. If restarting the DFS Namespace service doesn’t help, you might need to restart the affected domain controller.

Verification

After detecting DFS Namespaces event 14532, this monitor resets to the Healthy state.

External References
This monitor does not contain any external references.

See Also for Windows Server File & iSCSI Services Management Pack


Downloads for Windows Server File & iSCSI Services Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED