Setting Up An NFS Server And Client On Fedora 13

Version 1.0
Author: Falko Timme
Follow me on Twitter
Last edited 09/16/2010

This guide explains how to set up an NFS server and an NFS client on Fedora 13. NFS stands for Network File System; through NFS, a client can access (read, write) a remote share on an NFS server as if it was on the local hard disk.

I do not issue any guarantee that this will work for you!


1 Preliminary Note

I'm using two Fedora systems here:

  • NFS Server:, IP address:
  • NFS Client:, IP address:


2 Installing NFS


On the NFS server we run:

yum install nfs-utils nfs-utils-lib

Then we create the system startup links for the NFS server and start it:

chkconfig --levels 235 nfs on
/etc/init.d/nfs start


On the client we can install NFS as follows (this is actually the same as on the server):

yum install nfs-utils nfs-utils-lib


3 Exporting Directories On The Server


I'd like to make the directories /home and /var/nfs accessible to the client; therefore we must "export" them on the server.

When a client accesses an NFS share, this normally happens as the user nobody. Usually the /home directory isn't owned by nobody (and I don't recommend to change its ownership to nobody!), and because we want to read and write on /home, we tell NFS that accesses should be made as root (if our /home share was read-only, this wouldn't be necessary). The /var/nfs directory doesn't exist, so we can create it and change its ownership; in my tests the user and group nobody both had the ID 99 on both my Fedora test systems (server and client); when I tried to write to /var/nfs from the NFS client, I got a Permission denied error, so I did a chmod 777 /var/nfs so that everyone could write to that directory; writing to /var/nfs from the client worked then, and on the client the files written to /var/nfs appeared to be owned by the user and group nobody, but on the server they were owned by the (nonexistant) user and group with the ID 65534; so I changed ownership of /var/nfs to the user/group 65534 on the server and changed permissions of /var/nfs back to 755, and voilà, the client was allowed to write to /var/nfs:

mkdir /var/nfs
chown 65534:65534 /var/nfs
chmod 755 /var/nfs

Now we must modify /etc/exports where we "export" our NFS shares. We specify /home and /var/nfs as NFS shares and tell NFS to make accesses to /home as root (to learn more about /etc/exports, its format and available options, take a look at

man 5 exports


vi /etc/exports

/home ,sync,no_root_squash,no_subtree_check)

(The no_root_squash option makes that /home will be accessed as root.)

Whenever we modify /etc/exports, we must run

exportfs -a

afterwards to make the changes effective.

Share this page:

1 Comment(s)

Add comment


From: Bayou Man at: 2010-11-15 19:06:40

... and after having booted both machines - you will find that they now have different ip-addresses!!

The only 'sane' way of exporting a nfs-mount is that the server has a fixed ip-address - anything else will fail sooner or later.

The ip-addresses given in the example are typically dynamic addresses - though the author doesn't specifically say so.

Most routers will accept static addresses in the 2 through 99 (and 150 through 254) range ('1' being the router itself), dynamic addresses are typically in the 100 through 149 range.

If you have a linksys ap - it will typically have a 245-address, some printers I have come across are 51 (out of the box, but can be changed) - ymmv.

To _my_ simple mind - any desktop/server/net-product should have a fixed address.


Just my 2c-worth ...