The running firewall is not configured to allow the NFS service. (Refer post #2).
public
target: default
icmp-block-inversion: no
interfaces:
sources:
services: dhcpv6-client samba emby-server nfs
ports:
protocols:
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:
But I still the “firewall not configurable” message int NFS Server configuration.
I am not using the firewall, thus I can not realy offer help.
But IMHO, YaST is trying to do what it should do: helping in configuring NFS by doing the appropriate firewall config. Some time ago the firewall software changed from SuSEfirewall2 to firewalld. Can it be possible hat YaST misses here that it should configure firewalld and not the old software. Please others that use the firewall, comment.
And again, I ask the OP if he can try to check if his NFS functions by swiitching off the firewall for a a test and then try to mount on the client. I asked this earlier, but got no reject (one can always say, no I rather would nlot try that, but then please say so), nor a report (what such a test told you).
Now that the firewall is configured (I assume that you’re using NFSv4) try testing as Henk suggests.
I turned the firewall off and the media player box that i have that has NFS fnction can see the Suse server.
It seems to recognise firewalld ok (it at least references firewalld), but it does not appear to be able to configure it, and even if it is suitably configured the YaST module does not recognise the fact. So, a likely bug. It also doesn’t recognise that the nfsserver is started already.
That reads like progress. I think you got hung up with the yast utility mis-information.
You should also tell us if you’re using NFS v3 or v4. That makes a difference with the firewall configuration.
It’s NFSv4.
Ok, then AFAIU opening the NFS port (port 2049 TCP) should be all that is required. This obviously needs to apply to the interface connecting with the client LAN, so you should check that too. Make sure that when the firewall is enabled you are still getting connected to the LAN as expected. For example being able to ping hosts on the network from the server.
OK, seems to be working now. thanks.
Great, thanks for the update.