#NAS S3 Access failure

1 messages · Page 1 of 1 (latest)

hallow monolith
#

I have been testing NAS S3 functionality but it seems that I cannot actually make it work.

the volume and the bucket are created correctly,
I create the s3 user and the appropriate user mappings (both unix and windows even though security style is unix for the underlying volume)
I can ls the bucket but put always fails with

1/19/2026 18:25:54 estia11-01 ERROR secd.nfsAuth.noNameMap: vserver (estia11-s3) Cannot map UNIX name to CIFS name. Error: Get user credentials procedure failed
[ 0] S3 user 'nas-s3' mapped to UNIX user 'pcuser'
[ 25] Mapping Successful for S3 user 'nas-s3' to Windows user 'winuser' at position 4
[ 25] Could not find Windows name 'winuser'
[ 25] Trying to map user to the default Windows name 'winuser'
[ 25] Could not find Windows name 'winuser'
**[ 25] FAILURE: Name mapping for S3 user 'nas-s3' failed. Mapped Windows user 'winuser' does not exist

I have even tried mapping windows to unix ,
define and/or remove the default windows user in the object-store-server but always the same problem

NFS Server is enabled, SMB/CIFS is not

Anyone have any idea what I might be missing ?

humble portal
#

Maybe send the output of "vserver name-mapping show"

Looks like it is failing mapping the "winuser" -> does not exist

whole hare
#

is your root volume also UNIX style security? for some reason it tries to map to a Windows user which shouldn't be necessary