Well, it turns out that the smbstatus/Access column/0x3 condition is not the cause of the problem. (I still don't understand the significance of that column.)
A simple upgrade from 3.0.5 to 3.0.8 broke file sharing on a MSAccess 2k database (Win2k and WinXP clients.) There are Paradox databases on the same file-share that are working fine. The log files show no errors. I'm about to try increasing the debug level, but can anyone give me a clue in the meantime? Thanks, Lane Beneke --- Lane Beneke wrote: > This is really strange. > > The samba server in question is a domain member > server > on a Windows NT 4.0 Domain network. It runs Gentoo > 2004.3 with a 2.4.24 kernel. > > The Gentoo server was upgraded from Samba 3.0.5 to > 3.0.8 last night. After the upgrade, the server had > to be re-joined to the domain. After that, > everything > appeared to be working. > > This morning we found that the MSAccess database > files > can no longer be shared if the database users open > the > MDB file containing the tables. The first user in > can > use the database, and databases that are externally > linked to the database in question can share the > data > just fine. (Weirdness) > > A quick look at smbstatus output reveals that no > oplocks are placed on the MDB or the LDB files. > However, the "Access" column of the smbstatus output > shows 0x2019f for all files except the MDB files, > which show 0x3. Does anyone know what this means? > > 32748 DENY_NONE 0x3 RDWR NONE > /samba/common/smc.mdb > 32748 DENY_NONE 0x2019f RDWR NONE > /samba/common/smc.ldb > > Help! > Lane Beneke > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail - Easier than ever with enhanced search. > Learn more. > http://info.mail.yahoo.com/mail_250 > __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba