Question : Portmap fails to start (Server for NFS)

We have "Telserver" with Windows Server 2003 R2, and Shoretel IP telephone software installed to interface with IP phones and our PCs running Outlook.

Apparently there is an important unix interface with the phones for updating information such as date and time. (Because it's not working since a power-outage hard-boot)

The Server for NFS service fails to start, because it is dependent on PORTMAP. When attempting to start portmap with "net start portmap", I get the following error:
"A device attached to the system is not functioning"

In the system Event Log, the error is attached below.

To further complicate the matter, there appears to be no hardware issues with the server in Device Manager.

I need help with this issue. Any insight or immediate solution would be appreciated as I know very little about portmap or NFS server

Code Snippet:

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:

           
           
             Event Type:	Error
Event Source:	Portmap
Event Category:	None
Event ID:	3001
Date:		6/16/2008
Time:		9:28:05 AM
User:		N/A
Computer:	TELSERVER
Description:
The Portmap service did not start as it could not register on port UDP 111. Please ensure that no other program has registered on UDP port 111.
 
-----------------------------------------------------------------------
Event Type:	Error
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7001
Date:		6/16/2008
Time:		9:28:05 AM
User:		N/A
Computer:	TELSERVER
Description:
The Server for NFS service depends on the Portmap service which failed to start because of the following error: 
A device attached to the system is not functioning.

           
         

Open in New Window Select All

Answer : Portmap fails to start (Server for NFS)

Hi,

On the server, could you run the following in a CMD window and paste the output here?

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. E.g:

Active Connections

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:111 0.0.0.0:0 LISTENING 724

You can then use "Task Manager" to 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.
Here is a nice KB about this as well:

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