similar to: oplocks ?

I have a File Server with 3 HDDs. Everyone has a directory with the name "samba". One of the HDD has a secondary Directory with the name "samba_nfo". In this Directory,i have created links to the other shares. My Question is: Can a Client follow this links with the smb.conf Option "wide links = no". It is a security Problem when i turn this Option to "yes"

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

Hi all, I've posted a similar message a few weeks ago. I had the 'oplock' problem. I run a linux server with samba (specification below). I get a reply who told me to disable kernel oplocks and oplocks. I did exactly what he told me to do. I hoped it worked... but it did not... From there one i started reading in the archives and followed the 'lock' discussions in this list.

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

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

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

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 =

Dear Samba team. I have hybrid network with MSDOS / Win9x(ME) / Win2k/XP(NT) computers at home. I'm using Samba as PDC. W9x/me clients works fine as so as with roving profiles, but I'm experiencing problems with w2k, NT4/XP just not test because i'm testing on my box at home and when it'll work fine then I'll go to clients from which smaller part has XPs installed on PC.

When 2.2.4 was released, I updated my cvs and did ./configure and make (no special options). Since I came in somewhat early today and nobody was around I did the make install. Everything ran fine until I tried to load a particular file and I'm receiving the following error and unable to open the file on a network share. If I place the file on a local drive it loads fine. Permissions and

I have been searching for info on this and haven't found an authoritative answer. From what I have read, oplocks are good because they increase connection speeds, but they are bad because they don't really work, but they actually do work, but they only work in some cases, etc etc. so, here's my problem and my question together: I get tons of these messages every day (over a thousand a

Hello list! I've seen the threads in this months archives on oplock issues, so I hope I am not hitting a sore spot by bringing it up again. The reason I am beating on this is that I've got a testable, repeatable issue with Win2K terminal server (SP2) running CorelDRAW 10 (patched to current) against a Debian Woody box running Samba 2.2.3a-6 for Debian. Since I can repeatedly test the

Hi everyone, Trying to copy a 3.5MB file from a Windows 2000 workstation to a FreeBSD 4.6.2 server running samba-2.2.6.p2. The 3.5MB file is an MS Access file called MoldFE.mdb. After a few seconds of copying the file, a message box pops up on the W2K workstation that states "Cannot copy MoldFE: The specified network name is no longer available". In /var/log/messages, I see this:

We have been using samba for years now and are generally very happy. But since a recent upgrade to 2.2.8 we have seen samba slowing down periodically to a crawl every 2 or 3 days. BTW the start of these problems coincided with the upgrade to samba 2.2.8 and a partial cabling upgrade to 100 MBit, which also coincided with the introduction of the first Win XP Pro machines to our LAN. ;-( We have

Hello, System: Solaris 8/9 Samba: 3.02 and 3.06 We have problems with accessing files (from Windows XP) on a samba server that are mounted over nfs (on the server). Some users have symlinks in their home directories to nfs resources. When they try to copy file located in nfs the client simply hangs. To make the thing even stranger: Sometimes it also works (after restarting the samba server

Hi, Has anyone any ideas what is causing my smbd processes to crash? The files being accessed via samba are on an NFS mounted directory. In the samba log file I am getting the following errors: [2004/12/03 16:31:33, 0] smbd/oplock.c:request_oplock_break(1026) request_oplock_break: no response received to oplock break request to pid 2181 9 on port 53336 for dev = 2c00002, inode = 297939333

Hi- I've used the same smb.conf for many such file servers: one big share the office can write to, share level, no passwords. But I've never had the following error, and can't find the same combo of errors on the web either. They are MS works 2000 databases. If a client opens one, then closes it, no other client can access the file (it will hang indefinitely) until the original

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

We are trying to troubleshoot slow performance. A lot of my NT client log files show messages like this about oplock break issues. [2003/10/09 12:50:39, 0] smbd/oplock.c:(1008) request_oplock_break: no response received to oplock break request to pid 2907 on port 61752 for dev = 40240002, inode = 29, file_id = 2 64 [2003/10/09 12:51:03, 0] smbd/oplock.c:(395) process_local_message:

Hi all, We have a HP-UX 11i server running as a samba server. Users use Windows 2000 boxes with Service Pack 4 to connect to the samba server. Several days ago, we upgraded samba server from 2.0.7 to 3.0.5, and we started to experience the following problem: The general connection and access to the samba server is ok. However, under the samba share there have been some directories mounted from