Your share should be mounted exactly where you specified. Try mounting it on the client using /etc/fstab. If you aren’t certain if the share will always be available on the client, add noauto to the list of options to prevent your system from trying to mount it automatically. The end result should look a bit like the example below. The options are up to you, but using the defaults and allowing user access are pretty common for non-sensitive shares. Follow that with where the share is to be mounted. Start with the location of the share on your network. The overall syntax looks a lot like the command that you just used to mount your share. Provided the mount succeeded, you’ll be able to access your shared files in the directory where you mounted them.įor a more permanent solution, you can add the share to your client’s /etc/fstab file.
#DEBIAN GUI NFS MANAGER INSTALL#
Assuming that your clients are Ubuntu or Debian based, you can install the required package to connect with: $ sudo apt install nfs-common Your share is now accessible from the client machines that you configured in your exports.
$ sudo systemctl restart nfs-kernel-server Connect to a Share
Then, restart the server to load your new exports configuration. Once you have everything set up the way you want, save and exit the file. async: ignores synchronization checks in favor of increased speed.sync: this just ensures that the host keeps any changes uploaded to the shared directory in sync.no_subtree_check: specifies that the host should not check the location of the files being accessed withing the host filesystem.subtree_check: specifies that, in the case of a directory is exported instead of an entire filesystem, the host should verify the location of files and directories on the host filesystem.no_root_squash: is an extremely dangerous option that allows remote “root” users the same privilege as the “root” user of the host machine.rw: grants both read and write permissions on the directory.ro: specifies that the directory may only be mounted as read only.Here is a complete breakdown of what’s available: There are plenty more options that you can choose from to configure how the server handles you share for each guest. In that instance, each of those machines could view and read from the share, but only the computer at 192.168.1.112 could write to it. You can also include more than one hostname or IP in each line and assign them different permissions. Doing that from the command line would take a long time to type and increase the risk of making a mistake since it is generally allot easier to make a typo than forget to click a button.You can include as many shares as you like, provided each has its own line. One nice thing about the user-admin GUI tool is that you can view a list of all the permissions (about 13 of them) that a user currently has and add or remove those permissions by simply checking a box (just a few clicks). I agree that somethings, like adding a single user with default permissions, is faster from a command line (for a person who knows the commands), it doesn't mean that a command line is always better or faster every time.įor example, I just installed Debian and created a new standard user account but by default this account does not have permission to connect to wireless networks, mount user space file systems, suspend and hibernate the computer.
#DEBIAN GUI NFS MANAGER SOFTWARE#
There are times when a GUI can be simpler and faster than typing at a command line, for example if you want to adjust specific permissions for different users such as who is allowed mount storage devices, who is allowed to configure the network settings, who can install software etc, then the users-admin GUI in gnome-system-tools is great.