Event ID 1072 — NFS Port Registration

Event ID 1072 — NFS Port Registration

Updated: January 27, 2011

Applies To: Windows Server 2008 R2

Network File System (NFS) clients discover NFS servers by querying the port mapper for a remote server. RPC Port Mapper converts RPC data into TCP and UDP protocol port numbers. It must be active for Server for NFS to start.

Event Details

Product: Windows Operating System
ID: 1072
Source: NfsServer
Version: 6.1
Symbolic Name: EVENT_NFS_MOUNT_SPECIFIC_PORT_RPC_REGISTRATION_FAILURE
Message: Server for NFS could not register the mount protocol on the specified port. Server for NFS did not start.

Without the mount protocol, Network File System (NFS) clients cannot connect to NFS shared resources on this server.

Verify that no other programs are registered on the specified mount protocol port, or use the Nfsadmin command-line tool to specify a different port.

Resolve
Free ports and restart Server for NFS

To make TCP/IP ports available and restart Server for NFS:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type netstat -a -b -o. to display all connections with their associated executables and processes.
  3. Unload unnecessary drivers, stop unnecessary services, or close unnecessary programs.
  4. Type net start nfssvc to start Server for NFS.

Verify

To verify that Server for NFS has successfully registered all protocols:

  1. Open a command prompt with elevated privileges. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type rpcinfo to determine the ports and transports that Server for NFS uses.
  3. In the list, verify that the following services are present on both IPv4 and IPv6 (if used):
  • mountd
  • nfs
  • nlockmgr
  • status

Related Management Information

NFS Port Registration

File Services

Related:

Event ID 1071 — NFS Port Registration

Event ID 1071 — NFS Port Registration

Updated: January 27, 2011

Applies To: Windows Server 2008

Network File System (NFS) clients discover NFS servers by querying the port mapper for a remote server. RPC Port Mapper converts RPC data into TCP and UDP protocol port numbers. It must be active for Server for NFS to start.

Event Details

Product: Windows Operating System
ID: 1071
Source: NfsServer
Version: 6.0
Symbolic Name: EVENT_NFS_NSM_SPECIFIC_PORT_RPC_REGISTRATION_FAILURE
Message: Server for NFS could not register the Network Status Manager (NSM) protocol on the specified port. Server for NFS did not start.

Without the NSM protocol, NFS clients would not be able to reclaim files locks on this server, if either the server of client’s service is disrupted.

Verify that no other programs are registered on the specified NSM protocol port, or use the Nfsadmin command-line tool to specify a different port.

Resolve
Free ports and restart Server for NFS

To make TCP/IP ports available and restart Server for NFS:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type netstat -a -b -o. to display all connections with their associated executables and processes.
  3. Unload unnecessary drivers, stop unnecessary services, or close unnecessary programs.
  4. Type net start nfssvc to start Server for NFS.

Verify

To verify that Server for NFS has successfully registered all protocols:

  1. Open a command prompt with elevated privileges. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type rpcinfo to determine the ports and transports that Server for NFS uses.
  3. In the list, verify that the following services are present on both IPv4 and IPv6 (if used):
  • mountd
  • nfs
  • nlockmgr
  • status

Related Management Information

NFS Port Registration

File Services

Related:

Event ID 1069 — NFS Port Registration

Event ID 1069 — NFS Port Registration

Updated: January 27, 2011

Applies To: Windows Server 2008

Network File System (NFS) clients discover NFS servers by querying the port mapper for a remote server. RPC Port Mapper converts RPC data into TCP and UDP protocol port numbers. It must be active for Server for NFS to start.

Event Details

Product: Windows Operating System
ID: 1069
Source: NfsServer
Version: 6.0
Symbolic Name: EVENT_NFS_NFS_SPECIFIC_PORT_RPC_REGISTRATION_FAILURE
Message: Server for NFS could not register the Network File System (NFS) protocol on the specified port (%6). Server for NFS is will attempt to continue. At least one successful NFS port registration is required to start Server for NFS but some NFS clients may not function properly without this specific port registration.

Verify that no other programs have registered with RPC Port Mapper with the following parameters.

Program Name:%t%2
Program Number:%t%3
Version:%t%t%4
Protocol:%t%t%5

Resolve
Free ports and restart Server for NFS

To make TCP/IP ports available and restart Server for NFS:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type netstat -a -b -o. to display all connections with their associated executables and processes.
  3. Unload unnecessary drivers, stop unnecessary services, or close unnecessary programs.
  4. Type net start nfssvc to start Server for NFS.

Verify

To verify that Server for NFS has successfully registered all protocols:

  1. Open a command prompt with elevated privileges. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type rpcinfo to determine the ports and transports that Server for NFS uses.
  3. In the list, verify that the following services are present on both IPv4 and IPv6 (if used):
  • mountd
  • nfs
  • nlockmgr
  • status

Related Management Information

NFS Port Registration

File Services

Related:

RPC Port Mapper was unable to register on port 111. RPC Port Mapper was unable to start.

Details
Product: Windows Operating System
Event ID: 3002
Source: portmap
Version: 5.2.3790.1830
Message: RPC Port Mapper was unable to register on port 111. RPC Port Mapper was unable to start.
   
Explanation

The NFS protocol uses the RPC Port Mapper to enable NFS clients to discover the ports for various NFS services, such as mount, Network Lock Manager (NLM), and Network Status Manager (NSM). If the RPC Port Mapper cannot register on TCP Port 111, Server for NFS will not start and NFS clients will not be able to access Server for NFS file shares.

Cause

Other software may have already registered network services on port 111.

   
User Action

Close any programs registering network services on port 111. Then start Server for NFS by clicking Start and then Control Panel. In Control Panel, double-click Administrative Tools, then click Services. Click Server for NFS. In the Action menu, click Start.

Related:

A Windows subsystem failed a critical request. RPC Port Mapper was unable to start.

Details
Product: Windows Operating System
Event ID: 3000
Source: portmap
Version: 5.2.3790.1830
Message: A Windows subsystem failed a critical request. RPC Port Mapper was unable to start.
   
Explanation

The NFS protocol uses the RPC Port Mapper to enable NFS clients to discover the ports for various NFS services, such as mount, Network Lock Manager (NLM), and Network Status Manager (NSM).

If the RPC Port Mapper cannot start, Server for NFS will not start and NFS clients will not be able to access Server for NFS file shares.

Cause

Windows may be low on system resources.

   
User Action

Try closing programs and restarting Server for NFS. Click Start and then Control Panel. In Control Panel, double-click Administrative Tools, then click Services. Click Server for NFS. In the Action menu, click Start.

Related:

No endpoint was found.

Details
Product: Windows Operating System
Event ID: 1708
Source: RPC
Version: 5.0
Component: System Resources
Symbolic Name: RPC_S_NO_ENDPOINT_FOUND
Message: No endpoint was found.
   
Explanation

An endpoint identifies a particular server instance (or address space) on a host computer in a distributed computing environment. The client part of a distributed (RPC) application is seeking an endpoint that cannot be found.

   
User Action

Contact the supplier of the running distributed application.

Related:

The endpoint format is invalid.

Details
Product: Windows Operating System
Event ID: 1706
Source: RPC
Version: 5.0
Component: System Resources
Symbolic Name: RPC_S_INVALID_ENDPOINT_FORMAT
Message: The endpoint format is invalid.
   
Explanation

An endpoint identifies a particular server instance (or address space) on a host computer in a distributed computing environment. A distributed (RPC) application has generated badly-formatted endpoint identification information.

   
User Action

Contact the supplier of the running distributed application.

Related:

Server for NFS was unable to register with the RPC Port Mapper while attempting to start. Server for NFS is not started.

Details
Product: Windows Operating System
Event ID: 1062
Source: nfssvr
Version: 5.2.3790.1830
Message: Server for NFS was unable to register with the RPC Port Mapper while attempting to start. Server for NFS is not started.
   
Explanation

NFS services do not usually register on well-known ports. NFS utilizes the RPC Port Mapper services for NFS clients to discover the port numbers for the various NFS services, such as mount, Network Lock Manager (NLM), and Network Status Manager (NSM). If Server for NFS is unable to register with the RPC Port Mapper, NFS clients will not be able to access Server for NFS file shares.

Cause

Other software may already be registering with RPC Port Mapper.
   
User Action

Close the program registering with the RPC Port Mapper, then start Server for NFS.

 Click Start and then Control Panel. In Control Panel, double-click Administrative Tools, then click Services. Click Server for NFS. In the Action menu, click Start.

Related:

Server for NFS was unable to register a protocol on a port. One or more NFS services, including Server for NFS, may not be available.

Details
Product: Windows Operating System
Event ID: 1064
Source: nfssvr
Version: 5.2.3790.1830
Message: Server for NFS was unable to register a protocol on a port. One or more NFS services, including Server for NFS, may not be available.
   
Explanation
A required network port is not available.NFS uses the Network Lock Manager (NLM) protocol to provide file locking, the Network Status Manager (NSM) protocol to provide file locking status services, and the mount protocol to provide file share mounting services.If Server for NFS cannot register one of these protocols on their port, NFS clients may not be able to mount shares, establish locks, or even access Server for NFS.

Cause

Another program may be blocking the port or may have registered it for its own use.

By default, mount uses port 1048, NLM uses port 1047, and NSM uses port 1039.

   
User Action

You should either close the program that registered the port or specify different ports for NLM, NSM, or mount using the nfsadmin command-line tool. For more information about using nfsadmin, type nfsadmin /? at the command prompt.

You then need to start Server for NFS. Click Start and then click Control Panel. In Control Panel, double-click Administrative Tools, then double-click Microsoft Services for NFS. Click Microsoft Services for NFS. In the Action menu, click Start.

Related: