Set a static port for statd and lockd daemons, edit the /etc/sysconfig/nfs, and enter the following entries. It implements the Network Status Monitor RPC protocol.ДЄlthough both of these services are started automatically by the nfslock service, you can configure them to run a static port, which can be useful in firewall configurations. On the other hand, the statd daemon is responsible for notifying the users when the NFS server gets restarted without a graceful shutdown. The lockd daemon allows the NFS clients to lock files on the NFS server. These daemons run on the server-side and the client-side. The NFS Lock Manager daemon (lockd) and Status Manager daemon (statd) are other services required r to run NFS. The port is true on both TCP and UDP protocols. This is a critical service that works with the Linux kernel to provide functionality like server threads for all clients connected to the server.Д«y default, the NFS daemon is already configured to run a static port of 2049. This is the NFS daemon that runs on NFS servers. However, you can edit the configuration to set a static port in the file /etc/sysconfig/nfs. It is mainly handled by the nfsd service and does not require user configuration. This service runs on the NFS server and is used to handle mount requests from the NFS clients. The other service required to run NFS is the mountd daemon. If you are implementing a firewall, ensure sure this port is allowed for incoming and outgoing packets. It runs on Port 111 for both TCP and UDP protocols. Portmapper service is required to run NFS both on the client and the server-side. Keep in mind that this is only for NFS v2 and v3. To implement NFS sharing, the following services are required. The portmap service in Linux handles Remote Procedure Calls, which NFS (v2 and v3) uses to encode and decode requests between the client and the servers. Services Required (NFS v2 and V3)ДЄs mentioned, NFS v2 & v3 use portmap service. NFS v2 and v2, however, require additional ports and services, which we are going to discuss in this tutorial. Therefore, in NFS v4, only port 2049 is required. NFS v4 does not use a portmapper, and services required by NFS V2 and V3 are unrequired. If you wish to learn more, consider the official document provided below: The table above shows some of the features of NFS protocol 4 vs. The following is a comparison of NFS v3 and NFS v 4. They include stateful operations, backward compatibility with NFS v2 and NFS v3, removed portmapper requirement, Cross-platform interoperability, better namespace handling, Built-in security with ACLs, and Kerberos. The most recent version of the NFS v4 provides new and improved features. However, NFS v3 is not compatible with NFS v2 clients. NFS v3 is newer than NFS V2 and offers more features such as variable size handling, improved error reporting, etc. NFS v2 is the oldest and the most widely supported. There are three versions of NFS supported at the time of writing this article. Once we understand the specific ports and services of the NFS share, we can use them to configure security measures such as firewalls and troubleshooting. In this tutorial, we will focus on the fundamental networking concepts of NFS, specifically, the ports used by the NFS services. That makes NFS a much better choice for remote shares compared to Samba. In addition, NFS server access is also restricted to specified hostnames and IP addresses. However, unlike Samba, NFS provides an encryption mechanism and authentication. The NFS protocol is similar to the Samba protocol. Network File System or NFS is a file system protocol that allows users to share directories and files over a network.

Windows nfs v4