similar to: Installation problems on Fedora Core 2

Environment: OpenBSD v 3.6 Release, Samba ver.: Samba 3.0.5 LAN: 192.168.0.0/24, Samba servers: 2 installed replacing workgroup peer shares Windows version: XP Pro History: The 2 Sambas were installed last year and appear to have operated well until recently. Client admin now reports that, after some time connected to a shared directory, searching for files results in a Win error message to the

When rebuilding from the source rpms on ia64 on Fedora Core 1 with all updates I am getting the following error. --------------------------------- Processing files: samba-client-3.0.4-2 error: File not found: /var/tmp/samba-3.0.4-root/usr/lib64/samba/lowcase.dat error: File not found: /var/tmp/samba-3.0.4-root/usr/lib64/samba/upcase.dat error: File not found:

I'm having trouble sending messages to my Win2000 and XP clients. Everything worked with Samba 2.2.2, and now with Samba 3.0 (CVS) it fails. Below are two trails, the first works (sending to the Samba server) and the second fails. (Also, how do I get rid of the upcase.dat, lowcase.dat, and valid.dat errors?) Thanks!! -Paul penguin# echo "TEST" | smbclient -M penguin incorrect size

When I try to compile samba.org 3.0.10-14a rpms on Fedora Core 2 and 3 x86_64, I get the following errors. The missing files are in /var/tmp/samba-3.0.14a-root/usr/lib/samba/ and there are just 2 files in lib64. So what is the secret incantation here? Thanks, Chuck + cp -pr README COPYING Manifest /var/tmp/samba-3.0.14a-root/usr/share/doc/samba-3.0.14a + cp -pr WHATSNEW.txt Roadmap

Wed Jun 14 01:50:55 GMT 2006 * Previous message: [Samba] <http://lists.samba.org/archive/samba/2006-June/121816.html> LDAP Group mapping * Next message: [Samba] testparm <http://lists.samba.org/archive/samba/2006-June/121845.html> gives error in Solaris 10 * Messages sorted by: [ <http://lists.samba.org/archive/samba/2006-June/date.html#121817> date ] [

Hello, I am trying to set up Samba in a Solaris 10 system. Solaris 10 already has Samba installed, so I just want to make configuration changes in smb.conf and then start the service. We already have a smb.conf file from a RHEL 3 system where Samba works fine. So I tried to use the same smb.conf file for Solaris. But on running "testparm /etc/sfw/smb.conf", I get the following error.

Hi, We've been trying to set up a Samba 3 installation using a Postgresql backend with the passdb pgsql module. We compiled our own version of Samba 3.05 on Debian 3.0r1 after realizing the packages don't build the experimental backends by default. The Postgresql database is set up and working, but when attempting to add a new user using pdbedit, we keep getting this errors regarding

HP UX11i My SA is off island and I am in unfamiliar territory. We are getting an error when trying to start winbindd. =============================================================== [Thu Apr 28 12:04:49 2005 , 0] lib/util.c:smb_panic2(1398) PANIC: internal error [Thu Apr 28 13:07:20 2005 , 1] nsswitch/winbindd.c:main(843) winbindd version 3.0.5 based HP CIFS Server T.30.PV.02

Hi, I was trying to install Samba 3.0 Alpha 9 onto a server running HPUX 11.00 64 bit. I have the Openldap libraries installed and also Kerberos (the PAM Kerberos and KRB5 Dev Tools available from the HPUX application CDs). I have followed the instructions as outlined in the Samba 3.0 prealpha guide to Kerberos authentication (Steps 1-2, Step 5) and everything seems to be fine at steps 1-2 (the

Hi Jerry, Andrew, et. al. Background: RH 7.2 Two Samba installs: 3.0-15 under /usr/local/samba 2.2.3a under /usr error as follows: ---snip--- [root@phoenix root]# /usr/local/samba/bin/smbclient -L 127.0.0.1 incorrect size for /usr/local/samba/lib/upcase.dat - got 0 expected 131072 incorrect size for /usr/local/samba/lib/lowcase.dat - got 0 expected 131072 creating lame upcase table creating

Hai, There is something going on in your resolving, that im sure. I dont know where you missing a setting or did a wrong setting, but this should all work out of the box. The PTR lookup responce with ip of the DC, should be hostname.fqdn. and not hostname. I've also had a good look at the debug script output again. That all looks ok to me so i'm wondering, if apparmor is in play

On Wed, May 25, 2016 at 2:38 PM, pisymbol . <pisymbol at gmail.com> wrote: > Hello: > > Platform: CentOS 6.7 x86-64 > > $ rpm -qa | grep samba > samba-common-3.6.23-30.el6_7.x86_64 > samba4-libs-4.2.10-6.el6_7.x86_64 > ie-samba-utils-3.6.13-7.x86_64 > samba-winbind-3.6.23-30.el6_7.x86_64 > samba-client-3.6.23-30.el6_7.x86_64 >

On 29/07/2019 08:11, L.P.H. van Belle via samba wrote: > Hai, > > There is something going on in your resolving, that im sure. > > I dont know where you missing a setting or did a wrong setting, > but this should all work out of the box. > > The PTR lookup responce with ip of the DC, should be hostname.fqdn. and not hostname. > > I've also had a good look at the

Yes, I confirm. Le ven. 20 déc. 2019 à 19:12, Praveen Velliengiri < praveenvelliengiri at gmail.com> a écrit : > Hi, > Orc v2 is different from the internal structure then Orc v1 not just in > API level. > TLS support is not in ORC for a long time at least I'm aware of , Could > you please confirm that ORC v1 actually compiles and run the code with > Thread locals?

This spnego stuff makes me think about "client ldap sasl wrapping = sign" to be added in some cases. There are threads related to that posted recently. Disabling spnego is, if I'm not mistaken, disabling Kerberos. Disabling Kerberos should not be what you really want with AD : ) 2016-05-26 13:23 GMT+02:00 pisymbol . <pisymbol at gmail.com>: > On Wed, May 25, 2016 at 2:38

I'm using the Yocto Project to build an embedded distro, to which I'm adding Samba 3.6 from OpenEmbedded. Doing so increases my root file system from about 63MB to 175MB. I seem to be building a large Samba server with a small ancillary operating system tacked onto it. I listed the files in my file system image, and see that lots of the commands are quite large. I understand that Samba 4

With some extra effort of export samba_cv_CC_NEGATIVE_ENUM_VALUES=0 I could compile Samba3 for ARM. (./configure --host=arm-none-linux-gnueabi --build=i686; make) As I couldn't install samba on my host with make install (as I compiled on Intel machine) I just - copied smbclient, libwbclient.so, - created an empty /usr/local/samba/lib/smb.conf - and copied lowcase.dat and upcase.dat to that

And yet the same C++ code using thread-local variables works fine (or seems to) when compiled with Orc v1. Does the change to the Orc API really make thread-local storage more difficult? On Fri, Dec 20, 2019 at 3:52 PM Praveen Velliengiri < praveenvelliengiri at gmail.com> wrote: > Oh, I think Linux don't have support for TLS. > > On Fri, 20 Dec 2019 at 20:19, Geoff Levner

Hello, I'm afraid this message is going to be a little long (188 lines, not counting the headers). It is comprised, in fact, of two posts I sent to the comp.protocols.smb newsgroup, from which I've not received any replies. I'm hoping I can have better luck with the mailing list, (to which I've just subscribed, so it's probably most appropriate to send replies there...)

No, the problem is that Finalized is true. It is set to true at the start of the finalize() method. That's why I added a test causing that line to be executed if the symbol's address is zero... On Tue, 17 Sep 2019, 00:05 Lang Hames, <lhames at gmail.com> wrote: > Hi Geoff, > > Oof. I don't know what this is yet, but I bet it's going to be awful. > Quick apology