similar to: Oplock problem in 2.0.7 locks up Samba completely

I've used oplocks = no for a long time now, because of the famous "oplock_break" error, but I decided to give 2.0.7 a try. I still get "oplock break" errors as before, but this time I got a new error too: [2000/05/02 10:04:52, 0] smbd/oplock.c:oplock_break(976) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file XXXXX/xxxxxx/mailbox.pst

Hey, i build my first Linux Server in Oktober 2001. Everything works fine. At the end of Februar 2002 i got a problem. Please see the logfile. [2002/02/25 09:02:15, 0] smbd/password.c:domain_client_validate(1563) domain_client_validate: could not fetch trust account password for domain NENN [2002/02/25 09:02:47, 0] smbd/oplock.c:request_oplock_break(997) request_oplock_break: no response

Hello All, this morning, after rebooting our samba-testserver to activate some patches, we continuously got this error: [1999/02/18 09:53:29, 0] smbd/oplock.c:(943) request_oplock_break: no response received to oplock break request to pid 1650 on port 1230 for dev = ff000009, inode = 53134 [1999/02/18 09:53:40, 0] smbd/oplock.c:(943) request_oplock_break: no response received to oplock break

Hello, I'm running a samba 3.0.14a server in production on a fedora core 3 (kernel 2.6.9-1.667smp) with a least 250 clients (XP Pro SP2) (up to 400 sometimes). A few days ago, a problem appeared with a soft that we are using for a long time. (Petit Robert, a french dictionnary). When someone launch the dictionnary, many clients are freezed when they try to access to the "start

Hello, I've been running samba 2.0.7 for a couple years now on a DEC alpha with Tru64 4.0D. I't pertty much a default smb.conf as far as oplocks & that sort of stuff. Anyway, the other day some users started having troubles with saving ms-word files. The smbd processes have always been running as root. But now the users with the problem own their smbd process. And they get

We run samba 2.0.3 and it works fine since several weeks, until these days... Since two days I get lots of problems with samba. Oplocks seems to cause troubles, and it crashes MS Word in such messages: "unrecoverable network error" indefinitely until Dr Watson (under NT). We run 2.0.3 with samba as PDC. Quite all the clients run NT 4.0. Here is the entry I encounter very often in the

Hi everyone, Trying to copy a 3.5MB file from a Windows 2000 workstation to a FreeBSD 4.6.2 server running samba-2.2.6.p2. The 3.5MB file is an MS Access file called MoldFE.mdb. After a few seconds of copying the file, a message box pops up on the W2K workstation that states "Cannot copy MoldFE: The specified network name is no longer available". In /var/log/messages, I see this:

I am writing this to help those that have experienced the problem of clients having problems with the Samba Shares and the error noted in the logs is the dreaded oplock issue. Perhaps this would be a good addition to the FAQ. Start of oplock analysis ---------------------------------- We spent a 48hr session trying to solve this, it turn out to be a hub, Started with the oplock condition and

Hi- I've used the same smb.conf for many such file servers: one big share the office can write to, share level, no passwords. But I've never had the following error, and can't find the same combo of errors on the web either. They are MS works 2000 databases. If a client opens one, then closes it, no other client can access the file (it will hang indefinitely) until the original

Hello, I've set up samba 2.2.1a on a Linux box as a PDC for a bunch of NT4SP5 clients. This works quite nicely. All applications work as they should, except Office, which complains about a failure to initialize user32.dll. If I turn all users into domain admin, of- fice works as it should. Some of the PCs run with FAT (I know it's bad, but it was already so when I started to

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

Hi all, I've posted a similar message a few weeks ago. I had the 'oplock' problem. I run a linux server with samba (specification below). I get a reply who told me to disable kernel oplocks and oplocks. I did exactly what he told me to do. I hoped it worked... but it did not... From there one i started reading in the archives and followed the 'lock' discussions in this list.

Dear All, We are in the process of evaluating Samba to provide SMB access to unix file storage for a few hundred PC's. One of our tests is to save a Word97 document - something that has caused various PCNFS clients problems in the past. While saving the document the client stopped and said something like connection lost, or seesion closed, and the drives mapped from the samba box

When trying to delete or copy over certain files on my Samba server, Windows hangs for some time and then gives "access denied". I can delete these files directly from the server, so it's a Samba or Windows problem. There seems to be nothing special about these files, other than that Samba doesn't like touching them. Upon checking the Samba logs, I find this message or

we are running Samba 2.0.6 on a solaris 7 (intel) box. Users (about 270 at one time) connect to the home directories located on the samba server by NT 4 workstations . Problem is ..Some times they lose access suddenly .In the log files the following message appears ?------- [2000/08/22 08:28:09, 0] smbd/oplock.c:request_oplock_break(1202) request_oplock_break: no response received to oplock

Users are trying to cennect to their home dirs ... the request_oplock_break is failing: [1999/10/21 10:50:39, 1] smbd/service.c:make_connection(521) gpnte109i (137.94.128.183) connect to service s22350 as user s22350 (uid=22350, gid=34) (pid 27704) [1999/10/21 10:50:54, 0] smbd/oplock.c:request_oplock_break(1136) request_oplock_break: no response received to oplock break request to pid 25867

I hope someone can enlighten me on this. Situation: NT network, Samba PDC, about 20 NT 4.0 workstations. log(s).smbd are created per machine for easier analysis (as log.smbd.<NetBios Name>). Not often, but often enough to be of concern, are errors in request_oplock_break that seem to indicate that another smbd process that should be listening for break requests on a UDP socket

Server is PII-350MHz/256 MB RAM, hardware mirrored high speed SCSI disks. Installed is SuSE 8.2 with Samba 2.2.8a RPM, XFS filesystems and LPRng as printservices. Server acts as PDC and WINS server. Clients are W2K SP2 (a few with SP3). There are +/- 100 clients. We see a server that is 100% busy and we see during a long time a very high CPU load (60- 95%) related to one W2K client. When

I've seen a couple mentions of trouble w/ large files in the list archives, but nothing that seems to resolve this problem... When trying to move or copy largish files (~ >1MB) with WinN using Samba 1.9.18p10 on a Sparc Solaris 2.5 system, things hang for a while and then a dialog box pops up saying "Cannot copy {filename}: The session was cancelled. I've tried setting

I'm running samba 2.0.7 on Solaris 2.6. We've have terrific success for well over a year with samba until about a week ago I started receiving reports that users could not open MS Office docs saved on a samba share. The samba logs are full of information about oplocks like this: [2001/03/07 10:14:04, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response