similar to: Oplock Problems: Start HERE!!!!!!!!!

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

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

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

first of all: thank you all for you excellent work on Samba. However, I dare to complain about a problem with oplocks that of- ten plagues the server here. The server is used for just about everything, Samba is used for file and print services but also as a gateway to a Pervasive SQL database (via a named pipe). Usually after a few days of perfect function (just over two weeks at the last

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:

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

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.

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! 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

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 trying to troubleshoot slow performance. A lot of my NT client log files show messages like this about oplock break issues. [2003/10/09 12:50:39, 0] smbd/oplock.c:(1008) request_oplock_break: no response received to oplock break request to pid 2907 on port 61752 for dev = 40240002, inode = 29, file_id = 2 64 [2003/10/09 12:51:03, 0] smbd/oplock.c:(395) process_local_message:

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

Hi All, My problem started with new server hardware and software update, also I changed my network from 10 to 100Mb (New Cable and switches) I have a problem with oplocks. I run Samba 2.0.10 (also tried 2.2.1a) on Suse 7.1 Kernel 2.4. Several times a day I have an oplock error like this: (request_oplock_break: no response received to oplock break request to pid 5312 on port 32857 for dev = 803,

Hello there. I'm having a few problems using samba 2.2.3a and sharing a paradox database. On the whole everything works fine but (there's always a but), every now and again. a machine's shares will close causing the database to crash (sometimes only that machine) - the other networked machine recover after a few error messages. I guess the easy answer would be to disable oplocks

TEST: ===== SAMBA STRESS OVER GIGABIT NETWORK: This is a simple Read/Write/Compare/Delete kind of test over the network via Samba. Multiple clients with multiple threads try to read/write/compare/delete(in a loop) a finite sized file (64K block size) over samba for a prolonged period of time in an effort to stress test the server. SERVER SIDE CONFIG: =================== ARCH: x86 OS: RHL AS

Hello, all. I'm using Samba 2.2.2 at my FreeBSD 4.4-STABLE server, and have next problems: There is pool of W2K machines, each starting compilation job (usually 2 at one dual CPU machine). Then these jobs trying to simultaneously access sources, located at Samba server, appear problems. Then I running 2 compilation threads from single machine - there is no problems. For jobs error seems

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

Can someone please explain these smb.log entries??? [2003/08/26 18:58:31, 0] smbd/service.c:make_connection(381) fmouse logged in as admin user (root privileges) [2003/08/26 18:58:35, 0] lib/util_sock.c:read_socket_with_timeout(298) read_socket_with_timeout: timeout read. read error = Connection reset by peer. [2003/08/26 18:58:35, 0] smbd/oplock.c:oplock_break(758) oplock_break: