Poor response time when accessing directories mounted on different subnets or NFS server hostname not responding

netstat -rs

NFS requests being routed 

Keep clients on the subnet directly connected to server. 

Poor response time when accessing directories mounted on different subnets or NFS server hostname not responding

netstat -s shows

incomplete or bad headers, bad data length fields, bad checksums. 

Network problems 

Check the network hardware. 

Poor response time when accessing directories mounted on different subnets or NFS server hostname not responding; sum of input and output packets per second for an interface is over 600 per second

netstat -i

Network overloaded 

The network segment is very busy. If this is a recurring problem, consider adding another (le) network interface.

Network interface collisions are over 120 per second 

netstat -i

Network overloaded 

Reduce the number of machines on the network or check the network hardware. 

Poor response time when accessing directories mounted on different subnets or NFS server hostname not responding

netstat -i

High packet collision rate (Collis/Opkts>.10)

- If packets are corrupted, it may be due to a corrupted MUX box; use the Network General Sniffer product or another protocol analyzer to find the cause.  

- Check for overloaded network. If there are too many nodes, create another subnet. 

- Check network hardware; could be bad tap, transceiver, hub on 10base-T. Check cable length and termination.