similar to: AW: Errors in samba 2.2.4

> Hi, > the problem Netikular has, i have to on some Windows NT Workstations. Jeremy > Allison says, that this is just a network problem, but we can`t change the > network structure. Can we change something on the clients to resolve this > problem, like Time Out parameter or something else. > > Best regards > Ren? > > On Mon, May 06, 2002 at 01:25:26PM -0600,

I just downloaded and installed samba 2.2.4 on freebsd 4.5. I am running this freebsd server as a PDC and file storage server for 4 windows 2000 computers and 1 windows 98 (the win98 computer is not part of the Domain) I was wondering if anyone has any suggestions as to what would cause errors of the following types oplock errors [2002/05/06 12:06:08, 0] smbd/oplock.c:oplock_break(758)

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

Hello there. I'm having a few problems using samba 2.2.3a and sharing a paradox database. On the whole everything works fine but (there's always a but), every now and again. a machine's shares will close causing the database to crash (sometimes only that machine) - the other networked machine recover after a few error messages. I guess the easy answer would be to disable oplocks

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

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

For some strange reason, a samba setup which was previously working has suddenly stopped working, and I can't figure out why. The symptoms is that attempts to write some files onto a samba filesystem take a long time, and then error out with the error message (in Windows dialog box): "Cannot create or replace <filename>: The specified network resource or device is no longer

Hello, I'm having problems with samba share and trying to make multiple connections from one PC. Here are the errors I'm seeing in the log file: [2006/12/19 09:02:48, 1] smbd/service.c:make_connection_snum(648) amcfp001 (10.210.4.65) connect to service bvvol02_U1 initially as user bvvol02 (uid=502, gid=502) (pid 17671) [2006/12/19 09:02:48, 1]

Can someone please explain these smb.log entries??? [2003/08/26 18:58:31, 0] smbd/service.c:make_connection(381) fmouse logged in as admin user (root privileges) [2003/08/26 18:58:35, 0] lib/util_sock.c:read_socket_with_timeout(298) read_socket_with_timeout: timeout read. read error = Connection reset by peer. [2003/08/26 18:58:35, 0] smbd/oplock.c:oplock_break(758) oplock_break:

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

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

Samba 3.0.9-2.3 on Suse 9.2 I'm still getting errors copying to my samba box: Often the first attempt to copy to it fails seemingly before it's copied anything. When this happens, there is a zero-length file created with the right name. If I retry the copy immediately and reply Yes to overwrite the zero-length file, it usually proceeds without problems. Many times the copy just goes

I'm using samba 2.1 pre-alpha. When I right click an .exe file on the most shares, explorer freezes, and must be killed to recover. The problem doesn't show up on the home shares, but appears on any other shares I create. I've experienced this problem on many different workstations. Looking at the logs, it seems to be a problem with oplocks; the part of the log that seems to apply is

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]

Hi! Been having the same problem with oplocks for a while and have been trying to figure out what's going wrong. The FAQ says that we may have a networking (hardware?) problem, but according to the Linux box's ifconfig results, we have had no errors and no dropped packets on the internal network. I am able to reproduce the error pretty much at will on our network, and it is not isolated

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

TEST: ===== SAMBA STRESS OVER GIGABIT NETWORK: This is a simple Read/Write/Compare/Delete kind of test over the network via Samba. Multiple clients with multiple threads try to read/write/compare/delete(in a loop) a finite sized file (64K block size) over samba for a prolonged period of time in an effort to stress test the server. SERVER SIDE CONFIG: =================== ARCH: x86 OS: RHL AS

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

First... Hi. Im new in the list and I want to say Hello Second. Apologies because my english writing is too bad. I haven't problem to read. But the verbs and syntaxis when I write is too bad. I will try to read the list without write. I write now because I have a big problem. In this right moment Im downloading the entire archive lists and I will try to ask less. I have a samba server and the