similar to: Invalid key given to dptr_close / NT error 3013

A productional system (linux) running samba 2.2.5 runs 'cracy' from yesterday. There are lot of 'odd' behaviours. People cant logon or cant logoff. Access to files fails. Examining the logs the most eyecatching events are: (not that the keynumber started at 959 and went slowly down. I did not wait until it goes to zero and let the user reboot its machine before) Any idea ? thnx,

Fabian, Fast explains. On the NT server work BrightStore with version r9, more highly does not go because of NT. On the REHL4 side works (worked) BrightStore Linux Client r11.5. Smaller version does not work goes because of RHEL4. BrightStore servers r9 and Linux Client r11.5 are not compatible unfortunately. I must now decide everything with the version Share to work to get. Or the operating

can anyone tell me what these sorts of errors in log.smbd mean? my searches thus far haven't uncovered anything at all recent [2011/04/25 23:19:43, 0] smbd/dir.c:292(dptr_close) Invalid key 0 given to dptr_close we have samba 3.4.8 running under solaris10; the number of clients ranges between 30-100 at any given time. all works flawlessly for months at a time, yet every few months or

I am running Samba 2.2.6 on FreeBSD 4.5 built from it's ports tree. When accessing a Samba share using a Compaq iPAQ running Pocket PC 2002, I get the following error in my system logs: Invalid key xxx given to dptr_close I have googled regarding following error to no avail. I can access the shares but keep getting the above message in my logs. Can anyone enlighten me on what the error means

Hi List, need your help, property the here following. OS / Samba = samba-3.0.10-1.4E (RHEL4) Error message in Samba logfile = Invalid key XXX given to dptr_close This message comes then if by NT server with BrighStore a Backup is started. The Backup is made by a Share. all the same with or without kernel oplocks = no level2 oplocks = no oplocks = no without success Info: Error Log from

Hello, I am currently working on a solution to replace Apple OpenDirectory on some aging Xserve hardware. I currently have CentOS Samba4 AD DC?s replicating for redundancy using sernet-samba repositories. The third one has File/Print roles defind and it works perfectly EXCEPT on OSX 10.6. IT works great on any Windows workstation and OSX 10.7,10.8, 10.9 GNOME/Nautilus and even CIFS CLI mounting

Hi there, I have a quite ugly problem with a Samba server. The server is running Linux 2.4.13 and Samba 2.2.2. The NFS-client is running Linux 2.4.5. The windows homedirs are on \\server\username, the UNIX homedirs are NFS mounted by the server. So, whenever I access \\server\username this actually NFS-mounts /nfs/client/home/username. I now have one client machine that causes the following

Greetings We just updated two RH9 servers to 3.0.14a-1 and are still seeing a lot of errors in the logs. They're not stopping us working but I would _really_ like to understand what is causing them. On the first server, in the logwatch, we get a whole swag of: samba: Unknown Entries: session opened for user janicer by (uid=0): 6 Time(s) session opened for user sonjap by

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

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, I run a Samba Server on openSuSE 11.4 with LDAP Authentication Backend. appears to work fine. However, only some shares work on my Mac client boxes: for instance, i can browse my home directory on the Linux box (/home/ray), whereas other shares are simply empty ("r01" below) on the mac (but they are shown as connected). [homes] comment = Home Directories valid users =

Does anyone know what is going on with the following:- A windows 98 machine maps several directories from a samba (2.0.0) server on a Solaris 2.6 machine. Twice now the win98 machine has locked up on opening the "my computer" icon, simultaneously several smbd processes have appeared on the solaris machine (initiated by that win 98 machine). log.smbd reports a single error:-

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

I found these articles that talk about the oplock_break problem (specifically they are related to problems with word97): http://support.microsoft.com/support/ntserver/serviceware/nts40/e9msge2bc.asp http://support.microsoft.com/support/kb/articles/q163/5/25.asp Basically they say: either apply sp3 on the winnt client or disable oplock on nt server But they don't say anything about win9x,

-----Original Message----- From: JUSTIN GERRY [mailto:JGERRY@butchers.com] Sent: Wednesday, May 15, 2002 10:33 AM To: vansickj-eodc@Kaman.com Subject: Re: RE: RE: [Samba] Win2k Printing Problems No my ports are: servername (ip address in my case as I am going across a router) print server (actual printcap name) When I add a printer to a Win2k box, in the registry under

================================================================== "Design can be art. Design can be aesthetics. Design is so simple, that's why it is so complicated." Paul Rand ================================================================== Release Announcements ===================== This is the latest stable release of Samba 3.5. Major

================================================================== "Design can be art. Design can be aesthetics. Design is so simple, that's why it is so complicated." Paul Rand ================================================================== Release Announcements ===================== This is the latest stable release of Samba 3.5. Major

CentOS Errata and Bugfix Advisory 2018:3013 Upstream details at : https://access.redhat.com/errata/RHBA-2018:3013 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0e3a88856581aea77fe93130ea5a87c8db4645ef9e8a542dba9ea503293379e0 tzdata-2018f-1.el6.noarch.rpm f798c34e5a2e851ae952333ed2230c575199aa04159836012f65b89dfe3fb907

CentOS Errata and Bugfix Advisory 2018:3013 Upstream details at : https://access.redhat.com/errata/RHBA-2018:3013 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 59e12ef8382b5e1e893053e6b6b8ae9408df040bfe114a5a01e83dbfd53f6287 tzdata-2018f-2.el7.noarch.rpm 789b5f573116c54397536cc178fb76eec58bc6b06cc811c0c3372f0505bfd251

Hi, My Samba server (Solaris 7, 64-bit mode) with AFS option has been running for a year. I just changed the "Max Log Size" global parameter few times today. Each time I committed the change, I got the following same set of error messages in my Samba log (the log.smb file): [2002/01/03 17:40:56, 0] lib/util_sock.c:set_socket_options(151) Failed to set socket option