similar to: logon drive, ldap ssl = start_tls, ssh and client/server encryption (and logon.bat permission tip)

Hi, I've a problem in connecting samba 2.2.5 to LDAP with ldap ssl = start_tls. I've already patched the file pdb_ldap.c and configure.in and run autconf (as described in the Samba-LDAP-PDC howto). However, doing a rpcclient servername -U root%password -c "enumprinters" shows this in the log: [2002/08/23 16:50:44, 0] passdb/pdb_ldap.c:ldap_open_connection(181) Failed to

I have 20+ freebsd 10 samba 4 servers joined to our local microsoft active directory. At the moment things work well enough. However the windows administrator wants to tighten his AD security by requiring tls encrypted ldap. When I add: ldap ssl = start_tls ldap ssl ads = yes cldap port = 389 the net ads commands fail: net ads testjoin Failed to issue the StartTLS instruction: Connect error

Hi, i was the one who had problems with the start_tls function. I applied the patch yesterday. But now the compiling doesn't work anymore. This is what happens : --------snipp---------- [Lots of compiling output cut away] Linking bin/smbd passdb/pdb_ldap.o: In function `pdb_setsampwent': passdb/pdb_ldap.o(.text+0x1730): multiple definition of `pdb_setsampwent'

> Message: 8 > Date: Mon, 24 Jun 2002 18:13:33 -0500 (CDT) > From: "Gerald (Jerry) Carter" <jerry@samba.org> > To: samba@samba.org > Subject: [Samba] patch for 2.2.5 and check for start_tls with OpenLDAP 2.0.x libs > > This message is in MIME format. The first part should be readable text, > while the remaining parts are likely unreadable without

FYI.... There is a bu in the configure script for 2.2.5 that prevents the script from locating the start_tls function in the OpenLDAP 2.0.x libs. Apply this patch and rerun autoconf. Should fix it. Patches configure.in and passdb/pdb_ldap.c Sorry for the inconvience. cheers, jerry --------------------------------------------------------------------- Hewlett-Packard

On Wed, 2015-01-28 at 10:11 -0600, Russell Poyner wrote: > I have 20+ freebsd 10 samba 4 servers joined to our local microsoft > active directory. At the moment things work well enough. However the > windows administrator wants to tighten his AD security by requiring tls > encrypted ldap. > > When I add: > ldap ssl = start_tls > ldap ssl ads = yes > cldap port = 389

hi, it seems when dovecot use ldap user and password databases it's not possible to use tls connection and certificate with the ldap connection. wouldn't it be possible to use the same certificate on the ldap connection as used in the ssl_{cert,key}_file parameters in the dovecot conf (or would be possible to use it's own cert in the ldap conf file? yours. -- Levente

I've encountered exact same issue as in this thread below, but I cannot figure out what the solution is https://lists.samba.org/archive/samba/2015-February/189012.html In short, my Samba 4.1.22 used to be a member of the domain, with these ldap ssl settings in the config: ldap ssl = start tls ldap ssl ads = Yes I've updated it to 4.3.8, and it now cannot talk to the domain, it shows

Andrew, Thanks for the pointers about looking into the ldap client libs. I think I've found a situation where tls connections to the AD server on port 389 have trouble. I've added the CA cert to ldap.conf, and to the ca_root_nss file on this system. First what works: 1. ldapsearch commands with -Z to force use of tls (configured in /usr/local/etc/ldap.conf) 2. ssl connections with

I upgraded from 12.2 to 12.4 and found that my happy little eventmachine processes die with: terminate called after throwing an instance of ''std::runtime_error'' what(): call SetTlsParms before calling StartTls Here''s what I believe is the relevant snippet of my code, which calls start_tls() in the connection_completed() callback: connection =

Hi everyone. Does anyone have any preferences or ideas for an interface for SSL certificates, both client-side and server-side? At present, the only interface is EventMachine::Connection#start_tls, which uses a built-in self-signed cert on the server side. On the cilent side, it accepts any well-formed cert (that is, it doesn''t check that the remote cert is signed by a trusted authority).

Hello, I am running RedHat 8 and have the same problem with both the distributed and updated samba RPMS (2.2.5 -> 2.2.7) and the source dist (2.2.8a). I can seem to change many options but the "logon script = logon.bat" doesn't want to change. This is what I have in my smb.conf file : [global] ...some stuff... logon script = %U.bat logon drive = H: [netlogon]

On win XP Pro workstations it would be so convenient if the domain logon script which is stored on the samba pdc could be made to run with Administrative (or System) privileges. I know that I can interactively run another security context by choosing "run as user" but how could I achieve this non-interactively and domain wide whilst a "limited account" is loggin in? Thanks

Hi all, I've been searching the lists and web for an answer but i'm stumped hope some one here has an answer for me. As I'm new to this sysadmin role. I have set up OpenLDAP to authenticate our linux users and exim MTAs. This all works fine with OpenLDAP only providing a ldaps:/// connection on 636. However I cannot for the life of me get samba to speak tls to it. I've seen

I know this is something which should have a simple fix but I'm failing to see it somehow. I'm moving samba service between a couple of FreeBSD systems (9.3 to 10.2), and I'm stuck on getting samba on the new machine to connect to our openldap server over ssl - frustrating since I've been running samba+ldap for 15 years or so; feel sure I'm missing something basic!

We setted up a PDC with Samba 2.2.5-UL (United Linux with Service Pack 2a) and everything is working fine. On startup there is a script running which will do some work and map a specific share from a server. But sometimes for some reason this script is not running on some workstations. After disconnecting all the shares (net use * /delete) and a reboot everything is working again. When does

I recently set up a samba PDC 2.2.8 for testing purposes only. Everything runs well enough now. There is one thing I can't seem to get to work. I made a logon.bat logon script for sharing a share called 'databank' on T: and it works correctly, but trying to get the windows mount the home folder too results in no mounting. That is: no databank and no home folder (on T: and Y:). My

Hey, I have a fedora core 1 machine with samba 3 PDC. I switched the password backend ('passdb' ) from 'smbpasswd' to 'tdbsam'. The problem is that my win 98 machine stop mapping my home directory. I swtiched back to 'smbpasswd' and it works fine. 'net time \\server /set /yes' and 'net use p: \\server\apps' work perfectly. My logon.bat contains the

Dear Samba-users, I cannot manage to make samba read my logon.script for windows clients where basicaly networkdrive-mapping is done. Samba complaines about not having permission... Error: switch message SMBntcreateX (pid 28286) [2004/12/03 11:27:31, 3] smbd/dosmode.c:unix_mode(110) unix_mode(logon.bat) returning 0744 [2004/12/03 11:27:31, 3] smbd/open.c:open_file(173) Error opening file

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil Url : http://lists.samba.org/archive/samba/attachments/20041203/d1eed200/attachment.bin