similar to: Samba 2.0.6 (Suse 6.3) and weird log.smb.old Problem

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, we' ve installed a Samba server in an austrian school. To have a good access control to the network, everyone have to authenticate against our samba server. Now the following problem occurs: When somebody enters another domain name in the login-mask's domain-field, the person can easily use this PC with all users/password combinations. Does somebody know, how to turn off the

Hi, in the last weeks I've unsuccessfully tried to get Samba (2.0.5a) - Unix (Suse 6.2) password sync working. Maybe somebody can give me a hint, what's wrong. Enclosed you'll find additional information. Thank you for helping, Johannes -------- smb.conf: passwd chat = *password* %n\n *password* %n\n *Password* -------- password chat (manually): homer:~ # /bin/passwd web New

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

This is just a information in case somebody runs into the same issue: I was unable to upload drivers to a samba-server (3.0.28a and 3.0.29) via the windows add printer wizard. The driver files started uploading, then processing stopped saying the driver is not compatible to windows xp. In the logs the following message popped up. However some files could be copied: [2008/05/27 10:30:09, 0]

a plea to anyone who is using ms word from ms office 97 to access word documents on a samba 2.0.6 server from nt workstation 4 clients... can you send me the relevant smb.conf section for any samba shares that you use to read and write shared ms word documents? i'd like to know if you're doing anything funky with locking or something like that. i'm trying to allow a group to share

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

Running samba 2.06 on Solaris 2.6 and CIFS/9000 on HPUX11. Accessing from NT 4.0 Terminal server. We are seeing the following symptoms. Can anyone offer any diagnostic advice... Users will connect to samba servers and be working along ok. Without warning, the connection starts to act flaky. e.g. can't save documents, file system browsing becomes very erratic. A quick "ps | grep

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

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

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

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

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

This was in regards to a problem with ms applications hanging on trying to open a file. Turns out it was an nfs locking issue. Hope this helps, Don -----Original Message----- From: Partenheimer Nate [mailto:npartenh@butler.edu] Sent: Monday, March 26, 2001 1:23 PM To: "MCCALLDON "@envelope.hp.com; HP-USA@envelope.hp.com; ex1 " Subject: RE: RE: Explorer & MS Office hang