Hi, I had the same issue. In may case the `force group` option had the problem. If I removed it, there was no `read-only` problems.
I saw that your other shares have the same option, so it is a bit strange... You can also try to upgrade to version 3.2, as this `force group` problem is solved in that version. Regards, Tamas Csabina On Wed, 2008-03-05 at 18:22 +0100, Mister Olli wrote: > Hi... > > I wanna use samba 3.0.28 (on FreeBSD 7.0) machine just to serve some > shares with different content. > > We have several users, and access to a share should be managed by the > unix group a user is in. so if the user is a member of the group > 'business' he has access to a share called business. Every users has his > primary group set to 'users'. I implemented that for several groups: > - software > - internal > - business > - acquise > > everything works fine, except for the 'business' share. when a user > opens a word/powerpoint file, the file is opened as 'read-only' and you > can't save it under another name. This issue is only seen under > WindowsXP, and I wasn't able to reproduce it within VMware, so it have > to rely on the client maschine & users that actually have the problem. > > My config (testparm -v) is attached to this mail... > > > any suggestions how to fix that? my clients are currently pissed ;-)) > > regards, > olli -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
