Both (NFS server/client) are on Solaris 10 x86.
drwx-----x 5 nobody nobody 512 Jun 25 16:04 userA
The NFS client does not have any user account. So that the
UID and GID are re-mapped to nobody as above. It does not
happen on NFS server in which Solaris 8 installed. How can
I get the correct UID/GID using NFS mounting as below:
drwx-----x 5 123456 123 512 Jun 25 16:04 userA
Thank you very much.
--
Johnson Chow
It sounds like they're using NFSv4, and have different NFSv4 domains.
Make the domains the same, or force them to negotiate NFSv3. Both
things can be done by editing /etc/default/nfs.
--
Chris
I just tried to set /etc/default/nfs :
NFSMAPID_DOMAIN=something.somewhere
and reboot in another set of NFS server/client.
There's no effect. Should I change to NFSv3? How?
--
Johnson Chow
Did you restart the NFS service on the server?
Do the client and server have the same domain name?
See the description of setting NFSMAPID_DOMAIN in the nfs man page.
--
Ian Collins
1. I had tried either init 6 or svcadm restart nfs/server .
2. Same domain name and NFSMAPID_DOMAIN both in NFS server/client.
3. I use "mount -o vers=3" to fix this problem. However,
I think that NFSv4 client is better. Anyone has solution.
--
Johnson Chow
Hi,
To have properly mapped credentials both client and server must be
able to resolve all involved user and group names (of course the NFSv4
domain names must also match). NFSv4 communicates user and group
information using strings (like "username@nfsv4domainname" and such).
NFSv3 uses numerical user/group IDs.
Client and server must be able to translate these "username@domain"
strings into numerical IDs and numerical IDs into "username@domain"
like strings. The numerical IDs don't need to be the same on
client and server though.
Ronald
--
* The whole problem with the world is that fools and fanatics are always
* so certain of themselves, but wiser people so full of doubts.
* --Bertrand Russell