Portmap be running on ???

your_shadow03 · 07-23-2009, 02:48 AM

Should Server and Client both need portmap running for NFS Server-Client Architecture?

catkin · 07-23-2009, 03:22 AM

Quote:

Originally Posted by your_shadow03

Should Server and Client both need portmap running for NFS Server-Client Architecture?

Googling Linux pages for NFS and portmap very quickly shows the answer is "yes".

vap16oct1984 · 07-23-2009, 03:28 AM

yes both needed portmap service for running client sever architecture.

sycamorex · 07-23-2009, 03:32 AM

Yes, also I believe that in some distros (eg. Fedora 10+) portmap has been replaced with rpcbind.

chrism01 · 07-23-2009, 07:13 PM

Just FYI, if you use NFSv4, the support services like portmap are built-in and thus no longer needed individually:
http://www.linuxtopia.org/online_boo...l5_ch-nfs.html

vap16oct1984 · 07-25-2009, 06:41 AM

Well rpcbind: (portmap in older versions of Linux) The primary daemon upon which all the others rely, rpcbind manages connections for applications that use the RPC specification. By default, rpcbind listens to TCP port 111 on which an initial connection is made. This is then used to negotiate a range of TCP ports, usually above port 1024, to be used for subsequent data transfers. You need to run rpcbind on both the NFS server and client.

So its the same now its with the name rpcbind but in earlier version of linux its running by name portmap.