NFSv4-UID-GID-nobody Version 4 of the NFS protocol (RFC3530) changed the way user or group identifiers (UID or GID) are exchanged between the client and server. The protocol requires that a file's owner and group attributes be exchanged between an NFS Version 4 client and an NFS Version 4 server as strings in the form at user@nfsv4-domain or group@nfsv4-domain, respectively. If file owner (at NFS client side ) is user1 with UID 123456, nfs mapid daemon must match this UID "123456" with string "user1@nfsv4-domain". These all informations must also match at NFS server side. So, at first NFSv4 domain names must match both at NFS server side and NFS client side. NFSv4 domain names can be taken from DNS domain entry at /etc/resolv.conf but we prefer setting NFSv4 domainname to "localdomain" everywhere and override DNS domain config at our servers in the company. This way, we remove dependency on DNS and we make NFSv4 domainname unique and same everywhere by setting everywhere to same "localdomain" value and we dont live NFSv4-UID-GID-nobody problem. Because if NFSv4 domain names does not match at both NFS client and server, NFSv4 thinks that it could not find proper UID-GID values so it always displays nobody:nobody. Our Company Central NFS server is Linux. All AIX-Solaris-Linux clients mount their central package repositories from this Linux NFS server with NFSv4. Needed configs at NFS client side are below. Feel free to communicate by bulent.yucesoy@gmail.com - AIX NFSv4 client NFS domain name config [root@aix1]cat /etc/nfs/local_domain localdomain [root@aix1]stopsrc -s nfsrgyd [root@aix1]startsrc -s nfsrgyd [root@aix1] - Linux NFSv4 client NFS domain name config [root@linux1]cat /etc/idmapd.conf Domain = localdomain [root@linux1]service rpcidmapd restart [root@linux1]nfsidmap –c [root@linux1] - Solaris NFSv4 client NFS domain name config [root@solaris1]cat /etc/default/nfs NFSMAPID_DOMAIN=localdomain [root@solaris1]svcadm restart svc:/network/nfs/mapid:default [root@solaris1]