In this case, we will have a 192.168.xxx.xxx IP for the internal facing interface. The file server is seeing the internal IP, not the external IP, and this is causing an issue. The problem seems to be that when connecting to the file server, that internal IP is being used as the system ID. We need a way to ONLY use the external facing IP, which is always unique.
In this case there are multiple NFS clients behind different firewalls. These NFS clients are configured to be identical. When these NFS clients access the same files on the NFS server it gets the following errors:
May 6 16:38:57 hosta kernel: NFSD: nfsd4_open filename .filename op_stateowner (null) May 6 16:38:57 hosta kernel: NFSD: warning: no callback path to client 192.168.xx.xx/yyyy.yyy.yyy.200 tcp UNIX 0: error -5 May 6 16:38:57 hosta kernel: NFSD: move_to_confirm nfs4_client ffffxxxxxxxxxxx
- Red Hat Enterprise Linux 6.3
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.