Red Hat

BH083108 seems to be using NFSv4 as rpc.idmapd is an NFSv4-ism.

how about turning off the cdrom if you think that's causing the problem. comment it out from fstab?

I think RHEL uses nfs 4 by default.

nfsstat should tell you running version

[root@BH083108 1]# nfsstat
bash: nfsstat: command not found

The hang problem does not happen any longer. I feel this has been resolved by specifying udp during the mounting process:
[root@BH083108 1]# mount -t nfs=3 rw,intr,udp con:/home /server
mount: fs type nfs=3 not supported by kernel


I am getting these errors when the instrument software is told to write the data to the remote nfs server. It creates all the necessary directories but when it comes to writing the data itself. For example I run a proton sample and define the path /server/<username> (server is the exported file system. Permissions UID are the way they should be. The application even goes to the extent of creating multiple directorys in my home directory, but no the data results. Then
/var/log/messages presents:
Sep 8 13:56:48 localhost kernel: lockd: server 128.186.184.148 not responding, still trying

Any IDEAS?

---------- Post updated at 04:22 PM ---------- Previous update was at 02:26 PM ----------

I think I figured it out:
mount -t nfs rw,intr,udp,vers=3 con:/home /server

---------- Post updated at 04:23 PM ---------- Previous update was at 04:22 PM ----------

I still have the errors though lockd server ip_address not responing