Setting up an NFS connection with NFSv4 - I am failing

I am try to set up a dedicated NFSV4 connection between my workstation and a network renderer, both are on the same subnet. The workstation is running KDE desktop with the server on 192.168.169.236 and the client device is (I believe) a debian variant.
I have been trying to create a read only connection between the two machines, not the whole subnet.

The server has the following export:-

/run/media/alastair/old_data    192.168.168.236(ro,root_squash,sync,no_subtree_check)

I set this up using Yast2 and enabled nfs on the firewall but there is a warning message concerning the Firewall not being configurable which might be an issue but whatever the problem, when logged into the client device I cannot see the server. Please could I have some guidance on this.

Checking my NFS server, I see that I have changed firewall rules to allow

mountd
nfs
nfs3
rpc-bind

That’s all for the “public” zone.

It is getting late and keeping up with the rugby but should I have the server address IP in this line? I may be confusing client and host!!!

I shall switch to NFSv3 and see if that helps.

Try adding insecure to your options. This tripped me up for the longest time when making the switch to v4. According to the exports man page:

The insecure option in this entry also allows clients with NFS implementations that don’t use a reserved port for NFS.