similar to: Permission denied after successful mount of Windows share

Why this log? Debian Lenny 5.0.4 Samba with PDC tailf -f /var/log/samna/log.nmbd tdb(unnamed): tdb_open_ex: /var/run/samba/unexpected.tdb (65025,49187) is already open in this process [2010/05/12 09:57:36, 1] lib/util_tdb.c:tdb_log(682) tdb(unnamed): tdb_open_ex: /var/run/samba/unexpected.tdb (65025,49187) is already open in this process [2010/05/12 09:57:36, 1] lib/util_tdb.c:tdb_log(682)

When I start winbindd (Samba v2.2.3a on Linux), I get the entries in log.winbindd shown below. What's the story on all those complaints about file "unexpected.tdb"? There is no general problem with Samba writing to that subdirectory: # ll /var/lock/samba/ total 288 -rw-r--r-- 1 root root 696 Feb 12 22:01 brlock.tdb -rw-r--r-- 1 root root 231 Feb 13

Please, What's this? Please, please, how to resolve ? [root@neosaldina-lj003 samba]# more nmbd.log tdb(unnamed): tdb_open_ex: /var/cache/samba/unexpected.tdb (835,457947) is alr eady open in this process [2005/08/04 00:12:51, 2] tdb/tdbutil.c:tdb_log(725) tdb(unnamed): tdb_open_ex: /var/cache/samba/unexpected.tdb (835,457947) is alr eady open in this process [2005/08/04

Hi all, I am running RedHat 7.3 and Samba 2.2.3a. I am using DHCP for my Linux box (hostname: NGPLinux, IP 132.189.26.62). I can see the list of shares I defined by using "smbclient -L NGPLinux -N". I can resolve the name using "nmblookup -U 127.0.0.1 NGPLinux". However, when I tried to use "nmblookup -B 132.189.26.255 NGPLinux" on the local machine, I got the

Experts, We've just migrated from samba 2.2.8a to samba 3.0.20b in a very large corporate environment. Everything was really fine in our lab, but we began experiment serious load problems on the productive servers the morning after the procedure took place. I'll try (briefly) to describe the characteristics of the scenario: Resources: Old Environment: Hardware:

The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 2974 (/usr/sbin/smbd). This means there was a problem with the program, such as a segfault. Below is a backtrace for this process generated with gdb, which shows the state of the program at the time the error occurred. The Samba log files may contain additional information about the problem. If the

Hi, we have installed the newest release of samba from HP for HPUX. It's based on samba 2.2.3a (B8725-1.0.8 HP number) We used the same config file and started the samba stuff and run into the following problems. 1) The machine was only reachable under one netbios alias. 2) Only some pc could connect (~15 out of 150), but those could also only see the toplevel of a share 3) The following

Gurus, I have downloaded and compiled 3.0.2a. I can map from 2000 to my share fine. If I try a smbstatus I get errors, see below. Can someone please point me in the right direction? smbstatus -s /usr/local/etc/meltwk-tst02.conf -d 10 edited to keep it short but this error about not having this charset repeats about 10 times. Locale charset 'ISO8859-15' unsupported, using ASCII

On a recommendation from this list I checked the junklog file, the output from which I attached below. It looks as if it does not even see the linux machine as it indicates not seeing "explorer" which is the local netbios name. The Win XP machine does not even show in the log. Here is the last entry for nmbd.log: ***** [2003/11/21 06:24:58, 0] nmbd/nmbd.c:terminate(54) Got SIGTERM:

Hello, I've encountered a problem printing to a windows print share and am uncertain how to go about resolving my problem. From what I've been able to tell, the problem lies in samba. I've got a fedora 13 box with samba installed and running on it. My goal is to print to a windows print share. I am able to use smbclient to query the print server and get a list of shares and

On Fri, 20 Oct 2017 14:57:42 +0200 Daniel Carrasco via samba <samba at lists.samba.org> wrote: > Hello, > > Sorry for take so long to answer, but I was not able to do the tests > because the computer is in use and out of my office. > > Finally I've progressed in this topic with realmd, sssd and autofs, > but now I'm locked on mounting shares from my member

A little summary of building Samba 4.12.0rc3 on OmniOS: The following 4 (5) small patches are needed in order to compile and run Samba 4.12.0rc3 on the latest OmniOS r151032p (OpenSolaris/Illumos variant): 1. ARRAY_SIZE is already defined in <sys/sysmacros.h> on OmniOS, put an #ifndef around it in lib/replace/replace.h (can be ignored but causes a gazillion compiler warnings :-):

Hi everybody, I'm an italian system administration (newbie about Samba). I have installed on Mandrake 9.1 the rpm samba3-*-3.0.2a downloaded from a Samba.org's mirror. I have configured a PDC based on ldapsam (OpenLDAP 2.1.29) that works fine, i use smbldap tools to manage sincronization account. Now the problem, when I try from my W2000 Workstation to change my domain password I reach

I have successfully implemented Samba in the past but I am now perplexed by a new installation which fails smbstatus with the message: "tdb((null)): tdb_open_ex: could not open file /var/cache/samba/brlock.tdb: No such file or directory Failed to open byte range locking database "tdb((null)): tdb_open_ex: could not open file /var/cache/samba/locking.tdb: No such file or directory ERROR:

Hi all, i am trying to run Samba 2.2.3a under a RedHat 7.2 i386 machine. After i compiled and installed the packages, i made a smb.conf up. Just some standard stuff nothing special. Now, when i start smbd and then check it with smbstatus it gives me this error : Samba version 2.2.3a Service uid gid pid machine ---------------------------------------------- tdb((null)):

Hello, Sorry for take so long to answer, but I was not able to do the tests because the computer is in use and out of my office. Finally I've progressed in this topic with realmd, sssd and autofs, but now I'm locked on mounting shares from my member server. I'm able to use autofs and smbclient to mount and connect to sysvol share on my DC server, but when I try to connect to my

Hi There, I'm using Mandrakelinux 10.0 Community, kernel version 2.6 I want to send a message to Windows clients from my Samba 3.0.2a box. Clients are w2k and winxp. If i say in CL $> smbclient -M recipient_machine then recieve error message "session request failed". Here the part of debug log: ------------------------------------ [gri@griff gri]$ smbclient -M serv -d5 ... ...

I have been unable to get my Samba shares on RedHat 7.3, Samba 2.2.3a to be visible from my Windows 2000 SP1 server. From the DIAGNOSIS.txt tests (results below) I think that nmbd is not working properly, but it stops and starts fine, and a ps -A shows 1 X smbd and 2X(?)nmbd processes running, I have tried the suggestions there without luck and am not sure where to go next. I'd appreciate

Hi all I try to get Samba running on the recent Debian stable release. All upgrades have been done and Samba was included in the OS Installation. I use the Samba version 2.2.3a-12.3 for Debian. smbd and nmbd are starting automaticly when the System is running. The smb.conf is still the one from the installation, nothing edited yet. Here are the errormessages that i get if i try testparm and

Everytime I install Samba on Debian 2.4.27, And I check smbstatus I get this: tdb((null)): tdb_open_ex: could not open file /var/run/samba/brlock.tdb: No such file or directory Failed to open byte range locking database tdb((null)): tdb_open_ex: could not open file /var/run/samba/locking.tdb: No such file or directory ERROR: Failed to initialise locking database Can't initialise locking