Closed xttjsn closed 4 years ago
It turns out that I only have to change /shared
to /
when doing mount:
sudo mount -v -t nfs -o vers=4,nfsvers=4 10.0.0.94:/ /mnt/shared_client
mount.nfs: timeout set for Sun Mar 8 18:18:33 2020
mount.nfs: trying text-based options 'vers=4,addr=10.0.0.94,clientaddr=192.168.117.129'
Glad that you got it worked out and thank you for sharing your solution; hopefully it will help others.
NFSv4 uses a "pseudo filesystem" that causes widespread confusion wrt mount points. It's counter intuitive at best.
This might be a noob question, but I have two VMs running in the same bridged network. I configured VM1 as the NFS server:
Here's VM1's network status:
VM2 will be using the interface
ens33
at10.0.0.94
.When I connect to the server using VM2, I get:
Some more verbose output:
Strangely, when I set up VM1's server by
systemctl start nfs-kernel-server
in the same network setup, VM2 CAN connect to the server without issue.Am I missing anything?