Thanks Rainer,

I am using IP @ and here is the command I launched :

server_export server_2 -P nfs -option anon=0,rw=10.184.165.166,root=10.184.165.166 /test_NFS_MS/test_NFS_MS

and here is the output of this command : server_export server_2 -list

export "/test_NFS_MS/test_NFS_MS" rw=10.184.165.166 root=10.184.165.166 anon=0

if anon=0 works then putting the server into rw+root has to work as well

Most likely you made a mistake in the export

are you using a name or an IP there ?

most likely resverse lookup for the name doesnt work or the server is using a different IP than you thought

then most likely the client is using a different IP

take a network trace you should quickly see what IP is used and which UID is sent over the wire

Also check which users Windows is mapping to anon and which to root

This is how it work on a Unix/Linux NFS client:

NFS client just sends the NFS request with the users UI/GID to the NFS server - no mapping

on the NFS server:

if the client IP/name is in the root=list then the request gets handled with root access rights

if the client is not in the root= list the NFS server remaps root uid 0 to anon uid 65535

if anon=0 is set for the exports than for any NFS request anon is mapped back to root

if no anon=0 then the requests with anon are evaluated against the others in the owner-group-others rights

IF Windows is mapping other users than root to anon then just using root= wont work

Then you need to configure the user mapping in Windows

see the Windows NFS client documentation for details

clear ?

To be honest not that much. I'm not that savy with windows server. Thank you anyway I'll look more in depth. Thanks.

Windows NFS client info is readily available from Microsoft support web sites