NFS server not responding
 

I have a large Solaris network with 8 Redhat Enterprise machines. At the weekend I took down the main NFS server. All the solaris machines reconnected fine. Two of the Linux boxes had a fit....an application failed to run and when I went to the accounts home area I got an error and had to remount the share...is this normal? Can RH not handle an NFS disruption...or is there something else needed (some local NFS settings).

Cheers,

I think this is normal. NFS can be a bit of a bear, and clients can have a hard time handling the sudden loss of shares they expect to exist.

I am not sure if what I am going to say is what you expect. But in NFS client's fstab file, you can include a option called 'soft' which will not hang the system even if the connection to the remote nfs share is not obtained.

You could also try the bg option which will background the connection.

I am having problems connecting to a nfs server, i have tried hard mounting and soft mounting it, ive checked that nfs is running on client and sever, portmap on both, checked exports.

They can both ping each other without any problems

All i am recieving is mout: RPC:Remove system error - Connection timed out


any help apprechiated

you might want to check your /etc/hosts.allow and /etc/hosts.deny files to make sure you are allowing the proper nfs/portmap protocols.

sorry i should of replied to this message along time ago.
I had the ports closed on a firewall.