similar to: Has anyone seen this before?

Below are a number of errors that appeared in a log file today. I am running Samba v2.2.5 on a Red Hat Linux v7.3 system. The client experiencing/causing the errors below is a WinXP(SP1) machine. The log entries below pertain to 2 errors, the first in handling file "6.zip" and the second in attempting to run file "DiskeeperWks413zssi.exe". I didn't see the first

Hi all, I have the following problem. A Linux (2.2.19) machine is running Samba 2.2.2 as a PDC. The clients are Win2K SP2. A user accesses several Excel 2000 files on a share. This sometimes results in long(ish) delays (the user reports around 10 seconds, although this could be longer) and the message from Excel that the file is in use and can only be read. After closing and re-opening the file,

I am currently using samba to try and replace a windows NT box as the default print server. All is working well except for one printer driver. All drivers were installed from a win2k machine onto the samba print$ share. The problem that I'm having is with a driver for the HP laser jet 4000N printer. The PCL driver works and loads quickly. The PCL 6 driver works, but the properties

After upgrading from 2.0.10a to 2.2.4, I'm seeing many new messages being logged. What does this mean? Jun 5 09:42:50 files2 smbd[27585]: [2002/06/05 09:42:50, 0] smbd/oplock.c:oplock_break(788) Jun 5 09:42:50 files2 smbd[27585]: oplock_break: no break received from client within 30 seconds. Jun 5 09:42:50 files2 smbd[27585]: oplock_break failed for file

I'm currently using Samba 2.2.5 on a Mandrake 8.0 box with cups 1.1.4. I have several printers shared that are accessed from winNT/2k/xp boxes. When I right click on the printer or select printer properties, or go to print from any of those other boxes, the response is slower than molasses. I have an identical machine running WinNT Workstation that was previously our print server. It is

Can any one help me ? This has been bugging me for ages. I have been using different versions of samba for a while on different versions of Redhat (7.0, 7.2, 7.3). I regularly get erratic freezing (for about a minute) whenever I right click on files. This has happened on different computers on different sites on different networks, so I assume it's quite consistent This is what I get when

Well I'm having some trouble with samba, I had those troubles on a box for quite some time and not long ago I moved all the stuff to a new box to see if it'll work better but it doesn't. I'm monitoring one person in particular because she's the one who do most of the editing stuff in there. What happens is when she opens a document (.doc or .xls most of the time), when she

Guys, I think the answer to my question is to upgrade samba. However, since this is my production machine, I thought I would try and understand the problems I'm having a little better to insure that an upgrade will correct my issues. My setup - Mandrake 7.2, samba 2.09. Win98, ME and XP clients. The 98 and ME machines have no problems. The XP machine has some intermittent slowness

Hello! Whenenver I try to save a downloaded file with Opera [6.x] to a Samba share [2.2.x], Opera (and also the windows-explorer) freezes. Having set log-level to 1, I get the following message after a while. Sometimes, but not always, Opera continues working after 30seconds or so. I have the same behaviour in Samba 2.2.2, 2.2.3a and 2.2.4-pre. My Server is running SuSE 7.3 with the 2.4.16

Hi all, I use samba 2.2.2 on AIX 4.3.2 (1500 NT4 sp6a / w2k sp2 workstation). since i had updated from 2.0.7 to 2.2.2 the CPU load will very fast go to 100% an d teh memory use of a smbd process will grow up to 100 MB. In teh log-files are many errors like that: PANIC: open_mode_check: Existant process 22700 left active oplock smbd/open.c:open_mode_check(555) open_mode_check: exlusive oplock

> I have samba v 2.2 on one of my production server, the client connections > seem to drop sometimes, these clients run overnight jobs and when this > happens there job crashes and they have to manually start it. > > Below is the snippet of the log for one of such clients with problems. > > ###########cut-paste of log (only part of it)######### > > oplock_break:

Hi! I've been using samba for some time now with about 20 users and with remote installation of Windows XP from dos (TFTPboot image with dos network drivers - ms client 1.6c). On all releases (up to, and including 2.2.5) a recursive xcopy (from dos) copied all files normally. When I upgraded to samba 2.2.6, the recursive xcopy (win98 version of xcopy.exe, copying from a mapped drive)

Hi folks I hope someone might be able to shed some light on a problem that I am experiencing with a Samba server. I installed this server about 2 and a half years ago on a client's site. The server has been running fine. We are now experiencing two problems which according to the client occured overnight. The first problem started about a week and a half ago when they found that when trying

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

To force guest access to a share, you need both guest ok = yes guest only = yes Otherwise it will try and authenticate you first before dropping you to guest. If this doesn't work, possibly you don't have a valid guest account set. If no account is set as the guest account (on the linux machine) it will use the user "nobody". > -Larry Engleman > The Burgiss Group >

I am using samba 2.2.5 and cups 1.1.4 as a print server. Everything is working well, except occasionally the spooler service on my user's machines will randomly die. This happens across platforms (2k, NT, XP) and never happened with the same drivers/setup on the WinNT print server that I have just replaced. I've attached a link to my setup file. Let me know if you have any ideas. My

Hi ! I hate to do this but I'm close to get crazy about printing with samba. I have a samba server ver 2.2.5 running as a domain controler. The domain logon works fine, I've created the computer account by hand for testing and it is great. The problem is with printing. I've created the [print$] share all the directories in this share like W32ALPHA, W32MIPS, W32PPS, W32X86,

Dear Samba users, I've had a problem recently with Samba (2.2.3a, and now 2.2.5) on my OpenBSD 3.1-stable Installation. Bsd: OpenBSD 3.1-stable (CYNOSURE) #1: Fri Oct 4 01:06:45 EST 2002 avant@XXXX:/usr/src/sys/arch/i386/compile/CYNOSURE I get problems such as these: <poor formatting> [2002/10/13 23:00:04, 0]

We are running samba 2.2.3a ( for about 3000 users ) on HP/UX 11.11 fileservers. Our customers are complaining about slow response on the opening/closing of files in office/excel etc. In the samba log file we see the following messages : [2002/10/29 09:03:27, 0] ../source/smbd/oplock.c:(761) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file My

Hi, Thought I posted this already two weeks ago. Haven't seen any reactions yet, so I post it again We got the following problem here: Every now and then, users are unable to save Word or Excel documents on our Samba server. We already tried a couple of things: disabling oplocks, increasing oplock break wait time, putting the documents on a new share, ... but to no success so far. The