similar to: FW: RE: Explorer & MS Office hang

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

Thanks to Nate Partenheimer <npartenh@butler.edu> I will try this. On Thu, 20 Aug 1998, Partenheimer Nate wrote: > > Problem: > > -------- > > Maintaining two password databases for 6000 accounts > > > > Dave, > > This may or may not be something you want to consider... > We have been trying to give users one username and password which will >

We're running Samba 1.9.18p8 (non-PDC) on solaris 2.5.1. Everything works well except that file permissions are inconsistently assigned. Specifically, we are sharing users public_html directories which are mapped automatically by a policy when they logon a WinNT 4sp3 workstation so that a users can, theoretically, copy web pages from a diskette or other server to their web directories using

I have a prerelease version of Samba 2.0.4 running successfully on MacOSX Server with encrypted passwords and domain security. (Thanks to help from Bill Chin and others on the list, and Jeremy Allison and rest of the samba team) I have just started work on testing Samba as a NT domain member, and want to know if I have the right ideas from my reading of the docs: With security = domain, the Samba

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

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

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

Server is PII-350MHz/256 MB RAM, hardware mirrored high speed SCSI disks. Installed is SuSE 8.2 with Samba 2.2.8a RPM, XFS filesystems and LPRng as printservices. Server acts as PDC and WINS server. Clients are W2K SP2 (a few with SP3). There are +/- 100 clients. We see a server that is 100% busy and we see during a long time a very high CPU load (60- 95%) related to one W2K client. When

I've seen a couple mentions of trouble w/ large files in the list archives, but nothing that seems to resolve this problem... When trying to move or copy largish files (~ >1MB) with WinN using Samba 1.9.18p10 on a Sparc Solaris 2.5 system, things hang for a while and then a dialog box pops up saying "Cannot copy {filename}: The session was cancelled. I've tried setting

Couple questions to those who have the winbindd service up and running... I *think* winbindd is working now... I can browse the samba server through windows explorer and open directories. There is a little delay when I first connect... I assume this is winbind passing the authentication request to my NT servers and awaiting a response. The problem now is that I can't seem to write to the

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

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

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

Hi, i have a problem with access xp (2002) database files after moving the files to the linux files server. really often (6 times today) the database file is corrupt. i am running samba 2.2.5 on linux mandrake 8.2 with kernel 2.4.18. i have read that this has something to do with the file locking, but don't know what to do right now. i've set the parameter "veto oplock files =

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

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

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)