This object monitors the connection to the configured NIS server and generates an alert if Server for NFS cannot connect to the NIS server, if the alert is enabled for this monitor.
Services for NFS supports Network Information Service (NIS) and RFC 2307-based netgroups. Netgroups are used to create network-wide named groups of hosts. Netgroups simplify the control of user and group logon and shell access to remote computers, and enable system administrators to more easily manage NFS access control lists.
This monitor can enter a Critical health state because the NFS server is unable to access the NIS or RFC 2307-based store where the netgroup configuration is stored. The most likely causes are:
Server for NFS is not configured appropriately to access NIS or RFC 2307-based netgroups.
There is a network connectivity issue between the NFS server and the NIS server.
If the health state is unknown, it means that monitoring has not yet begun for this object.
Determine location of NetGroup Source
If the NFS server is unable to access the netgroup store, determine if the location of the NIS or RFC 2307-based NetGroup Source is accurate by using the following procedure:
1. At an elevated command prompt on the affected server, type nfsadmin server.
2. Verify that the netgroup settings NIS Domain and NIS Server display the intended NetGroup Source.
3. Verify that network connectivity exists between the NFS server and the NIS or RFC 2307-based store where netgroups are configured as follows:
For an RFC 2307 source, use the ldifde.exe or ldp.exe tools on the computer running Server for NFS to verify that the store is accessible and has the appropriate netgroup attributes. Copy these tools from a computer with the Active Directory Domain Services (AD DS) or Active Directory Lightweight Directory Services (AD LDS) role installed.
For an NIS source, use the rpcinfo.exe tool to verify that the NIS server is accessible over the network. To check if the source computer is accessible and the NIS service is registered on the source computer, type the following command, where <computername> is the name of the NIS server: rpcinfo <computername>.
The NIS service should appear in the output of this command as RPC program number 100004 and protocol version 2.
Verify Server for NFS is configured appropriately to access NIS server
Verify that Server for NFS is correctly configured to access the NIS server as follows:
2. Verify that Protocol for NIS is UDP, TCP, or both, and is compatible with the protocol allowed at the NIS source computer as determined from the output of the command rpcinfo.exe <computername>.
To verify that Server for NFS is connected to the NIS server, restart Server for NFS as follows:
1. At an elevated command prompt on the affected server, type nfsadmin server stop.
2. Type nfsadmin server start.
This monitor automatically resets to a Healthy state after Server for NFS is restarted.