Tech support request (an odd one)

Greg Louis glouis at
Tue Oct 23 09:51:03 GMT 2001

On 20011023 (Tue) at 0748:39, Gerald (Jerry) Carter wrote
(and thank you for the reply):
> On Mon, 22 Oct 2001, Greg Louis wrote:
> > If anyone can suggest a fix or workaround for this, it would be much
> > appreciated:
> >
> > Since upgrading from 2.2.1a to 2.2.2 on a 4-processor Linux 2.2 server,
> > we have an interesting problem with Office 2000 applications, and
> > Microsoft Backup, on Windows 2000 clients: these programs cannot save
> > to the user's Homes share (an access-denied error message results).
> > Other programs, such as Eudora, can save to the Homes share; the Office
> > apps can save to other shares; and once saved, the files can be copied
> > to the Homes share and read from there.
> Use smbstatus and see if the file has been open with a RDONLY share mode.
> We think we have just fixed this in the SAMBA_2_2 cvs tree.
> You can apparently work around it in 2.2.2 by setting oplocks = no
> in the share.

Hm.  As mentioned in the smb.conf excerpt I sent with the original
question, oplocks were set = No globally:

        kernel oplocks = No
        blocking locks = No
        oplocks = No
        level2 oplocks = No
        posix locking = No

The interesting part is that saving to any (permitted) share but the
Homes share works fine.  The only difference I can see there is that in
all those other shares the user is explicitly named in the valid-users

We're looking into the question of the share mode.

| G r e g  L o u i s          | gpg public key:      |
| |   finger greg at |

More information about the samba mailing list