Export (0) Print
Expand All

Port Mapper Startup Status

Updated: January 27, 2011

Applies To: Windows Server 2008 R2

The RPC Port Mapper service enables UNIX-based computers to discover the UNIX-compatible services that are available on Windows-based computers.

Events

Event ID Source Message

3000

portmap

Windows(R) failed a request to allocate memory. RPC Port Mapper cannot start. Network File System (NFS) clients use RPC Port Mapper (also known as Portmap and Rpcbind) to discover NFS protocols on remote servers. Without RPC Port Mapper, Server for NFS cannot start and NFS clients cannot access files on this server. Windows may be low on system resources. Try increasing available system resources by closing programs, then start Server for NFS manually (which will also start RPC Port Mapper).

3001

portmap

Windows(R) failed a request to register RPC Port Mapper on User Datagram Protocol (UDP) port 111. RPC Port Mapper cannot start. Network File System (NFS) clients use RPC Port Mapper (also known as Portmap and Rpcbind) to discover NFS protocols on remote servers. Without RPC Port Mapper, Server for NFS cannot start and NFS clients cannot access files on this server. Verify that no other software is registered on UDP port 111, then start Server for NFS manually (which will also start RPC Port Mapper).

3002

portmap

Windows(R) failed a request to register RPC Port Mapper on TCP port 111. RPC Port Mapper cannot start. Network File System (NFS) clients use RPC Port Mapper (also known as Portmap and Rpcbind) to discover NFS protocols on remote servers. Without RPC Port Mapper, Server for NFS cannot start and NFS clients cannot access files on this server. Verify that no other software is registered on TCP port 111, then start Server for NFS manually (which will also start RPC Port Mapper).

3003

portmap

Windows(R) failed a request to provide RPC Port Mapper with the IP address for the local host. RPC Port Mapper cannot start. Network File System (NFS) clients use RPC Port Mapper (also known as Portmap and Rpcbind) to discover NFS protocols on remote servers. Without RPC Port Mapper, Server for NFS cannot start and NFS clients cannot access files on this server. Verify that this server is configured properly for networking, then start Server for NFS manually (which will also start RPC Port Mapper).

3004

portmap

Windows(R) RPC Port Mapper service has completed starting but has not yet registered any interfaces. Interface registration for IPv6 UDP interfaces is dynamic and is performed as a background operation. These registrations should be completed shortly. An event will be logged when the registration is completed. Until this registration is complete, any Network File System (NFS) clients attempting to use RPC Port Mapper (also known as Portmap and Rpcbind) to discover NFS protocols on this server may be unable to locate the local Server for NFS and so will not be to access any files hosted on this server. If no registrations for the portmap service itself happen within a few seconds, verify that this server is configured properly for networking, stop the RPC Port Mapper service and then restart the Server for NFS manually (which will also start RPC Port Mapper).

3005

portmap

Windows(R) RPC Port Mapper service (also known as Portmap and Rpcbind) has completed registration of all dynamic interfaces. The service is available for use.

Related Management Information

RPC Port Mapper

File Services

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft