[Samba] URGENT problem in production enviroment 3.0.23c-1
Sander van Harmelen
sander.vanharmelen at isp.solcon.nl
Mon Nov 13 12:51:20 GMT 2006
Inn the error:
Cannot read or set the permissions for file \\server\share\folder:
initializing the SD failed
Does SD stand for Security Descriptor?
I have a server that doesn't want to make new folders without giving
this error. This only applies to folders!! Files don't give this
I downgraded from 3.0.23c-1 to 3.0.21b-1 but that didn't solve it. It
did solve the
ntrol problem (acl group control)
Van: samba-bounces+sander.vanharmelen=isp.solcon.nl at lists.samba.org
[mailto:samba-bounces+sander.vanharmelen=isp.solcon.nl at lists.samba.org]
Namens S. J. van Harmelen
Verzonden: zondag 12 november 2006 19:18
Aan: samba at lists.samba.org
Onderwerp: Re: [Samba] URGENT problem in production enviroment 3.0.23c-1
Problem seems to be with the changed "acl group control" parameter. When
I try to change rights of a file from within Windows I get an access
denied (I'm not the owner of the file but I am a member of a group who
has rwx rights).
How can I regain this functionality? "dos filemode = yes" is already
set. I really need a solution, our customers are getting pretty grumpy.
On Sun, 2006-11-12 at 17:43 +0100, S. J. van Harmelen wrote:
> We use Samba as backend for an IIS webfarm (shared hosting). Some of
> customers are using Frontpage extentions to manage their site. Now
> uploading a new folder or file the users are getting:
> Cannot read or set the permissions for file \\server\share\file:
> initializing the SD failed
> When you click OK (you can only click OK at this point) the folder or
> file is created and the rights are also as the should be (even the
> ACL enties are fine), but the publication of the site is stopped and
> to be started again.
> So how to get rid of the above error? Now for every new file or folder
> our customers have the click on OK and start publishing again until
> hit the next new file or folder and then is starts over again.
> I have a logfile and a tcpdump from the same session where this
> but I can't find the solution in there. So if someone with a better
> want's to take a look I would be very greatful!! Just reply and I will
> send the log and the trace.
> Last bit of info: I've had this exact error before and at that time
> adding "acl group control" and "dos filemode" was the solution. But
> are still here now...
> Really hope someone can spare a few minutes!!
To unsubscribe from this list go to the following URL and read the
More information about the samba