@toer: The simple workaround I have described only works for NFSv4. Which NFS protocol version are you using? BTW: You can also see error messages in dmesg where rpcbind states that it cannot contact the NFS server if you are using NFSv4 and if you have _not_ specified port=2049 explicitly. But again, this is only the case if you are using NFSv4 with TCP and everything else is blocked between the client and the server (mainly UDP, because of RPC).
NFSv3 by default uses the portmapper(for RPC) and UDP. NFSv4 is a very different. @Owen: Please do not close the bug. It is still there if you are using NFSv4 and have a UDP blocking firewall between the client and the server. The man page (NFS4) says: "If this mount option [port=] is not specified, the NFS client uses the standard NFS port number of 2049 without first checking the server's rpcbind service." Simply, this is not the behaviour that is described. The client does contact the server's rpcbind server (via UDP) and this fails with "internal error", although it is not supposed to do so. -> Bug -- 8.04 & 8.10 nfs clients report "internal error" when attempting to mount NFS exports https://bugs.launchpad.net/bugs/213444 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
