samba - Jan 2004 - Re: Strange behaviour WinHP and 2.2.8a and inherit permissions

>> > ... I don't see anything wrong with it, although
>> > my working equivalent of your [Dokumente] looks a little
>> > different:
>> >
>> >  [Dokumente]
>> >        path = /daten/shares/dokumente
>> >        read only = No
>> >        map system = No
>> >        inherit permissions = Yes
>> >        security mask = 0777
>> >        directory security mask = 0777
>> >        oplocks = No
>> >
>> 
>> Some more differences that would have been easier to pick
>> had you smb.conf been reduced to non-default essentials:
>> 
>>   [global]
>> ...........
>>       dos filemode = Yes
>>       mangle case = Yes
>>       character set = ISO8859-1
>>       map system = Yes
>>       map hidden = Yes
>> ...........
>> 
>> It doesn't strike me as possible cause but you can never 
>> dismiss the possibility of side effects even in a well done 
>> software suite like samba.
>
>[global]
>	workgroup = ARBEITSGRUPPE
>	server string = Samba Server
>	encrypt passwords = Yes
>	map to guest = Bad User
>	time server = Yes
>	unix extensions = Yes
>	socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
>	printcap name = CUPS
>	os level = 2
>	local master = No
>	domain master = No
>	printing = cups
>	veto files = /*.eml/*.nws/riched20.dll/*.{*}/
>[homes]
>	comment = Home Directories
>	valid users = %S
>	read only = No
>	create mask = 0640
>	directory mask = 0750
>	browseable = No
>[print$]
>	comment = Printer Drivers
>	path = /var/lib/samba/drivers
>	write list = @ntadmin root
>	force group = ntadmin
>	create mask = 0664
>	directory mask = 0775
>[Dokumente]
>	path = /daten/shares/dokumente
>	read only = No
>	inherit permissions = Yes
>	oplocks = No
>
> Map system, security mask, directory security mask dont show 
> because the values you have given are default values 
Default for map system is "No". But since it is "Yes" in
[global], in order to make it compatible with some M$ dirty
tricks in user homes and profiles, it is only redefined "No" 
in this share. Some side effects from first enabling and 
then explicitely disabling might be what's missing. Or else
your smb.conf is basically the same as mine, in which case
you need to try to debug it.

There's also bug #51 which might be the cause of your problem
although it was defined in other terms. I had a problem that
excel sheets didn't open from paths containing German Umlauts.
Since I never checked if the bug persists without inheritance
it might be the same problem with different symptoms. There's 
a bugfix for that in Samba's bugzilla here:

  https://bugzilla.samba.org/show_bug.cgi?id=51
> The only different option was oplocks but it did not make 
> any difference. 
>
> Perhaps I get a little time this evenig and try samba3 or 
> going back to 2.2.6 wich worked fine.
That would be a pity and a security risk.