I am a Debian/testing user and I had the same problem today, even though I can't figure out what had changed, as I updated packages on the client as well as on the server.
However I detected that in /etc/default/portmap on the server I had this:
# If you want portmap to listen only to the loopback
# interface, uncomment the following line (it will be
# uncommented automatically if you configure this
# through debconf).
OPTIONS="-i 127.0.0.1"
I don't know, whether this had been configured before or not, but after disabling this OPTIONS line and restarting the portmap service I could mount the NFS shares again.Maybe this helps in locating the source of the problem, but maybe it is just some other kind of problem, especially because you have updated the client and not the server.
I am a Debian/testing user and I had the same problem today, even though I can't figure out what had changed, as I updated packages on the client as well as on the server. portmap on the server I had this:
However I detected that in /etc/default/
# If you want portmap to listen only to the loopback
# interface, uncomment the following line (it will be
# uncommented automatically if you configure this
# through debconf).
OPTIONS="-i 127.0.0.1"
I don't know, whether this had been configured before or not, but after disabling this OPTIONS line and restarting the portmap service I could mount the NFS shares again.Maybe this helps in locating the source of the problem, but maybe it is just some other kind of problem, especially because you have updated the client and not the server.