This error message likely has nothing to do with versions or protocols.
First make sure the machine where the file system resides is actually running an nfs server. For example you can say sudo service --status-all
; there should be a line there for nfs-kernel-server, with a + sign.
Also check that the server has an entry in /etc/exports that allows your client to remote mount it. For example, if the client is called "foohost",
a line in the server's /etc/exports might look like this:
/home foohost(all_squash,anonuid=1000,anongid=1000,no_subtree_check,rw,sync)
Instead of foohost you could have * to allow any host to mount it, or an IP range, etc. Type man exports
to see the meaning of the various options in parentheses.
After editing /etc/exports, be sure to run sudo service nfs-kernel-server restart
(also on the server) so the changes take effect.
nfsmount.conf
– Bob_Ross May 11 '21 at 21:26mount
command and error message. Telling us you looked all over online isn't helpful unless you're specific; and that you allowed for the time-difference with what you found & the software stack you are using (ie. 18.04 means the 2018-April release making your Ubuntu system easy to date for changes/comparison with online documentation you find...) – guiverc May 12 '21 at 01:21