NFS don’t work Leap 43,2 > Leap 15 ?
sergio@positivo:~> mount /mnt/asus
mount.nfs: requested NFS version or transport protocol is not supported
NFS don’t work Leap 43,2 > Leap 15 ?
sergio@positivo:~> mount /mnt/asus
mount.nfs: requested NFS version or transport protocol is not supported
That is a very incomplete report. At least show the /etc/fstab entry that belongs to this mount.
On 10/12/2018 05:06 AM, sergelli wrote:
>
> NFS don’t work Leap 43,2 > Leap 15 ?
I see “NFS don’t work” which I presume means that NFS des not work for you
in some case, but the’43.2 > 15’ bit does not make sense. 42.3 came
before 15, so it is not greater than 15 despite numeric assumptions we may
make as humans.
> Code:
> --------------------
>
> sergio@positivo:~> mount /mnt/asus
> mount.nfs: requested NFS version or transport protocol is not supported
>
> --------------------
This is not much on which to base any kind of conclusions. You do not
appear to have a ‘root’ prompt, so I am surprised this works at all unless
you have set it to work as a regular user, but if so then what other
changes have you made to the mountpoint configuration?
What kind of NFS service is this?
Does this work with other NFS services (like this box itself)?
Is this an upgraded box, and if so did it used to work (maybe that is what
‘42.3 > 15’ was meant to mean)?
What happens on the wire as shown in a LAN/wire trace captured via tcpdump?
What does the server side show in its logs when you try to connect?
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
I will just note that NFS has been working for me.
I have one server (my primary desktop), and my other systems are clients.
During the Leap 15.0 beta period, I was regularly using 15.0 on clients with a 42.3 server. Right now, I am using a 15.0 server, and everything is still working fine when I boot client systems to 42.3. For that matter, booting client systems to Tumbleweed still works (including NFS).
I am using automount (running the “autofs” service) for my NFS mounting.
My moves from 42.3 to 15.0 were all clean installs (but keeping “/home”). They were not upgrades.
I just know that after installing Leap 15 on a notebook that I call “asus”, I can no longer connect to my PC that I call "positive.
This is the line inside my fstab
192.168.1.31:/home/sergio /mnt/asus nfs rw,exec,nofail,users,noauto 0 0
The exports file on the server is as it always was, and before it works
If I try to mount as root, it’s the same
sergio@positivo:~> sudo mount /mnt/asus
[sudo] senha para root:
mount.nfs: requested NFS version or transport protocol is not supported
sergio@positivo:~>
Concentrating on the Version part of the message, could you check if NFSv4 is switched on in your Leap 15.0 system (YaST > Network > NFS client, right Tab).
I ask because in an earlier system (I have still a 13.2 here) NFSv4 was NOT the default, while I see that in 51.0 it IS the default (I do not now when the switch was made).
When it is on, please switch it off and try again.