Displaying 20 results from an estimated 2000 matches similar to: "ldap_initialize: Bad parameter to an ldap routine"
2019 Mar 13
4
replication fails
Am 13.03.19 um 18:50 schrieb Rowland Penny via samba:
> Try running 'samba-tool ldapcmp ldap://dc1 ldap://dc2'
thanks!
I get differences, too many to post here, but I assume mostly related to
the drift between the 2 dcs now?
(lastLogonTimestamp seems obvious to me)
What might solve the initial problem *maybe*
* Comparing [DNSFOREST] context...
* Objects to be compared: 19
2012 Apr 14
2
Configuration of idmap_ldap "No backend defined"
Hi list,
I can't make idmap talk to my LDAP server. And I haven't found an updated
howto.
Some entries from log.windbindd-imap:
[2012/04/13 20:05:40.500475, 5] winbindd/idmap.c:153(smb_register_idmap)
Successfully added idmap backend 'ldap'
[2012/04/13 20:05:40.501112, 5] winbindd/idmap.c:153(smb_register_idmap)
Successfully added idmap backend 'tdb'
[2012/04/13
2020 Jul 18
3
Adding users with ldif file
On 18/07/2020 13:52, RhineDevil wrote:
> Fri, 17 Jul 2020 19:44:37 +0100 Rowland penny via samba <samba at lists.samba.org>:
>> On 17/07/2020 19:31, RhineDevil via samba wrote:
>>> And by that I mean, where are the dbs, what should I rm -rf?
>> On Debian just remove /var/lib/samba and /var/cache/samba
>>> By the way how do I obtain current machine netbios
2020 Jul 18
2
Adding users with ldif file
On 18/07/2020 14:30, RhineDevil wrote:
> Sat, 18 Jul 2020 14:19:25 +0100 Rowland penny via samba <samba at lists.samba.org>:
>> On 18/07/2020 13:52, RhineDevil wrote:
>>> Fri, 17 Jul 2020 19:44:37 +0100 Rowland penny via samba <samba at lists.samba.org>:
>>>> On 17/07/2020 19:31, RhineDevil via samba wrote:
>>>>> And by that I mean, where
2020 Jul 18
2
Adding users with ldif file
On 18/07/2020 14:47, RhineDevil wrote:
> Sat, 18 Jul 2020 14:41:31 +0100 Rowland penny via samba <samba at lists.samba.org>:
>> On 18/07/2020 14:30, RhineDevil wrote:
>>> Sat, 18 Jul 2020 14:19:25 +0100 Rowland penny via samba <samba at lists.samba.org>:
>>>> On 18/07/2020 13:52, RhineDevil wrote:
>>>>> Fri, 17 Jul 2020 19:44:37 +0100
2019 Mar 13
7
replication fails
Am 13.03.19 um 13:25 schrieb Stefan G. Weichinger via samba:
> My DC1 is named "PRE01SVDEB02"
> and DC2 = "PRE01SVDEB03"
checked for resolv.conf and DNS-pointers again. made sure that all 3
FQDNs (2 DCs, one DM) resolve from the servers.
showrepl is happy again on DC1, but still fails on/to DC2
hm
manual replicate: no progress or success visible (either from DC1 or
2020 Jul 18
2
Adding users with ldif file
On 18/07/2020 15:19, RhineDevil wrote:
> Sat, 18 Jul 2020 14:53:26 +0100 Rowland penny via samba <samba at lists.samba.org>:
>> On 18/07/2020 14:47, RhineDevil wrote:
>>> Sat, 18 Jul 2020 14:41:31 +0100 Rowland penny via samba <samba at lists.samba.org>:
>>>> On 18/07/2020 14:30, RhineDevil wrote:
>>>>> Sat, 18 Jul 2020 14:19:25 +0100
2020 Jul 18
1
Adding users with ldif file
On 18/07/2020 16:51, RhineDevil wrote:
> Sat, 18 Jul 2020 15:31:36 +0100 Rowland penny via samba <samba at lists.samba.org>:
>> On 18/07/2020 15:19, RhineDevil wrote:
>>> Sat, 18 Jul 2020 14:53:26 +0100 Rowland penny via samba <samba at lists.samba.org>:
>>>> On 18/07/2020 14:47, RhineDevil wrote:
>>>>> Sat, 18 Jul 2020 14:41:31 +0100
2020 Jul 22
3
Err: Naming violation
I added misc.schema to samba LDAP implementation, then I tried to insert this:
dn: CN=security,CN=aliases,CN=mail,CN=ypServ30,CN=RpcServices,CN=System,DC=mydomain,DC=mytld
cn: security
objectClass: nisMailAlias
objectClass: top
rfc822MailMember: root
I got this error:
https://0bin.net/paste/Xhhierl5ZAh6QVVJ#ZNXk9+hWY70PLof1eZ1TaqIoO-v3gRGOqNnIpfnX9GI
How could I solve?
-------------- next part
2020 Jul 22
1
Err: Naming violation
Wed, 22 Jul 2020 14:10:15 +0100 Rowland penny via samba <samba at lists.samba.org>:
> On 22/07/2020 13:53, RhineDevil via samba wrote:
> > I added misc.schema to samba LDAP implementation, then I tried to insert this:
> >
> > dn: CN=security,CN=aliases,CN=mail,CN=ypServ30,CN=RpcServices,CN=System,DC=mydomain,DC=mytld
> > cn: security
> > objectClass:
2008 Jul 03
0
configure: error: Active Directory support requires ldap_initialize
Tried configure of samba-3.2.0 on Sparc Solaris 9 with the following
line:
./configure --with-ldap --with-ads --with-pam --with-winbind
--with-krb5=/usr/local > $log 2>&1
There is a problem where the following error is produced:
configure: error: Active Directory support requires ldap_initialize
I can use the same line on samba-3.0.10 and it compiles and works.
$
2006 Feb 15
1
configure can't find ldap_initialize on HP-UX 11i
I'm basically using the instructions found in the HP-UX readme with the
exception that I am trying to use the version of openldap that is in
iexpress instead of the one from hpux.cs.utah.edu.
The recommendations listed in the doc are:
HP-UX 11.00 and 11.11:
OpenLdap 2.1.3 (http://hpux.cs.utah.edu)
OpenSSL 0.9.7d (http://hpux.cs.utah.edu)
HP-UX 11.23 only:
ixOpenLdap
2008 Oct 01
2
samba-3.2.4 Solaris 9: configure gets error: Active Directory support requires ldap_initialize
Unable to compile samba-3.2.4 on Solaris 9 for sparc.
#building openldap
CC=gcc
#echo $CC
#exit
CPPFLAGS="-I/usr/local/include -I/usr/local/ssl/include
-I/usr/local/BerkeleyDB.4.2/include -I/usr/local/include/sasl"
LDFLAGS="-L/usr/local/lib -L/usr/local/ssl/lib
-L/usr/local/BerkeleyDB.4.2/lib"
export CC CPPFLAGS LDFLAGS
#
CFLAGS='-D_AVL_H'
export CFLAGS
#
2010 Dec 13
1
Winbindd log error
Hello everyone
I have a Debian Lenny running Samba 3.4.7 + OpenLDAP as PDC. I'm
having trouble with Winbind. He logs so much messages that my disk is
almost full!
here is the log:
Dec 13 16:18:14 fileserver smbd[10017]: [2010/12/13 16:18:14, 0]
lib/util_sock.c:539(read_fd_with_timeout)
Dec 13 16:18:14 fileserver smbd[10017]: [2010/12/13 16:18:14, 0]
2018 Jun 15
1
Mounting samba share
Hi,
I was trying to mount a samba share from a host server using pam_mount module. This is my smb.conf for client machine and my pam-mount.conf.xml.
[global]
log level = all:10
security = ads
# auth methods = guest sam winbind:ntdomain
client ldap sasl wrapping = seal
netbios name = STAT1
realm = EXAMPLE.EDU
workgroup = WORKGROUP
2019 Mar 13
2
replication fails
Am 13.03.19 um 12:49 schrieb Rowland Penny via samba:
>> Should /etc/hosts contain pointers to own FQDN or not? To DCs?
>>
>
> /etc/hosts should contain a line that points 127.0.0.1 to localhost and
> a line that points the DC's ipaddress to its FQDN and shorthostname
>
> EXAMPLE:
>
> 127.0.0.1 localhost
> 192.168.0.6 dc4.samdom.example.com dc4
>
2019 Mar 13
0
replication fails
On Wed, 13 Mar 2019 19:30:30 +0100
"Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote:
> Am 13.03.19 um 18:50 schrieb Rowland Penny via samba:
>
> > Try running 'samba-tool ldapcmp ldap://dc1 ldap://dc2'
>
> thanks!
>
> I get differences, too many to post here, but I assume mostly related
> to the drift between the 2 dcs now?
2019 Mar 13
2
replication fails
Am 13.03.19 um 17:13 schrieb Stefan G. Weichinger via samba:
> Am 13.03.19 um 16:53 schrieb L.P.H. van Belle:
>> Ok thats small, a dc should be rebooted within 1-2 min and 1-2 min really max for AD sync.
one more observation:
manually running this works:
root at pre01svdeb03:~# samba-tool drs replicate dc PRE01SVDEB03
dc=blabla,dc=at --full-sync
but the one user I created (and
2006 Jul 20
1
3.0.23 for Debian Sarge: LDAP problems
Hi,
I always prefer the Samba packages for Debian-Stable from the
Samba-Team and I never had a problem so far (thank you, Simo!).
Yesterday I updated from 3.0.22 to 3.0.23 in my LDAP-based network. I
updated samba.schema, added "index sambaSID eq,sub" to my slapd.conf
and ran slapindex. When I started slapd and samba afterwards, I saw
error messages like these (from smbd.log):
2020 Jul 17
2
Adding users with ldif file
On 17/07/2020 19:31, RhineDevil via samba wrote:
> And by that I mean, where are the dbs, what should I rm -rf?
On Debian just remove /var/lib/samba and /var/cache/samba
> By the way how do I obtain current machine netbios name?
Depends on which netbios name, if you are referring to the one that is
in smb.conf 'netbios name = ?????', that is just the short hostname in
uppercase.