similar to: request_oplock_break: no response received to oplock break request

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

I saw a little discussion about this a few weeks ago but nothing concrete. We're running samba-1.9.18p8 under Solaris 2.6x86. I am periodically getting the following in the logfiles, usually _many_ at a time: 1998/11/03 14:42:00 request_oplock_break: no response received to oplock break request to pid 5411 on port 40884 for dev = 1980040, inode = 33c4d When I look up the PID (in this case

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

skeet@Bridgewater.EDU wrote: > > > Basically what it looks like to me is that an smbd process is spawning a > child which goes defunct for some reason I have yet to determine and the > smbd process hangs out there waiting for the child. Of course the child is > never going to answer being defunct, so the parent smbd process sticks > around and keeps its oplocks. > That

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

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

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:

Hi all, I increased the log level, and found something very interesting out. I know now what causes a sbmd to go into infinite hibernation on Solaris. I do not know why, it is probably something Solaris specific, I thought that a "dont descend" would have resolved my problem, but it has not. details at the end. Scenerio: solaris 2.5.1 running samba 2.0.0 (happens w/ several if not

Hi all, We have a HP-UX 11i server running as a samba server. Users use Windows 2000 boxes with Service Pack 4 to connect to the samba server. Several days ago, we upgraded samba server from 2.0.7 to 3.0.5, and we started to experience the following problem: The general connection and access to the samba server is ok. However, under the samba share there have been some directories mounted from

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

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.

For some strange reason, a samba setup which was previously working has suddenly stopped working, and I can't figure out why. The symptoms is that attempts to write some files onto a samba filesystem take a long time, and then error out with the error message (in Windows dialog box): "Cannot create or replace <filename>: The specified network resource or device is no longer

Has anyone tried using Windows 2000 Professional with Samba? I'm checking it out now, and when I try to connect to a share, I get an error message similiar to the one you get with Win98 and NT4 with SP3+ with encrypted passwords. Does anyone know the equivelant registry path to set plain text passwords? The NT4 path doesn't seem to exist:

First... Hi. Im new in the list and I want to say Hello Second. Apologies because my english writing is too bad. I haven't problem to read. But the verbs and syntaxis when I write is too bad. I will try to read the list without write. I write now because I have a big problem. In this right moment Im downloading the entire archive lists and I will try to ask less. I have a samba server and the

Hi, I've got a Samba server here that runs great! I've got an NT machine on my laptop and I can interface with the Samba server directly in any way I want, except for one thing: When I try to install a program (Visio) as a network shared app, the installation always tells me "I've determined that the target drive doesn't support long file names" after I choose to

We're using CentOS samba for about 20 workstations, mostly XP, some 2000 and two win98. Samba shares a data directory with Word, Excel and Access documents/db's. Also Exact for Dos is running from this share (executable and data). The users experience a long delay every morning opening the first Word document (Word 97, Word 2000). This could take 10 minutes or so. If they close

Hello, last friday I switched my users from an old server running 2.2.12 to a new one running 3.0.10 (that I've been testing myself and with smbtorture). After a while I had to switch back to the old server because some users were having serious problems. This is one of the logs (the others are very similar): [2005/03/04 12:25:05, 0] tdb/tdbutil.c:tdb_log(725)

Hello, I am running Samba 2.2.2 with acl-0.7.16 on RedHat 6.2 (2.2.19). The PDC is a Windows 2000 Server and the Samba server is a domain member using Winbind. All the workstations are Windoze 2000 Pro with SP2. Everything seemingly works fine but every day or two I get a runaway SMBD process which hogs the CPU and becomes unkillable. The only resolution is to reboot the server completely.