[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: nfs-utils (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/213444 Title: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/213444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
** Tags added: hardy ** Also affects: nfs-utils (Ubuntu Hardy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/213444 Title: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/213444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
** Description changed: + Fix is described in comment #23 + NOW: *ubuntu since 7.11 - meaning at the moment 8.04 and 8.10 releases can't reliably mount NFS exports without getting mount.nfs: internal error if done from the command line. If the mount request is in /etc/fstab it stops KDE loading and the system becomes unuseable (unless you know to open another TTY session). The only workaround (for most people) is to set the mount to noauto in /etc/fstab and try to mount it until it succeeds at the command prompt when the system is booted. WAS: Using Ubuntu Studio based on Hardy Heron beta, 64-bit w/AMD Athlon 64 x2. The other computer involved is a 32-bit Sempron running Gutsy Gibbon. I followed instructions on http://czarism.com/easy-peasy-ubuntu-linux-nfs-file-sharing to make a directory on the Gutsy system availalble on the Hardy beta system, and got the following message when I attempted the mount: mount.nfs: internal error I double checked the commands and the IP addresses/ranges involved, and they appear to be correct. At the Gutsy end: nfs-common and nfs-kernel-server are 1:1.1.1~git-20070709-3ubuntu1, portmap is 6.0-1ubuntu1. At the Hardy end: 1:1.1.2-2ubuntu2 and 6.0-4 for the same packages, respectively. ** Changed in: nfs-utils (Ubuntu Hardy) Status: New = Triaged ** Changed in: nfs-utils (Ubuntu Hardy) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/213444 Title: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/213444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
Has anyone seen this bug on any releases newer than Hardy (i.e. Lucid or Natty)? Or is it specific to hardy? Looking at the fix described in comment #23, it's not evident to me why that fixes it, so while that code change is straightforward enough, we wouldn't want to consider it for SRU without a more detail understanding of why it's a fix. I doublechecked the current nfs-utils package, which has the same bugged code present, so presumably either the bug still exists with newer nfs- utils releases, or the real fix was elsewhere, or the bug gets masked with newer releases (i.e. kernel 2.6.22). Anyway, if anyone still needs this fixed in hardy officially, the next step would be to propose a debdiff which packages the patch in question. ** Changed in: nfs-utils (Ubuntu Hardy) Status: Triaged = Confirmed ** Changed in: nfs-utils (Ubuntu Hardy) Importance: High = Medium ** Changed in: nfs-utils (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/213444 Title: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/213444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
I had this problem with the turnkey virtual appliance server's based on ubuntu. Changing nfs to nfs4 in fstab fixed it for me. -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
Had the same issue mount.nfs: internal error spent about a day trying different things, turns out our nfs could not do a reverse lookup on the client's IP. Resolv.conf had an old server not maintained by us and went away. Added a line for all the hosts that need nfs on the /etc/hosts of nfs server. mount -a started again. Hope this helps some of you having this issue, because it was driving me crazy. -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
I had same problem, but found reason and solution. Ubuntu NEED opened udp 111 port on server. I have checked binds on server ( freebsd ) and found udp 11 port binded to localhost. Just after that, I restarted rpcbind, mountd and nfsd services on my freebsd-server and all going ok :) Thank's to wireshark - it's really helps discover problems :) -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
I run hardy on booth nfs-server and client. Running in normal mode, mounting work perfectly. Running nfs through an ssh-tunnel as described by http://www.howtoforge.com/nfs_ssh_tunneling Reults in an internal error. Applying Bills workaround https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/213444/comments/23 fixes everything. A cannot understand why this takes so long time to fix when it is just to uncomment one line of code, or is the problem more complex? -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
Is it so difficult to solve this??? -- 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
Re: [Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
Hi I had no opportunity to test yey (work + children) but will do it soon, guys. What I do not understand is wher eI catch the difference between NFS3 and NFS4, I was assuming my command mounting mount.nfs corresponded to nfs3 and mount.nfs4 was mounting nfs4, where both failed execution. sudo mount.nfs 192.168.1.3:/media/TV/tdt /home/carlos/LAN.tv -o port=2049 mount.nfs: internal error sudo mount.nfs4 192.168.1.3:/media/TV/tdt /home/carlos/LAN.tv -o port=2049 mount.nfs4: internal error -- Carlos Blanquer Bogacz ___ skype: carlosblanquerbogacz ___ -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
@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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
Still same issue. I followed the link http://www.linuxconfig.org/HowTo_configure_NFS for setting up my share and the remote access. I have set up checked nfs on my server Kubuntu 8.10. I did set up a connection form my client PC Ubuntu 8.10, which does not work. These are the commands I issued: sudo mount.nfs 192.168.1.3:/media/TV/tdt /home/carlos/LAN.tv -o port=2049 mount.nfs: internal error sudo mount.nfs4 192.168.1.3:/media/TV/tdt /home/carlos/LAN.tv -o port=2049 mount.nfs4: internal error === As far as I see in the bugthread there is no solution yet, is there ? Or do I operate wrongly ? THX -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
@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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
The error appears remaining for unavailable mounts, example of the command 'mount -a' when four mounts are unavailable on the network: [~]$ sudo mount -a mount.nfs: internal error mount.nfs: internal error mount.nfs: internal error mount.nfs: internal error When three are available and one unavailable: [~]$ sudo mount -a mount.nfs: internal error and the three available are mounted and accessible. So far without any further digging, 'mount -a' via fstab seems to function as expected but any unavailible mount is (after about half a minute delay!) reported as an internal error. Specifying port=2049 made no difference - this was Kubuntu Hardy 8.04.1 -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
The problem is still there. At least in hardy which is LTS. I used NFSv4. Only one TCP port (2049) is possible between Server and Client due to a firewall. There is a really simply workaround for this: Specifiy port=2049 in the mount options on the client. By specifying this option rpcbind is not contacted any more by mount.nfs4, so UDP is not required anymore. Yes, I know that 2049 _is_ already the default port, but the fact that the option is explicitly set changes the behaviour of mount.nfs4. From the manpage: [...] Valid options for the nfs4 file system type port=n The numeric value of the server's NFS service port. If the server's NFS service is not available on the specified port, the mount request fails. If this mount option is not specified, the NFS client uses the standard NFS port number of 2049 without first checking the server's rpcbind service. This allows an NFS version 4 client to contact an NFS version 4 server through a firewall that may block rpcbind requests. [...] Important is the _last_ part. The nfs client is supposed to try only TCP port 2049 without asking rpcbind first if the port= option is _NOT_ given. But this is simply not the case. It definitly asks rpcbind which fails because UDP is blocked. So the whole mount requests times out and gives the internal error then. I managed to get around this by specifing port=2049 in the mount options. Now it seems to work. No more rpcbind errors in dmesg output. So I assume that rpcbind is not asked anymore. So at least there is a discrepancy between the man page and the actual behaviour of NFSv4 mounts with respect to one-tcp-port-only-mounts. -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
Following routine system updating on 4/1/09, the mounts now go through perfectly (and fast). I don't know which particular update fixed it but I can confirm that both 8.04 and 8.10 are now mounting NFS3 fine for me. How does the bug get closed as fixed? Cheers, Owen -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
Amazing that an update to nfs-common just arrived with various fixes, but without fixing this major problem that breaks previously-working systems when upgrading, especially since there's a working fix in a .deb in the ticket. -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
@ Paul Abrahams Supposedly the fixed code is available in Debian. It seems just not to have been picked up in *ubuntu - earlier posts in this thread seem to confirm. Amazing things I feel, a linux distribution that can't cope with either NFS or CIFS shares. See below for details: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/211631 -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
If it fails to mount the first time, try again. In your case: sudo mount /home/jason/Sync -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
We had the same problem, we solved it by disabling the networkmanager and either assigning static IPs or using the old approach of dhcp via interfaces not networkmanager... -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
The NFS mount problem has been around now for quite a while. I think I first reported it (under another number) a couple of years ago. It must be a bug since it should not be possible for a user to provoke an internal error no matter what he or she does. And it's been encountered by quite a number of people -- I assume that the reporters here are only a small minority of those who've bumped into it. Is there anyone around who has assumed responsibility for this? -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
@Owen: I saw where you posted that suggestion originally. I tried that and still got the internal error. After a reboot it still doesn't work. I tried to connect to it with my 8.10 laptop and got the same results using both my original configuration and the new one requested by Owen above. @Christoph Cullmann: I don't use network-manager on my laptop, I use Wicd instead and have a static IP. -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
Perhaps if no one can determine the cause of the error, it might be worthwhile to modify the code in order to produce a more revealing (to the code author, anyway) error message. -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
** Summary changed: - Hardy Heron nfs (client) reports internal error when I attempt to mount with NFS + 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
** Description changed: - Using Ubuntu Studio based on Hardy Heron beta, 64-bit w/AMD Athlon 64 - x2. The other computer involved is a 32-bit Sempron running Gutsy - Gibbon. I followed instructions on http://czarism.com/easy-peasy-ubuntu- - linux-nfs-file-sharing to make a directory on the Gutsy system - availalble on the Hardy beta system, and got the following message when - I attempted the mount: + NOW: + *ubuntu since 7.11 - meaning at the moment 8.04 and 8.10 releases can't reliably mount NFS exports without getting mount.nfs: internal error if done from the command line. + + If the mount request is in /etc/fstab it stops KDE loading and the + system becomes unuseable (unless you know to open another TTY session). + + The only workaround (for most people) is to set the mount to noauto in + /etc/fstab and try to mount it until it succeeds at the command prompt + when the system is booted. + + WAS: + Using Ubuntu Studio based on Hardy Heron beta, 64-bit w/AMD Athlon 64 x2. The other computer involved is a 32-bit Sempron running Gutsy Gibbon. I followed instructions on http://czarism.com/easy-peasy-ubuntu-linux-nfs-file-sharing to make a directory on the Gutsy system availalble on the Hardy beta system, and got the following message when I attempted the mount: mount.nfs: internal error I double checked the commands and the IP addresses/ranges involved, and they appear to be correct. At the Gutsy end: nfs-common and nfs-kernel-server are 1:1.1.1~git-20070709-3ubuntu1, portmap is 6.0-1ubuntu1. At the Hardy end: 1:1.1.2-2ubuntu2 and 6.0-4 for the same packages, respectively. -- 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
[Bug 213444] Re: 8.04 8.10 nfs clients report internal error when attempting to mount NFS exports
Well I edited fstab and tried to do a mount again but it got the same error. I'm going to shut my PC down for the night and I'll try it again tomorrow if I have time. Maybe it will work after a restart. I also brought my 8.10 laptop home from work, I'll try connecting to the NFS from it and see what happens. -- 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
