similar to: error packet at smbd/blocking.c(318) cmd=36 (SMBlockingX) NT_STATUS_FILE_LOCK_CONFLICT

I have a linux server that I'm preparing to migrate our samba services to. It has been running as a stand alone server and I intend to set it up as a PDC - we have another old system working as a PDC now. Because of some problems during samba testing (quite awhile ago) I decided to upgrade the samba version running on the server - the original packaged samba was 3.0.20 and I downloaded

I am running two Fedora 13 servers, one as a Samba PDC and the other as a BDC. For the past week I have been tracing a series of issues which may or may not be related to Samba 3.5.4. Here is one problem that I am tracking and need help from the list with suggestions. >From a wireshark trace between my Samba server and an XP client I am seeing the following error status returned for up to a

-----BEGIN PGP SIGNED MESSAGE----- ******************************************************************** The contents of this email are intended exclusively for the addressee. If you are not the addressee you must not read use or disclose the email contents ; you should notify us immediately [ by clicking "Reply" ] and delete this email. Nationwide monitors e-mails to ensure its systems

I am able to connect to my printer connected to my Mac (OSX 10.4.6) from both the Mac itself and from a Linux machine: $ smbclient "//MINI/HP LaserJet 5L" But, when I try to test printing, I get an error: $ smbclient "//MINI/HP LaserJet 5L" Password: Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.10] smb: \> print test.txt Error writing file: NT_STATUS_FILE_LOCK_CONFLICT

I think the message title says it all. I was attempting to do 'make test' against 3.0.23d and include the smbtorture4 tests from 4.0.0tp3 (as I read somewhere to be a good idea). Is there any reason that the test should not work? Does it have something to do with the 'unknown parameter'? Make test works fine without smbtorture4. Platform is Solaris 9 on sun4u. Samba 4 was

Hi all, I've got kind of strange setup, wherein all of my data is on a big NFS server (RH linux 8.0 running the 2.4.18 kernel and nfs-utils 1.0.1-2.80) and my Samba 3.0.0 PDC server (RH linux 7.3 w/ 2.4.18 kernel, nfs-utils 0.3.3-6.73) mounts the NFS export with the following options: rw,vers=3,wsize=8192,rsize=8192,hard,intr This mounted partition is then re-exported to the windows users

Hi all, I have been a loyal user of SAMBA since about 1996(?), and I recently upgraded a RH linux based system from by skipping a few generations and going directly from rh9 to FC5. Mostly everything is working, but there is an issue I haven't worked out yet with SAMBA. The main server here in our group has several shares, including some that are mounted from other servers via nfs,

Hi! Been having the same problem with oplocks for a while and have been trying to figure out what's going wrong. The FAQ says that we may have a networking (hardware?) problem, but according to the Linux box's ifconfig results, we have had no errors and no dropped packets on the internal network. I am able to reproduce the error pretty much at will on our network, and it is not isolated

I'm attempting to install Abacus Law (v13) under Samba and Linux. Install completes, and I get as far as a single user successfully logged in, but the 2nd user is nothing but trouble. Samba logs show nothing unusual to my semi-trained eye, but locking code or timing is a likely suspect. Technical support is of no help as they haven't tested (and therefore don't support) the

http://dovecot.org/releases/2.0/dovecot-2.0.11.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.11.tar.gz.sig Looks like v2.0.10 was a bit troublesome release. I expect this one to last longer. * dotlock_use_excl setting's default was accidentally "no" in all v2.0.x releases, instead of "yes" as in v1.1 and v1.2. Changed it back to "yes". - v2.0.10:

http://dovecot.org/releases/2.0/dovecot-2.0.11.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.11.tar.gz.sig Looks like v2.0.10 was a bit troublesome release. I expect this one to last longer. * dotlock_use_excl setting's default was accidentally "no" in all v2.0.x releases, instead of "yes" as in v1.1 and v1.2. Changed it back to "yes". - v2.0.10:

Hi, I'm trying to get sieve working with dovecot. I seem to have everything enabled but my scripts done seem to work. both sieve-filter (2000) and sieve (4190) are running along with pop3 and imap. I have a simple script which checks the email address and moves it to a folder. I'm at a loss as to what to check next. Thanks in advance, Matt

Hi, I sent a mail a few days ago to this list related with GFS+samba problems. Since the, we have installed a sepparated test environment also with two linux servers where we have tested a samba server with an exported share in GFS. The share is read-only and only one server is exporting it. When we try to access from a single windows client it works fine, but when we try to access to the

Debian Woody with security updates Linux kernel 2.2.25 Samba 3.0.0 libc6 2.2.5 The problem I have is with a windows application that uses samba. This application is crucial for the organization, so if this is not fixed, and soon, we will have to ditch Samba and move to a windows server. I *really* don't want to do this, as Samba has been working so well for years now and billg is rich enough

I'm hoping someone has some insight into a problem I'm currenty having, which is: No one is able to edit (in place) documents with Word 2000 on a samba (2.2.6) disk share. A user can open word and save a document to the share, but when they go to edit the document Word says "Word cannot complete the save due to a file permission error". From Microsoft KB Q211632 it appears

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Since we started our new Samba + LDAP backend server yesterday some (not all) PC we have a problem with Word and Excel files that are marked "read-only" when users are trying to open them from their Samba network shares. This happen ONLY for *.doc and *.xls files , if we open and save a *.html file with Word it works ... Any

Hi there ! I just upgraded (last friday night) our main Samba host to Samba 2.0.0 from version 1.9.18p10. This host provides access to our own file based database system. The number of Samba clients is around 60 (nearly all NT4.0's and few NT3.51's). The Samba 2.0.0 host runs 'uname -a': HP-UX vertex A.09.05 A 9000/720 65914162 two-user license After the upgrade change I've

I'm trying to solve a roaming profile problem which manifests as a locking error during Win2K logout with roaming profiles enabled. Level 3 debug tells me: [2002/05/30 11:59:58, 2] smbd/open.c:open_file(213) markk opened file markk/ntuser.ini read=Yes write=Yes (numopen=1) [2002/05/30 11:59:58, 3] smbd/process.c:process_smb(860) Transaction 1449 of length 75 [2002/05/30 11:59:58, 3]

I am observing the following behaviour with samba-2.2.12 (Yes, I know, it's old) and MS-Access XP on a Win2K box: The client opens a .mdb file and gets a level2 oplock. Then it opens the .mdb file again and loses the oplock (at least I assume it does: The server sends an SMBlockingX request to the client and waits for another SMBlockingX request from the client before sending the Reply to

There seems to be a few people having this problem, but not much response. I've dug into the logs, and while I don't know exactly what I am looking at, I think I may have found something that may make sense to someone. A short recap. Samba was working fine, until I did a Debian security update, which upgraded my Samba to 2.2.8a. Now, I can create files on a mounted Samba share in a