similar to: Oplock question

Hi! After more work on the oplock_break problem, I've found the following in my tcpdump-smb logging. It seems that when ost5 (pid=26339 in the logs that follow) requests access to the oplocked file comm.inf from ost6 (pid=5872) the oplock_break failes (this is NOT isolated to any one or two systems on our network, just using these two as an example, and the server reports no dropped packets

While trying to switch a domain from an WinNT 4.0 SP ? to an AIX 4.3 with samba 2.2.8 with OS2/warp 4 clients we receive some unexpected errors. - we can log on to the new domain , run logon scripts, map network drives , store and retrive files , print to a Remote server using the printers shared by samba. - we can't run VisualAge Generator (2.X) retriving files from the samba server. (we

hi there ;-) can you help ? ouer network has gone unreasonly slow newerdays, i?m nearly shure its no virus or shit.... i?d used tcpdump to see whats going on and found these errormessages ouer network is quite small, the linuxserver(samba), some windoofclients and the plotter_pc ( this one runs as a MSdosclient and searches a pathstructure for new files) what is this SNAP length ??? and

We recently tried the upgrade to 2.0 Beta series (just finished testing Beta 4) on our network. Everything works fine with 1.9.18pl10, but once we start 2.0 in its place we start getting the following in the log files: [1998/12/17 05:00:12, 1] smbd/files.c:file_init(219) file_init: Information only: requested 10000 open files, 246 are available. [1998/12/17 05:07:52, 1]

Samba is causing a couple huge problems for the NT admins here since we switched a bunch of machines to security=server and started running nmbd. We're running Samba 2.0.2 and 2.0.3 on a mix of Solaris, HP-UX, and OSF1 machines. One, selecting a Samba server in Server Manager, then selecting Computer/ Services causes Server Manager to crash ("An application error has occurred, blah blah,

Hi everyone. I just got a copy of Win2k in and have been messing with it. Have a question, and have searched the archives for the answer, but didn't find it. Can Win2k domain logon to a pre-3.0.0 samba server? Or di I need to get TNG running? I can get NT4.0 boxes to authenticate and login fine (Samba pre-3.0.0), but Win2k keeps complaining: "The following error occurred validating

I've been getting a lot of these recently in my samba-log ever since I downloaded the latest cvs SAMBA_2_0 branch code. Mar 6 18:13:06 gate smbd[11126]: cos5 (192.168.7.132) connect to service rsession as user rsession (uid=707, gid=100) (pid 11126) Mar 6 18:13:15 gate smbd[11126]: [2000/03/06 18:13:15, 0] lib/fault.c:fault_report(40) Mar 6 18:13:15 gate smbd[11126]:

Dear LLVM developers, My name is Ben Niu and I am a Ph.D. student at Lehigh University. I compiled the MUSL C library using Clang 3.3, and dumped the generated LLVM IR files. I found that the MUSL-defined FILE struct (aliasing __FILE_s) struct __FILE_s { unsigned flags; unsigned char *rpos, *rend; int (*close)(FILE *); unsigned char *wend, *wpos; unsigned char *mustbezero_1;

fyi the way that this will be used is to have: encrypted passwords = no update encrypted = yes for a few days, have everyone log in with their clear-text password, and a private/smbpasswd file will automatically be generated. then switch to encrypted passwords = yes update encrypted = no and voila. if you were feeling _really_ adventurous you could have: include = smb.conf.%M and have one

On Tue, Sep 10, 2013 at 7:13 PM, Ben Niu <niuben003 at gmail.com> wrote: > Dear LLVM developers, > > My name is Ben Niu and I am a Ph.D. student at Lehigh University. I > compiled the MUSL C library using Clang 3.3, and dumped the generated LLVM > IR files. I found that the MUSL-defined FILE struct (aliasing __FILE_s) > > struct __FILE_s { > unsigned flags; >

I have installed a small Limux box in my local primary school, in order to sahre CD iso images. The system works fine, untill several w/s's concurrently access the same program , whereupon, we get spurious crashes. I have tried disableing op-locks, which seemed to help, but only slightly. Any suggestions gratefully received. Shane oplock_break: no break received from client within 30

Hi all, I have a problem opening file on a samba share with Word 6.0. We use samba 2.0.5a running on a HP9000/800 (HP-UX 10.20). Often when try to open file, Word stop responding for some minutes (generally from 2 to 5) and then word succed to open it. In the sambadir/var the corresponding log file is like this : [1999/09/20 17:10:52, 1] smbd/service.c:make_connection(521) pc000320

I would really appreciate some help figuring out why one of my students has "disappeared" from the user list, and what to do about it. I'm using Samba3 on Fedora; the client machines are running WinXP. The system has been up and running since the beginning of September. Today one of my 4th-graders was unable to log on; she didn't read the error message carefully, so she

-----Oprindelig meddelelse----- Fra: Simo Sorce [mailto:idra@samba.org] Sendt: 8. januar 2003 15:40 Til: Preben S?rensen Cc: Andrew Tridgell; Jeremy Allison; samba-bugs@samba.org Emne: Re: oplock_break (PR#26342) Please send help request to the users mailinglist samba@samba.org Simo. On Wed, 2003-01-08 at 15:38, ps@datamann.dk wrote: > Full_Name: Preben S?rensen > Samba_Version: 2.2.5

Hi there everyone! I'm using Samba 2.0.5a-19990721 on a RedHat 6.0 machine with Linux kernel 2.2.12. My system generally works fine, however recently I've had some complaints about some files being corrupted. The latest and best-handled to enable a debugging happened at around the same time. Both clients were using Windows95 OSR2 machines with Excel 97 SP-2. Two users reported the problem

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]

Hi! I keep getting errors like these: oplock_break failed for file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_AZK.doc (dev = 301, inode = 2469218, file_id = 7). [2003/07/31 15:43:22, 0] smbd/oplock.c:oplock_break(843) oplock_break: client failure in break - shutting down this smbd. [2003/07/31 15:47:12, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb error (Success)

2.0.4b, RH60 (2.2.6+raid1, non root-raid), accessed from win98/ie5. Intermittently ie5 takes very long to load an html page from samba; at the same time it loads another html page ok from another linux/samba1.9.x At 10:47:34 I click on the html page and it is loaded at 10:48:18. [1999/06/23 10:47:34, 1] smbd/service.c:make_connection(488) go (10.0.0.115) connect to service go as user go

We are running Samba 2.0.5a on an AIX 4.2.1 box, and since we upgraded from 1.9.18, a Windows 95 client reports intermittent problems (timeouts) when saving small files. The log.smb file has entries from those events: [1999/09/08 14:59:07, 0] smbd/oplock.c:oplock_break(905) oplock_break resend [1999/09/08 14:59:17, 0] smbd/oplock.c:oplock_break(905) oplock_break resend [1999/09/08 14:59:27,

Hi! Even with 2.0.4, I'm still seeing a lot of oplock break failures (clients failing, see log further down). The client hangs for approx 30 secs (sometimes more) and then gets back online. At least one user can't use the file shares at all; it hangs whatever he does, and on any computer he uses (NT or 98, laptop, desktop...) Other users have less problems, but maybe they are less