MS Access on samba share

[Neha Patel]

Hi,
 
I have had no reply to the below email. I would appreciate any
suggestion you may have on how we can troubleshoot/resolve this problem.
 
Thanks
Neha.
 
-----Original Message-----
From: Neha Patel [mailto:npatel at nevi-soft.com] 
Sent: 03 August 2007 11:51
To: 'samba-technical at lists.samba.org'
Subject: 
 
Hi,
 
I have a client running Red Hat Linux 3.0 AS with samba 3.0.22.
 
Everything is working fine with samba and accesses samba shares from XP.
Recently, they have put MS Access database on the server for multi-user
access via samba share. We have tried setting the 'veto oplock files' on
the share to allow multi-user access on the access database file but the
access is restricted to only one user at a time i.e. if one user is in
the database, no other user is able to get into the database. Users do
not get any errors either to say the file is locked or in use.
 
We have noticed following error in the samba log file for machines
trying to access the database:
 
[2007/07/30 09:00:59, 0] lib/util_sock.c:write_data(556)
  write_data: write failure in writing to client 192.168.0.103. Error
Connection reset by peer
[2007/07/30 09:00:59, 0] lib/util_sock.c:send_smb(764)
  Error writing 5 bytes to client. -1. (Connection reset by peer)
[2007/08/03 10:13:25, 0] lib/util_sock.c:get_peer_addr(1225)
  getpeername failed. Error was Transport endpoint is not connected
[2007/08/03 10:13:25, 0] lib/access.c:check_access(326)
[2007/08/03 10:13:25, 0] lib/util_sock.c:get_peer_addr(1225)
  getpeername failed. Error was Transport endpoint is not connected
  Denied connection from  (0.0.0.0)
[2007/08/03 10:13:25, 0] lib/util_sock.c:write_data(556)
  write_data: write failure in writing to client 192.168.0.103. Error
Connection reset by peer
 
The configuration of the smb.conf file is:
 
# Global parameters
[global]
        netbios name = LINUX
        server string = Samba Server
        workgroup = BRANDY
        null passwords = yes
        password server = BRANDY
        username level = 8
        log level = 3
        log file = /var/log/samba/log.%m
        max log size = 50
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        os level = 0
        dns proxy = No
        hosts allow = 192.168.0.
        remote announce = 192.168.0.20
        comment = Linux Server
        guest account = ftp
        unix password sync = no
        security = user
        password level = 0
        preferred master = no
        domain master = no
        wins support = no
        dead time = 0
        debug level = 0
        username map = /etc/samba/smbusers
        load printers = no
 
[homes]
        comment = Home Directories
        path = /u/users
        writeable = yes
        create mask = 0666
        directory mask = 0777
        guest ok = Yes
        oplocks = no
        veto oplock files = /*.mdb/*.MDB/*.ldb/*.LDB/
 
[netlogon]
        comment = Network Logon Service
        path = /u/users
        writeable = yes
        force create mode = 0666
        directory mask = 0777
        guest ok = Yes
        share modes = No
        oplocks = no
        veto oplock files = /*.mdb/*.MDB/*.ldb/*.LDB/
 
Is this a problem with 3.0.22 release or do we need to do anything else
on the samba configuration? 
 
Thank you for your help in advance.
 
Neha.