[nzlug] nfs share not available to kubuntu clients

[Simon Bridge]

This one is confusing me...

There is an NFS server set up on an FC5 box.
There are four clients, two of which are running Kubuntu (Dapper and
Edgy), one mac and one WinXP. The mac and the xp can access the shares
fine, suggesting that the server is working. The Kubuntu boxes get
errors. 

They used to be able to access the shares - but the FC5 box endured a
general update via YUM. Since then, no sharing with kubuntu. Not tested
with other linuxes.

I've tried to gather what may be helpful:

Mounting from fstab gives the following error:
mount to NFS server 'acsserver' failed.

Edgy $ sudo mount -t nfs 192.168.0.105:/music /music -v
mount to NFS server '192.168.0.105' failed.
RPC Error: 15 ( Program not registered )

Edgy $ /usr/sbin/showmount -e acsserver
bash: /usr/sbin/showmount: No such file or directory

FC5 # exportfs
exportfs: could not open /var/lib/nfs/etab for locking

FC5 # rpcinfo -p acsserver
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  32768  status
    100024    1   tcp  55714  status

FC5 $ ls -l /var/lib/nfs
total 12
-rw-r--r-- 1 root    root       0 Jan 14 22:58 etab.rpmsave
-rw-r--r-- 1 root    root    1172 Jan 14 22:51 rmtab.rpmsave
drwxr-xr-x 7 root    root       0 Jan 19 18:05 rpc_pipefs
drwx------ 4 rpcuser rpcuser 4096 Jan 14 23:21 statd
-rw------- 1 root    root       0 Dec  6 20:36 state
drwxr-xr-x 2 root    root    4096 Dec  6 20:36 v4recovery
-rw-r--r-- 1 root    root       0 Dec  6 20:36 xtab

etab is, not present (though a file called etab.rpmsave is). Also not
present are files sm and sm.bak
... I thought these were required to export nfs shares... yet it is
working fine with non-kubuntu clients.

Have googled: practically everything on these errors involve situations
where there is only one client or no clients can access the shares.

At this stage I feel like setting up the clients then the server again
from the start - since it may be simpler than actually diagnosing the
problem.

hmmm... is portmap running on the clients (client says it is the same
client setup - but I should have checked...) I'll have to check. (Would
that produce these errors though?)