MS Access on samba share

[Ingo Steuwer]

Hello,

Am Mittwoch, 8. August 2007 23:48 schrieb 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.

for configuration questions you should contact the users list 
(samba at list.samba.org), this list is related to development questions.

[..]
> 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.

Locking should work with default settings. Documentation regarding 
oplock-Problems with Databases ist AFAIK outdatet, last time that I noticed 
problems was a 2.2-release of samba. Did you test on a share without any 
locking-options (remove also oplocks=no)?

Are you sure your application/database supports multi-user access?

> 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

AFAIK those are messages with a wrong debug-level but no real errors.

> The configuration of the smb.conf file is:
>
[..]
> [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/

Do you realy want to have two shares with the same path?

regards
Ingo

> 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.

-- 
** Besuchen Sie uns auf der CeBIT vom 15.-21.3.2007 in Hannover **
            ** Im Linux-Park - Halle 5 - Stand G57/3 **
------------------------------------------------------------------
Ingo Steuwer           Projektmanagement        steuwer at univention.de
Univention GmbH        Linux for your Business  fon: +49 421 22 232-43
Mary-Somerville-Str.1  28359 Bremen             fax: +49 421 22 232-99
                        http://www.univention.de