NFS: Server for NFS Network Port Registration Monitor

  • ID:  Microsoft.Windows.FileServices.Service.NFS.6.2.Server.PortRegistration
  • Description:  This object monitors the registration of ports with the network stack and generates an alert if Server for NFS cannot register a port, if the alert is enabled for this monitor.
  • Target:  NFS (Windows Server 2012)
  • Enabled:  Yes

Operational States

Name State Description
First Event Raised Error  
Second Event Raised Warning  
Third Event Raised Success  

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

This object monitors the registration of ports with the network stack and generates an alert if Server for NFS cannot register a port, if the alert is enabled for this monitor.

The Remote Procedure Call (RPC) Port Mapper service enables UNIX-based computers to discover the UNIX-compatible services available on Windows-based computers and must be active for Server for NFS to start. NFS clients discover NFS servers by querying the RPC Port Mapper service for a remote server. The RPC Port Mapper service converts RPC data into TCP and UDP protocol port numbers.

Causes

This monitor can enter a Warning or Critical health state if Windows does not have enough available TCP/IP ports. Other drivers, services, or programs might be using the TCP/IP ports that are required so that Server for NFS could not register all the port/protocol combinations.

Inspect the Windows System event log for messages from Event source Microsoft-Windows-ServicesForNFS-Server and Event IDs 1059, or 1060, which may have further information on which protocol or port caused the problem.

If the health state is unknown, it means that monitoring has not yet begun for this object.

Resolutions

Determine if Server for NFS has registered all protocols

To determine the ports and transports that Server for NFS uses, at an elevated command prompt on the affected server, type rpcinfo.

Server for NFS typically uses the following port/protocol combinations:

  • mountd service for protocol versions 1, 2, and 3 registered on port 1048 for udp, tcp, udp6, tcp6

  • nfs service for protocol versions 2 and 3 registered on port 2049 for udp, tcp, udp6, tcp6

  • nlockmgr service for protocol versions 1, 2, 3, and 4 registered on port 1047 for udp, tcp, udp6, tcp6

  • status service for protocol version 1 registered on port 1039 for udp, tcp, udp6, tcp6

Make TCP/IP ports available and restart Server for NFS

To make TCP/IP ports available and restart Server for NFS, use the following procedure:

1. At an elevated command prompt, type netstat -a -b -o to display all connections with their associated executables and processes.

2. Resolve port allocations conflicting with the NFS ports identified in Step 1 by deleting unnecessary drivers, stopping unnecessary services, or closing unnecessary programs.

3. Type nfsadmin server stop.

4. Type nfsadmin server start.

Verification

To verify that Server for NFS has successfully registered all protocols, use the following procedure:

1. At an elevated command prompt on the affected server, type rpcinfo.

2. In the list, verify that the mountd, nfs, nlockmgr and status services are all registered with the port mapper on both IPv4 and IPv6 (if used).

This monitor automatically resets to a Healthy state after Server for NFS is restarted.

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