similar to: Re: Locking Module?

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)): tdb_open_ex: could not

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

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

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

Hi! I've been fighting with Samba for over a week now and I can't seem to work it out. It all started when I installed the standard samba (2.2.1a-4) which came with RH7.2. I ran "smbstatus" and got the following error: Failed to open byte range locking database ERROR: Failed to initialise locking database Can't initialise locking module - exiting. I've tried 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

i have taken a default intel redhat 7.2 machine which came with samba 2.2.1a and removed samba, samba-common, samba-client and samba-swat. i also removed /etc/samba and /var/lock/samba and all samba log files i then installed the samba RPM for samba 2.2.5 from: http://se.samba.org/samba/ftp/Binary_Packages/redhat/RPMS/7.2/samba-2.2.5- 1.i386.rpm i then installed this with rpm -ivh

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

On 20/10/16 14:10, Amitay Isaacs wrote: > On Thu, Oct 20, 2016 at 8:09 PM, Alex Crow via samba > <samba at lists.samba.org <mailto:samba at lists.samba.org>> wrote: > > Hi list > > We recently upgraded our fileservers from Centos supplied 4.2.10 > to Sernet 4.4.6, and then our DCs from 3.6.x to 4.4.6. > > It seems that since then we've

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

When using Samba 3.0.23b (slightly old, I know) on CentOS 4.4, smbstatus -B fails with a segmentation fault. smbstatus works, and tdbdump is able to dump brlock.tdb and locking.tdb without any errors (which is not what I expected). Here's the backtrace (non-ASCII characters replaced with 'X'): #0 0x0017fa2c in memcpy () from /lib/tls/libc.so.6 #1 0x0029b19f in tdb_write

i've been integrating a Samba server into a mixed windows 2000/2003 authentication environment for use as a NAS device. i finally have things working for the most part, but in the process of debugging authentication i noticed an error when performing the following command: hmason@mpinas1:~$ smbclient -L localhost the error shows up when loglevel = 5 in smb.conf: Netbios name list:-

I have just upgraded a RedHat 6.2 box from Samba 2.0.10 to Samba 2.2.5 in one of our elementary school buildings because we now have some w2k boxes that must log to the domain. I'm now getting an error on initializing the locking modules when I run smbstatus. I did the upgrade remotely so I don't know yet whether workstations work properly with the upgrade. [root@fvserver samba]#

Afternoon, I'm running OpenBSD 3.1, and since being informed that since 2.2.3a contains a bug I should upgrade to 2.3.4 - which I've done. I've installed this from source, and havn't seen any reason to believe the build process didn't work properly (Other than having duplicated binaries in /usr/local/samba/bin/ and in /usr/source_distributions/samba-2.2.4/source/bin/smbd

Hi, When trying to copy 5000+ files from a client PC to a Samba server I have the following problem. Halfway during the operation it hangs on always the same file. Windows XP (SP1) gives: Unable to copy file [filename]. Specified network name is no longer available. (I had to translate this from Dutch, so it is not the exact message). When checking with smbstatus I get this:

Hi, After trying too long I fixed the problem below by reverting to the old 3c905 NIC. Problem solved but not understood. I had a similar 3c2000 NIC in another Samba server and it also failed to copy a large amount (5000+) of files. So that's two completely servers (hardware and Samba / Slackware version) having the same problem with any number of different clients. I couldn't imagine

Hi, testparm: --------- testparm shows: ERROR: the 'passwd program' (/usr/bin/passwd %u) requires a '%u' parameter. You can see, passwd program _is_ /usr/bin/passwd %u smbstatus: ---------- smbstatus command always shows processes _and_ shares even if using the switches '-p' for showing processes only or '-S' for showing shares only or '-B' for

Hi, I have been trying to get Samba 2.2.2 to run on HP-UX 11.00 64 bit, but seem to be running into problems with the locking databases. (Note : this is running the smb.conf file from the examples directory in SAMBA 2.2.2). I have tried to two different servers and both of them generate the same result described below. The problem I have hit is after compiling samba and starting up the system