The Portmap service did not start as it could not register on port UDP 111 Event ID 3001

You installed  Microsoft Services for Network File System, but Name Mapping service failing to start, maybe on you server running CA Archserve Backup server or you using other software that bound to port 111


Instruction how you can determine the problem:

On the server, run the following in a CMD window

rpcinfo -p
netstat -ano

Basically, there most likely is some other portmapper that has started up and bound to port 111, not the one the system is expecting. The rpcinfo -p will let you see that, look for something like:

program version protocol port

--------------------------------------------------

100000 3 udp 111 portmapper

100000 2 udp 111 portmapper

100000 3 tcp 111 portmapper

100000 2 tcp 111 portmapper



If you see the above in your output, then something is listeing on port 111. If so, you can then run netstat -ano to find out what program is bound to the above port.

Active Connections


  Proto  Local Address          Foreign Address        State           PID

  TCP    0.0.0.0:111            0.0.0.0:0              LISTENING       252


You can then use "Task Manager" or Sysinternals Procexp lookup up the PID and it will tell you the program that's listening on that port. Once you find out, sometimes it'll be a backup program or some other program that talks to UNIX boxes, investigate and see if you can disable it or work with the vendor to get the issue resolved.

Microsoft KB about this:

http://support.microsoft.com/kb/313621


If you running CA ARCserve Backup, you can delay service start by adding key to registry:


In the following:
HKEY_LOCAL_MACHINE\Software\ComputerAssociates\BrightStor ARCserve Backup\Base\Portmap


Create the DWORD DelayedRegistration.

Explanation:

Assign a decimal value for this key indicating the number of minutes BrightStor ARCserve Backup services wait before initializing portmapper registration. For example DelayedRegistration=2 causes all BrightStor ARCserve Backup services to start but not register with the portmapper for 2 minutes after startup.

6.1 Portmapper Conflicts with BrightStor ARCserve Backup. If BrightStor ARCserve Backup detects port 111 conflicts, indicating that it is using the same port number for the CA Remote Procedure Call server service as a previously installed portmapper, BrightStor ARCserve Backup automatically switches to another port number. To avoid having other software affected by a similar problem change the Automatic status of the CA Remote Procedure Call server service to Manual. If you have installed BrightStor ARCserve Backup in a Microsoft Cluster Services environment change the Automatic status of the CA Remote Procedure Call server service to Disabled. This enables you to avoid similar port conflicts after the system has completed the boot process. BrightStor ARCserve Backup can work with external portmappers (SFU 3.0 Noblenet Portmapper, StorageTek, Libattach and so on). However, during the machine boot up sequence BrightStor ARCserve Backup services may try to initialize before the external portmapper has fully initialized. Under these circumstances, BrightStor ARCserve Backup services then fail to initialize. To avoid this problem perform the following steps:

Another workaround, you can delay service, which one using portmapper. Link how to do it

http://support.microsoft.com/kb/193888