Skip to main content

Share your files through your local network – NFS for Network File System, is a file system that allow you to share files over your network, in similar way as local storage.

However, if you are looking for a solution to share files among GNU/Linux and Windows computers, NFS won’t help you much as Windows per default don’t have what it takes to use NFS system. You will want to use Samba instead.

The main advantage of NFS versus Samba for a basic usage is its speed. It performs better than Samba in term of transfer speed, as this old (2010) test shown or this new (2014) test shown too. However NFS is less flexible than Samba in term of permission I’ll say.

So if you are looking for a fast Linux to Linux (Or MacOS) transfer protocol, I strongly recommend you NFS, and here is how to install it.



On your server, you need to install the NFS Server package. In root (or with sudo), type:

and on the client side, you will need nfs-common



Here again, you will need a specific configuration on the server side while the client will only need to mount it.

Server side:

1) You will first need to create a mount point of NFS shares (You may have severals you want to centralized inside a single mount point, or not)

2) Then you will need to mount what you want to share in those new folders. Adding a new mount point to a folder will make it available for write and read (if folders/files permissions allow) at 2 places.

To avoid retyping this after every reboot, you will need to add a fstab entry. Still in root

and add:

(Note that between each of these variables you should not use SPACE but TAB)

and save with CTRL+X (then yes)

3) And finally, enable the export by creating/modifying the file /etc/exports with similar content:

where is the network you want to share with. (The /24 allow all combination of IP for the last 3 digits). Depending on your local network configuration, you may want to correct this entry with or whatever IP you want to share with. You can actually list more IP addresses and options on the same line, separated with a space such as:

For the option, you can the detail on the man page or directly here.

Once done, you can restart NFS Server:

Client side:

You will then simply have to mount the whole export folder or one folder by one folder on your client such as:

Where is your server IP.

Note that you may want to create a dedicated folder on the client side, to mount the share.

Or here again, to avoid having to mount it at every reboot, you could add a /etc/fstab entry with:

(Here again, there are not space but TAB)
You should now have a working NFS shares on your local network.

Also, having a good server and router will help to achieve higher speed and most probably, your first bottleneck will come from your router and network cables if still in 100M (need cat6 cable and gigabit router for faster transfer speed). On my Western Digital Green 2TO (5400tr/m) that I don’t recommend by the way, I acheive a steadily 80mo/s usually. (I’ve tried SSD to SSD transfer but most probably my router is still the bottleneck for faster transfer, but it will cost me a harm and a leg to have 10G router haha)


File Transfer

Network configuration – Static IP on Linux

Most probably, one of the first setting you want to do will be to assign a static IP of our server among your local network and start configuring your router and domain name.

Networks explanation

Indeed, if you start to install services (Like a website, a torrent client, a jukebox, etc…), you have to make sure all the ports are open and redirected to the correct machine and your domain name is well configured.

But to do so, you need first to make sure the IP of your server will not change. Hence you need to set a static IP into the /etc/network/interfaces file.


and mine is the following:

The part that interest us is iface eth0 inet static and then set the address IP you want (Usually or depending on your router configuration) while the netmask is always the same.

After modification, just save (CTRL+X then Y) and restart your network


Don’t know your IP?

If you don’t know your local IP address on your server or the gateway, you could check the current automatic (DHCP) configuration.

Just type:

and you should have something similar to that:

My local IP address is then

And for the gateway, it is most of the case if your IP is and will be is your IP is