similar to: 2.2.2 runaway SMBD process

Hi Alexander, Not sure if this of any help, but we had a similar problem with runaway SMBDs and what seemed to be oplocks. We are running RH6.2 with 0.7.26 ACLs. After much messing around and hassling Jeremy, I eventually changed the kernel from 2.2.19 to 2.2.20 and recompiled everything from scratch. Since then we have not had one of these rogue processes. I think Jeremy was right when he

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

Jeremy, Bit of bad news - we had a another runaway SMBD. This time profiles were NOT involved - I was simply copying up an installation of Office2000 and then deleting it. It almost reached the end of the deletion when the processor utilisation went up to 90%. The client connection then dropped with a 'connection is no longer available' and there is now 99% processor utilisation on the

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

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

Hi all, Jeremy, after trying to add kernel oplocks = no I got the same errors as describes in my last post. (samba working, but some folders not accessible, even not from commandline unix, can't kill smbd processes......) This is what happens in the log file: any ideas ? [2001/11/29 16:13:00, 1] smbd/service.c:make_connection(610) pc08ust (10.21.1.8) connect to service exchangejg99 as

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:

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

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

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:

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

<Long Post, sorry!> Folks, I have a really nasty problem preventing me from migrating a bunch of NetWare 5 servers to Samba--attempts to copy large (> 2MB+) files to any samba share results in an error. To clarify what I mean by "error": 1. I attempt to copy, using explorer, a 2MB+ file to any samba share. 2. A 30 second or so pause occurs (copying this file to any other

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'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)

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

Hello, i am running Samba 2.2.3a on a Red Hat Linux 7.3 box with kernel 2.4.18-10. I am experiencing some problems on a particular samba share, which is accessed by 10 Windows 98SE clients working on a COBOL production packet by mapping with a G: letters this samba folder. Well, some times a day it happens that this packed blocks because some files on that samba folder remains locked; i