You may have marginal NIC cards on these machines. I notice that new cards tend to work a lot better. I don't know what these errors are.
SB -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ruben Fagundo Sent: Monday, April 08, 2002 4:51 PM To: [EMAIL PROTECTED] Subject: [Samba] Strange Problem with Access I posed the following problem a few weeks ago, and finally, I've had time to update the RPM for the latest samba Version 2.2.3a I added the following line to [global] veto oplock files = /*.mdb/*.MDB/*.ldb/ And the following line to the directory having problems. [public] locking = yes oplocks = yes veto oplock files = /*.mdb/*.MDB/*.ldb/ I am still having problems opening the Access database from certain computers. All other systems are working perfectly fine. There is no correlation to the version of Windows opening the database. If anyone has any more suggestions, I would really love to hear them. The orginial problem description is listed below. And a more detailed log file is attached. The file experiencing problems is called "AWC Supporters.mdb" The irony of all this is that this was all working perfectly fine with Redhat 5.2 ================================================= I am running samba on a RedHat 7.2 Athalon box with software RAID 0 dual IDE disks on an ext3 filesystem. I have several users in a large community of users that are always hitting the samba server. The machine has been consistently reliable with one exception. There is a particularly large MS Access Database (10Meg) that everyone likes to use. A problem has developed from certain Win 98 and Win95 computers where users get an error message saying that someone currently has a lock on the database, and that it cannot be opened. However, smbstatus, reports that the user is actually trying to establish a lock on a different file, not the database in question. To add to the strangeness, I have opened the database on a different computer, and then all of a sudden everyone else can now open it as well. In addition to that, I had the database open from a win 98 machine, and someone else (that had been experiencing problems) opened it up, but smbstatus reports that the 2nd individual had a second file open in addition to the database, and clearly there were no other files open on that computer, by that user. So, we have files opening and getting locked when they were not opened, and a database that only certain users can open, cause other computers are being told that it is already open, and locked by a different user. Can anyone tell me what the heck is going on here, and what is the answer to this apparent lunacy ??? Thanks, Ruben -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
