Comment 5 for bug 106401

Same problem with correct mapping for file listings but denied write access here in hardy, after avoiding bug #235930, which by the way might be useful for people who get "nobody,nogroup" mappings.

Running "rpc.idmapd -fvvv" on both machines showed me that id mapping was done from server numeric ids to names to client numeric ids, but apparently not the other way round. I haven't understood nfs4 enough to judge whether or not this is expected behaviour. I guess I'd need to read more of rfc 3530, as I can't fathom yet where in my wiresharked network traffic all this user authentication is supposed to happen.