similar to: [samba4 dc ldap] LDAP_SERVER_FAST_BIND_OID is currently not supported?

Bug posted: https://bugzilla.samba.org/show_bug.cgi?id=9919 Sorry I can't making a patch, but I attached a Java client test file in it. Sorry again, I don't know to written it in C language. ------------------ Original ------------------ From: "Andrew Bartlett"<abartlet at samba.org>; Date: Thu, May 30, 2013 01:42 PM To: "Tide"<lovetide at qq.com>; Cc:

Hi sambalist, I'm using sernet samba for several years. I found that there's error in the log.samba file like this: [2019/07/10 14:55:25.892988, 0] ../../lib/util/fault.c:79(fault_report) =============================================================== [2019/07/10 14:55:25.893187, 0] ../../lib/util/fault.c:80(fault_report) INTERNAL ERROR: Signal 11 in pid 9906

Reindl/Harald, What is your first name? Sorry for asking, but always wondered about it. I just wanted to note here that... 1) I have seen this also if samba is upgraded and not restarted. Or 2) if a packages is not upgrade because an extra package is also needed at install. And that should be tested/checked/tried out first and if that all fails, then its needed to contact sernet support.

Sorry.. Centos.. yum update I dont know the Centos version of apt dist-upgrade. But check if ldb tdb tevent are upgrade. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > L.P.H. van Belle via samba > Verzonden: woensdag 10 juli 2019 10:12 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] error in

Hi All, I need so assistance please. Env. RHEL 7 # samba-tool -V 4.12.1-SerNet-RedHat-10.el7 bind-9.11.4-16.P2.el7_8.2.x86_64 I recently updated out Samba DC's from 4.11.7 -> 4.12.1. I then also ran # samba-tool domain schemaupgrade Updates went well without any issues, except for 1 DC it seems like. I have multiple core.* files that are created at / [root at DC3 /]# ll core.*

Am 10.07.19 um 14:39 schrieb L.P.H. van Belle via samba: > Reindl/Harald, > > What is your first name? Sorry for asking, but always wondered about it. > I just wanted to note here that... Harald > 1) I have seen this also if samba is upgraded and not restarted. won't happen on original CentOS packages, they have restart triggers in the spec files > 2) if a packages is

Hello you all, we have a 4 DC environment running on Centos7 with the Sernet-Packages. Version on all DCs is 4.9.8 (smb.conf below). We upgraded one of the DCs to 4.10.3. After a few minutes we see this in the logs: May 20 10:57:17 dc3 samba[15547]: [2019/05/20 10:57:17.200060, 0] ../../lib/util/fault.c:79(fault_report) May 20 10:57:17 dc3 samba[15547]:

We have a third party mail system which can write/read accounts to/from AD using ldaps protocol, it works fine with active directory of windows server 2003. When I test the mail system with samba4 DC, I can't disable user from the mail system, because the mail system write 0x800002 (8388610,UF_ACCOUNTDISABLED | UF_PASSWORDEXPIRED) to userAccountControl field of AD/samba4, and samldb returns

When I use ldbsearch to get the operatingSystemVersion information, I got '4.0.6', but I'm running samba-4.4.5 now. It seems that this information stayed at the version number when I provisioned the domain. Can this version number keeps up to date when I upgraded samba server? I can write a small script and scheduled it to change this information periodically, but if there's an

Hello - make fails to build the latest git of samba4 - erroring on drsblobs.so. Below is a full log from autogen.sh to the make. Would you have any suggestions on proceeding? Thank you, Ryan ryan at test1:~/samba-master/source4$ sudo ./autogen.sh ./autogen.sh: running script/mkversion.sh ./script/mkversion.sh: 'version.h' created for Samba("4.0.0alpha12-GIT-d83850a")

Here's someone that felt the need to put something better together. ---------- Forwarded message ---------- Date: Mon, 13 Jul 1998 04:22:15 -0400 From: Richard Thomas <rthomas@sy.net> To: BUGTRAQ@NETSPACE.ORG Subject: Slackware Shadow Insecurity Discovered by Ted Hickman: Recently I noticed something rather "insecure" about the slackware 3.4 /bin/login (and probably other

hi, all: I'v got a Gluster testing, and found some performance issuse pertain to Gluster I built a ten-node Gluster enviroment, (3 X HP 380G5, 4 IBM 3650, 2 X HP C7000. 1 X DELL PE2950, all the network switch & NICs are all gigabit). And set up three volumes: a ten-brick distribute volume (ten-brick means this volumes resides on ten nodes, others are same), a five-brick distribute

---------------------------- OS: CentOS 5.2 Samba: Samba 3.0.28-1.el5_2.1 Printer: HP LaserJet P2105n ---------------------------- I setup a linux print server for windows clients. First I downloaded the printer drivers for windows from HP website (both the Universal Printer Driver PCL6 and the PCL6 driver for P2105 series), and installed them on my windows client, then it created a local printer

I setup a central Fedora 11 printer server in a big office for 80+ windows clients due to the max 10 connections limitation of windows 2000/xp. 2 physical printers are connected to the server, and I configured 3 CUPS printers(1 printer with 2 different printer drivers) in Fedora 11. Is there a console tool to 1. Monitor the print queue(s) in real-time like windows system? A history windows hold