Comment # 2 on bug 1162897 from Kevin Nathan

Tried running a hand mount:

mount.nfs 10.2.4.199:/mnt/HD_a2 /dlink  -wv

And received:

mount.nfs: timeout set for Thu Feb  6 08:05:05 2020
mount.nfs: trying text-based options
'vers=4.2,addr=10.2.4.199,clientaddr=10.2.4.7'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options
'vers=4,minorversion=1,addr=10.2.4.199,clientaddr=10.2.4.7'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options
'vers=4,addr=10.2.4.199,clientaddr=10.2.4.7'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=10.2.4.199'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.2.4.199 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.2.4.199 prog 100005 vers 3 prot UDP port 964
mount.nfs: Protocol not supported

And then tried it on one of my Leap 42.3 machines:

mount.nfs 10.2.4.199:/mnt/HD_a2 /newdlink/ -wv

mount.nfs: timeout set for Thu Feb  6 08:11:30 2020
mount.nfs: trying text-based options
'vers=4,addr=10.2.4.199,clientaddr=10.2.4.227'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=10.2.4.199'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.2.4.199 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.2.4.199 prog 100005 vers 3 prot UDP port 964

and it mounts successfully.