@Carlos: Keep in mind that NFS3 and NFS4 are very different. My workaround with the port option is only intended for NFS4. NFS4 uses a single TCP connection for communication between client and server. Portmapper (with rpcbind) is not needed for NFS4. "My" internal error (for NFS4) is caused by the fact that no UDP communication is possible between my client and my server due to a firewall. Normally, NFS4 should first try to use only the TCP connection _without_ using rpcbind(Portmapper), but this simply not the case. Concerning "my" internal error, this is a bug. The decribed behaviour only works if the port option is specified, although the man page describes exactly the opposite.
Do you get any error messages in dmesg concerning the portmapper/rpcbind during the mount request (for NFS4 mounts)? When I get those internal error messages, they always come along with error messages from rpcbind. Maybe there are at least two different bugs which lead to this internal error. I think that people should clearly state if the intend to use NFS3 or NFS4. BR Christian -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
