I had a server running and had nfs working just fine. Until that machine went down! So I purchased a new machine of the same brand and basic model except,of course, newer. (Dell Inspiron).
I set the new machine up with the same directory setup, same network name, and the same dedicated ip address. I removed the old ssh keys and installed the new ones. ssh is working just fine. But, a “no route to host” message when trying to mount the drives from the new server on my desktop.
**ASU-X99:~ #** mount -v -t nfs4 10.118.118.4:/common /mnt/Server
mount.nfs4: timeout set for Mon Feb 7 18:03:52 2022
mount.nfs4: trying text-based options 'vers=4.2,addr=10.118.118.4,clientaddr=10.118.118.5'
mount.nfs4: mount(2): No route to host
mount.nfs4: trying text-based options 'vers=4.2,addr=10.118.118.4,clientaddr=10.118.118.5'
mount.nfs4: mount(2): No route to host
mount.nfs4: trying text-based options 'vers=4.2,addr=10.118.118.4,clientaddr=10.118.118.5'
mount.nfs4: mount(2): No route to host
^C
**ASU-X99:~ #**
I can ping the server, I can ssh into it, so It seems the ethernet connection is there.
I followed the directions given by Reference › Services › Sharing file systems with NFS . However, in that document, it states that nfsd, idmapd, statd and mountd should be running. But I get this:
**ASU-X99:~ #** systemctl status nfsd
Unit nfsd.service could not be found.
**ASU-X99:~ #** systemctl status idmapd
Unit idmapd.service could not be found.
**ASU-X99:~ #** systemctl status statd
Unit statd.service could not be found.
**ASU-X99:~ #** systemctl status mountd
Unit mountd.service could not be found.
**ASU-X99:~ #**
I don’t understand.
I commented out the line in /etc/fstab to try the mount command. Nothing changed
I’m hoping someone can point some stupid little mistake I made because I can’t find it.
Bart