Hi, I tried to setup NFS as client first using YaST. I told it to open the firewall port (it does not stick when I fire YaST again), then to browse the network for hosts: finds none. So I type the IP. Then I try to select directories: finds none. Then I tick "NFSv4share": it finds some (and incorrect, IMO): / /data /home_aux /var They are incorrect, I think, because the exports file on the server has: /data/storage_c/repositorios_zypp/ .... /home/ ... /home1/ ... /home_aux/ ... /data/storage_b/ ... /var/spool/news/ ... I tried with /data, and did not work: linux-9vao:~ # mount -v /data/data_nfs_tc/ mount.nfs4: timeout set for Sun Mar 11 14:15:33 2018 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.1.14,clientaddr=192.168.1.128' mount.nfs4: mount(2): Device or resource busy linux-9vao:~ # mount -v /data/data_nfs_tc/ mount.nfs4: timeout set for Sun Mar 11 14:16:54 2018 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.1.14,clientaddr=192.168.1.128' mount.nfs4: mount(2): Device or resource busy linux-9vao:~ # I later copied an entry from fstab from another install, and it worked instantly. Why doesn't YaST work, is it a bug, or work in progress, or a firewall problem somewhere, or what? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)