I am getting some crazy behavior from an NFS server. The server seems to think
that it is properly exporting and allowing clients to mount directories, but the
clients show the following error message when I try to mount.

[root@hestia /]# mount -t nfs hestia:/opt/test /mnt/nfs
mount: hestia:/opt/test failed. reason given by server: Permission denied

(The NFS howto covers this error message, but that didn't work.)

On the server side I get the following message in /var/log/messages.
May 16 11:30:21 hestia rpc.mountd authenticated mount request from hestia.x.x:720 for /opt/test (/opt/test)
(for now I am just trying to mount the filesystem back onto the server)

The previous message, to me, seems to indicate that the server thinks it is
exporting the filesystem to the client machine.

Before I forget, I am running Mandriva 10.1 with kernel 2.6.11-1mdksmp.

My /etc/exports line is this:
/opt/test 192.168.1.0/24(rw,no_root_squash,sync)

From every way I know how to check, the server appears to be exporting the
correct filesystem. This included using exportfs, showmount -e, and looking in
/var/lib/nfs/etab. DNS lookups and reverse lookups work. There are also no
firewalls that could interfere with mounting.

Whenever I attempt to mount the filesystem, the server will increment that
host's count in /var/lib/nfs/rmtab. Which seems to be another indication that
the server thinks it is successfully exporting the directory to the client.
However, rmtab contains a lot of strange looking entries such as:
192.168.1.170:192.168.1.170/24:0x00000001
192.168.1.170/24:/opt/test:0x00000001
192.168.1.170:192.168.1.170/255.255.255.0:0x00000001
192.168.1.170/255.255.255.0:/opt/test:0x00000001

On an NFS server I set up that is working, the /var/lib/nfs/xtab file contains
the list of hosts that have successfully mounted an exported FS. On the NFS
server that isn't working, xtab is empty.

And finally, a 'showmount -a' gives me a strange looking list such as this:
Hosts on hestia:
192.168.1.0/24:/opt/test
192.168.1.170:192.168.1.0/24
192.168.1.170:192.168.1.170/24
192.168.1.170:192.168.1.170/255.255.255.0
192.168.1.170/24:/opt/test
192.168.1.170/255.255.255.0:/opt/test
192.168.1.246:192.168.1.0/24

Thanks in advance for any feedback.

And what about the permissions on "/opt/test"?
Using chmod try giving full permission for all users on "/opt/test" and then see.

I tried playing around with the permissions again, but even
with the least restrictive permissions it still wouldn't work.

Thanks for the suggestion.

At this point I hope anybody who reads this will just fire out
any suggestions they can think of. If you know me, you'll
know that it isn't unusual for me to miss something obvious.

Just for good measure I have also tried rebooting back into
the same kernel and rebooting into a different kernel. Also,
TCP wrappers are not being used.