NFS, or Network File System, is a simple and efficient way to share files across Linux and UNIX systems. If you need centralized storage that clients can mount as if it were local, this guide walks you through how to set up a nfs server on common Linux distributions. Whether you are building a small home lab or a production environment, knowing how to set up nfs server correctly saves time and reduces troubleshooting later.

What you should know before you set up nfs server

Before diving into installation, consider a few planning points that influence both security and performance:

• Network topology: limit export access to trusted subnets to reduce exposure.
• Version choice: NFSv4 offers improved security and a single mount point, but some clients still rely on NFSv3 for compatibility.
• Permissions: decide whether to use file permissions, account mapping, or root squash to protect privileged operations.
• Backup and retention: ensure shared data is included in your normal backup workflow.

In practice, you will want to set up nfs server with a clear export policy and a plan for future expansion.

Decide on the NFS version and security model

Most modern environments can start with NFSv4, which supports strong authentication and better cross-platform compatibility. If you have legacy clients, you may also enable NFSv3 for those machines while still serving through NFSv4 for others. When you set up nfs server, you should:

• Enable NFSv4 as the default where possible to simplify firewall rules and performance tuning.
• Consider a Kerberos-based authentication (krb5) for higher security in sensitive environments.
• Use root_squash to avoid giving root users on clients full control over exported files, unless you have a controlled trusted network and specific needs.

Install the NFS server software

The exact commands depend on your Linux distribution. Below are the common steps for the two major families:

Debian-based (Ubuntu, Debian)

Update the package list and install the kernel server components:

sudo apt-get update
sudo apt-get install nfs-kernel-server

Red Hat-based (RHEL, CentOS, Rocky)

Install the NFS utilities and enable the service at boot:

sudo yum install -y nfs-utils
sudo systemctl enable --now nfs-server

On newer Fedora or RHEL systems that use dnf, replace yum with dnf. After installation, you will configure exports and start the service as described below. When you set up nfs server, you should verify that the nfs-kernel-server or nfs-server services are active:

systemctl status nfs-kernel-server  # Debian/Ubuntu
systemctl status nfs-server           # RHEL/CentOS

Prepare the shared directory and permissions

Choose a stable location for the shared data, typically under /srv or /export. Create the directory, set appropriate permissions, and ensure it is available to the NFS service:

sudo mkdir -p /srv/nfs/share
sudo chown nobody:nogroup /srv/nfs/share       # example ownership
sudo chmod 755 /srv/nfs/share

If your environment requires fine-grained access, consider mapping user IDs or enabling idmapd for NFSv4. The goal is to ensure clients either respect POSIX permissions or use a consistent mapping that you manage centrally.

Configure /etc/exports with export rules

The /etc/exports file defines which directories are shared, and which clients may access them along with the access options. A typical entry might look like this:

/srv/nfs/share 192.168.1.0/24(rw,sync,no_subtree_check,no_root_squash)

In a more secure setup, you might avoid no_root_squash unless you require root access from clients. You should also consider whether to use:

• ro or rw permissions
• sync vs async write semantics for performance and data integrity
• subtree_check to ensure valid exports after file tree changes
• fsid=0 for the NFSv4 root and proper pseudo-filesystem behavior

After editing /etc/exports, apply the changes:

sudo exportfs -a
sudo exportfs -v

When you set up nfs server, ensure that the export policy aligns with your security and performance goals. For example, you can restrict access to specific hosts or subnets and tune options for read or write workloads.

Start the service and enable at boot

Depending on your distribution, the service name may differ slightly. Start the service and ensure it starts on boot:

sudo systemctl start nfs-kernel-server
sudo systemctl enable nfs-kernel-server

Also verify that required RPC services are running, especially on older setups:

sudo systemctl enable --now rpcbind
sudo systemctl enable --now nfs-common  # on some Debian-based systems

If you are applying a new firewall policy, ensure it allows NFS traffic (see the next section for details).

Firewall and network considerations

Firewalls are a common source of NFS connectivity problems. The default ports for NFS include 2049 (tcp/udp), and related RPC services on 111, and possibly higher dynamic ports for mountd depending on your configuration. A straightforward approach for a small network is to allow 2049/tcp and 2049/udp from your clients, while enabling rpcbind as needed. For example, with UFW you could:

sudo ufw allow from 192.168.1.0/24 to any port 2049 proto tcp
sudo ufw allow from 192.168.1.0/24 to any port 2049 proto udp

In a larger or more dynamic environment, you may use firewalld or a dedicated network policy to permit NFS-related traffic only to trusted subnets. When you set up nfs server in a data center, consider consolidating rules to standardize access across multiple hosts.

Client side: mounting the NFS share

On the client machine, you need the NFS client utilities installed (nfs-common on Debian/Ubuntu or nfs-utils on RHEL/CentOS). Then mount the share:

sudo apt-get install -y nfs-common  # Debian/Ubuntu
sudo mount -t nfs4 server.domain:/srv/nfs/share /mnt/nfs

To mount with a specific NFS version or options, adjust the mount command:

sudo mount -t nfs4 -o rw,vers=4.1 server.domain:/srv/nfs/share /mnt/nfs

Make the mount persistent by adding an entry to /etc/fstab:

server.domain:/srv/nfs/share /mnt/nfs nfs4 defaults 0 0

When you set up nfs server, test accessibility from multiple clients to confirm that the permission and network rules function as intended.

Tuning, security, and best practices

To ensure a stable and secure share, keep these practices in mind:

• Use a dedicated mount point with restricted permissions to prevent accidental data exposure.
• Enable only the necessary NFS versions and security flavors. If you don’t need root access from clients, rely on root_squash.
• Prefer synchronous writes for critical data or enable async if you can tolerate a small risk in exchange for performance gains.
• Regularly monitor export policies and test failover scenarios if you rely on multiple servers or HA solutions.
• Consider NFSv4 with an LDAP or Kerberos-backed identity service for large deployments requiring centralized authentication.

In practice, you should periodically review the exports, monitor logs, and adjust exports as user needs evolve. The ability to set up nfs server changes the way teams collaborate, making remote file access predictable and reliable.

Troubleshooting common issues

Despite careful setup, problems can occur. Common checks include:

• Verify that the server exports are active with exportfs -v.
• Check service status and logs: systemctl status nfs-kernel-server and journalctl -u nfs-kernel-server.
• On the client, confirm that you can resolve the server and that the mount point exists, using showmount -e server and mount | grep nfs.
• Confirm that firewalls allow traffic on 2049 and related ports and that the client IP is permitted by /etc/exports.

If you run into permission issues, re-check UID/GID mappings and ensure the client and server share the same user identities where necessary. When you set up nfs server, small misconfigurations in exports or permissions are the most frequent culprits.

Maintenance, monitoring, and growth

Maintaining an NFS server involves a combination of regular checks and proactive planning:

• Schedule periodic audits of exported directories and client access lists.
• Monitor throughput and latency with standard Linux tools and consider tuning for large concurrent clients.
• Plan for capacity growth by monitoring disk usage on the share and setting up alerts.

As your storage needs grow, you may explore high-availability options, such as replicating exports to another server or integrating NFS with a clustered storage backend. In many environments, a well-designed NFS setup remains the backbone of scalable, shared file access.

Conclusion

Setting up a reliable NFS server is an essential skills for system administrators and IT teams. By carefully choosing the version, configuring exports with sensible permissions, securing the network, and validating with clients, you can build a robust file-sharing solution that scales with your organization. If you follow the steps outlined here, you will be comfortable with the process to set up nfs server and maintain it over time. Remember that good documentation and regular testing are as important as the initial configuration, ensuring that users experience consistent access to the data they need.

Whether you are new to Linux or managing a mixed environment, the ability to set up nfs server efficiently translates into fewer surprises and more productive collaboration across teams.