Bug 6574 - Can't rename files on a samba share
Summary: Can't rename files on a samba share
Status: RESOLVED INVALID
Alias: None
Product: Samba 3.4
Classification: Unclassified
Component: User & Group Accounts (show other bugs)
Version: 3.4.0
Hardware: x86 Solaris
: P3 normal
Target Milestone: ---
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-26 18:28 UTC by Karim Elatov
Modified: 2020-05-17 20:03 UTC (History)
0 users

See Also:


Attachments
Samba logs of my successful login (116.04 KB, text/plain)
2009-07-26 18:30 UTC, Karim Elatov
no flags Details
samba logs of when it fails to rename a file (18.86 KB, text/plain)
2009-07-26 18:32 UTC, Karim Elatov
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Karim Elatov 2009-07-26 18:28:18 UTC
Here is my smb.conf
===================================================================
[global]
workgroup = AD
realm = AD.COLORADO.EDU
password server = dc11.ad.colorado.edu dc12.ad.colorado.edu
security = ads

winbind separator = +
idmap config AD:readonly = yes

encrypt passwords = yes
passdb backend = smbpasswd

hosts allow = 128.138.

log level =  10
log file = /var/log/samba/log.%m

# Put a capping on the size of the log files (in Kb).
#   max log size = 50

[homes]
        guest ok = no
        writeable = yes

[tmp]
        path = /tmp
        writeable = yes
================================================================

when I log in with smbclient it logs in fine and authenticates via the ad properly and it maps my UID properly fine but I cannot remove or rename files. Altough I am able to upload files.

The contents of log.moxz (moxz is the machine name) when I login is in the attachment called "log.login"

the contents of the same file (log.moxz) when I try to rename the file is in the attachment called "log.rename"

and here are it looks like from the command line
===================================================================
moxz:~>ls -l k
-rwxr--r-- 1 elatov pitserver 54 Jul 24 08:10 k

moxz:~>getent passwd elatov
elatov:x:17227:150:Karim Elatov,,, :/home/pitserver/elatov:/bin/tcsh

moxz:~>smbclient //moxz/elatov
Enter elatov's password: 
Domain=[AD] OS=[Unix] Server=[Samba 3.4.0]
smb: \> rename k j
NT_STATUS_ACCESS_DENIED renaming files \k -> \j 
=================================================================

If I do the same thing with on the /tmp share then it works fine it looks like this
=================================================
moxz:~>ls -l /tmp/a
-rwxr-xr-x 1 elatov pitserver 165 Jul 25 13:29 /tmp/a

moxz:~>smbclient //moxz/tmp
Enter elatov's password: 
Domain=[AD] OS=[Unix] Server=[Samba 3.4.0]
smb: \> rename a b
smb: \
======================================================================

as you can see no error was produced.

here is the info about my machine
===========================================
moxz:~>uname -X
System = SunOS
Node = moxz.colorado.edu
Release = 5.10
KernelID = Generic_141415-05
Machine = i86pc
BusType = <unknown>
Serial = <unknown>
Users = <unknown>
OEM# = 0
Origin# = 1
NumCPU = 
============================

I am really stumped as to why the ad mapping is properly getting set but yet I get an "access denied error".

Any help is much appreciated.
Thanks
-Karim
Comment 1 Karim Elatov 2009-07-26 18:30:37 UTC
Created attachment 4472 [details]
Samba logs of my successful login

This is the first attachment
Comment 2 Karim Elatov 2009-07-26 18:32:21 UTC
Created attachment 4473 [details]
samba logs of when it fails to rename a file

this is second attachment
Comment 3 Rob 2009-12-15 14:36:55 UTC
I've also observed the same problem on Ubuntu 8.04 running Samba 3.0.28a.  I cannot rename top-level directories or files on a Samba share, and I also cannot delete files in the top level of the share.  However, I can rename and delete directories and files that exist in a subdirectory of the Samba share.
Comment 4 Björn Jacke 2020-05-17 20:03:04 UTC
sorry for the lack of feedbakc but this is not a bug, please consult one of the options from https://www.samba.org/samba/support/ if this is still an issue for you.