Weirdness: MS Access Files on Samba NT Dom

[Todd Stiers]

I attempted to set   veto oplock file = /*.*/ for the share,
and still the Access file will not open.

Running debug level 4 shows the file being created, then cleared very
quickly:

  tas opened file testit.ldb read=Yes write=No (numopen=4)
  set_share_mode: Created share entry for testit.ldb with mode 0x8040 pid=8893
  call_trans2qfilepathinfo testit.ldb level=258 call=7 total_data=0
  tas closed file testit.ldb (numopen=3)
  unix_clean_name [/testit.ldb]
  unix_clean_name [testit.ldb]

(this was done using a grep on tail -f of log.smb)


Does "veto oplock file = /*.*/" not work or is there a better
way to try this? How do I know the veto is working?

Thanks
-Todd






gscherb at mriresearch.org wrote:

> I've had similar problems with Access 97.  I got it fixed by setting oplocks
> to false or setting veto oplock files for *.mdb, *.ldb, ?  I have similar
> problems with MS Outlook *.pst files.  Interestingly, NT 5.0 Beta 2 does not
> have these problems.  Microsoft has messed around with the SMB
> implementation.  NT 5 would force all filenames to upper case on Samba
> 1.9.x, but that behavior is gone on 2.0.2.
>
> Disabling oplocks slows performance a bit, especially when attaching data
> tables dynamically where the client app is on a workstation and the back end
> database is on a Samba server.  Once the links are attached, performance is
> great, even with several users.
>
> Glenn A. Scherb
> Programmer/Analyst
> Midwest Research Institute
> gscherb at mriresearch.org
>
> -----Original Message-----
> From:   samba-ntdom at samba.org [mailto:samba-ntdom at samba.org] On Behalf Of Todd
> Stiers
> Sent:   Wednesday, March 17, 1999 7:52 PM
> To:     Multiple recipients of list
> Subject:        Weirdness: MS Access Files on Samba NT Dom
>
> Hi,
>
> I have come across a very strange error since upgrading my servers
> to Samba NT Dom 2.0 (late January).
>
> Apparently, MS Access 97 files can no longer be opened and run
> from the Samba fileservers. I can copy the files to NT local machines,
> they work, I can put them on NT shares, MS Access works, and I
> can put them on samba 1.9x versions and it works.
>
> Whats changed? Was it/is it intentional?
>
> Currently, only windows 95/98 machines seem to be able to open
> the MS Access docs stored on Samba NT Dom servers.
>
> Access seems to create a locking file on real NT and real NT shares,
> but on neither of the Samba (NT Dom and regular).
>
> HELP!
>
> Thanks
> -Todd
>
> --
> [--- [--- [--- [--- [--- [--- [--- [--- [--- [---
> Todd Stiers
> Director of Systems Administration
> The MicroDisplay Corporation
> http://www.microdisplay.com (510)243-9515x129
> ---] ---] ---] ---] ---] ---] ---] ---] ---] ---]



--
[--- [--- [--- [--- [--- [--- [--- [--- [--- [---
Todd Stiers
Director of Systems Administration
The MicroDisplay Corporation
http://www.microdisplay.com (510)243-9515x129
---] ---] ---] ---] ---] ---] ---] ---] ---] ---]