Originally Posted by trickykid
NFS by far always provides some of the best logs. Check those. Permission problems are usually caused by the exports file. Sometimes even if there is Reverse DNS in place, I've had to put in the actual IP to allow a client to mount an NFS share. But check the logs, it should give some insight to why these clients can't mount the NFS share.
The server is a ServiceGuard cluster (system ovrhomes == ovrnfs1 + ovrnfs2), so the 'real' logs may not be where I think they are - still looking.
However, your remark about reverses led me to do some more snooping: there is definitely a disconnect between NIS and DNS. Interestingly, both of the names returned are in that netgroup, but my guess is NFS might suspect it's trying to be spoofed.
ovrnfs1:/etc/rc.config.d # cd /tmp
ovrnfs1:/tmp # nslookup ovresx2-vm2
ovrnfs1:/tmp # nslookup 220.127.116.11
So, I fixed the NIS map, but I still got the 'permission denied' error
For pure S&G, instead of using the 'front end' name (ovrhomes) for the mount, I tried using the cluster members directly (yeah, scold me later)
ovresx2-vm2:/var/log # mount ovrnfs1.rose.hp.com:/export/misc /tmp/misc
mount: ovrnfs1.rose.hp.com:/export/misc failed, reason given by server: Permission denied
ovresx2-vm2:/var/log # mount ovrnfs2.rose.hp.com:/export/misc /tmp/misc
Wow! It mounts like buttah!
So, I still have some sort of outstanding issue, I just don't know what it is yet. It appears that it's only the RH Server 5 clients doing this. I have 21 AIX, 132 HP-UX, 60 RedHat, 72 Solaris, 5 Solx86, 6 SuSE, 4 Tru64 and a couple of FreeBSD clients - that all work correctly.