similar to: samba4

hi, ? i have recently installed a samba 4 in a DC role. The distribution is a debian jessie/sid, the version of samba is 4.1.7. The server is globally working but there is some litle trouble. on the server itself, i can do a kinit without probleme but if i try a kpasswsd, i obtain the following ? root at station:/var/log/samba# kinit Password for administrator at TOTO.FR: root at

On Tue, 2015-03-03 at 14:50 +0000, Mario Pio Russo wrote: > Good Day All > > first of all thank you for this mailing list, it's really great, as great > is Samba :D > > I have a question regarding Samba4 and the possibility to delegate > authentication to an external LDAP server using Cyrus SASL. > > Basically I have already successfully implemented an

? ? ?Quick and easy question: I have a network which already has its own kerberos + ldap servers running and I want to setup a samba4 box as AD. So, from conversations here and on irc, the best thing to do is to setup the samba4's built-in kerberos to do cross-realm authentication with the other kerberos server. Now, how would those crossed users look like in samba? Or, how would they be

thanks for your answer, I cannot do the reverse authentication unfortunately. Everything has to work as I have described. Furthermore I cannot change my external trust authority for authentication. From this thread it looks like the only option is to use local password for the Samba4 domain users, which add some complexity when managing IDs (and above all passwords), as a single user might have

Hi everyone, I did a test migration from Samba3 to Samba4. So far everything works fine. Great work! Thanks to Samba team. I want to share my experience with you and look for your comments. My existing servers: 1. Samba 3.4.5(compiled) server: domain logon + file sharing + printer sharing ( 300 users + 200 win7) 2. 5 samba3 file servers(using the same ldap backend, so uid and gid are

Hello everybody, Fist a little about our setup. We have an Debian (7) Wheezy, now upgraded to Debian (testing) Jessie with Samba4 as PDC, Kerberos and LDAP - all provided through Samba4, and bind9 and isc-dhcp server for DDNS and DHCP, our environment is a mix of Linux (Debian Jessie), Mac (Maverick and Yosemite) and Windows 7 and 8.1 clients. The Windows clients use Samba and are all part of

On Tue, 19 Mar 2019 11:03:12 -0500 John McMonagle via samba <samba at lists.samba.org> wrote: > We are currently running samba3 nt4 domain controllers using > smb-ldap-tools. We want to convert to samba4 ad so we can run new > versions of windows server. Why do you need a newer Windows version ? You state you have no Windows workstations. But you are correct, you need to upgrade,

Hi! We're currently in the process of evaluating an upgrade from our current setup (Samba3 with Kerberos/OpenLDAP and Bind), to Samba4. When we started reading about the migration process, we were led to believe that OpenLDAP wasn't fully supported in Samba4, and thus decided to use Samba4's builtin solution. Then upon reading the How-To on the Wiki, the "Migrating from LDAP

> For Samba4 AD, I see mentions of pam-winbind, pam-sss, sssd, kerberos, and > don't > quite understand which of these I actually need. Its your party... and,., you forgot pam-ldap ;-) You need to set UID/GIDs on the users and groups. And you need to make sure these users have a home dir. I choose kerberos for my linux auth. Per example for ssh, if you install ssh-krb5 in

Got it working! I did download the openssh source from https://www.openssh.com/ I added the --with-kerberos5 option to the configure script and otherwise used the options that Slackware uses to build the package: export CFLAGS="-O2 -fPIC" export ARCH=`uname -m` ./configure \ --prefix=/usr \ --mandir=/usr/man \ --sysconfdir=/etc/ssh \ --without-pam \ --with-kerberos5 \

Hi everybody. I attended the Samba conference at the FOSDEM yesterday. Jeremy Allison was great, and explained very clearly the problems faced by implementing an Active Directory controller. The CIFS protocol is required in heterogenous environments. Jeremy made it pretty clear that even in pure Unix environments, CIFS is quite superior to NFSv4. Samba is thus a required component of pretty

We run Apple's OD to support our Linux, Mac, and Windows clients and servers. We are under pressure to use AD because more and more software coming out for Windows requires it. We don't want to use AD, so Samba4 looks good. However, we don't want to pull apart our directory to implement samba4. Is there a way to get Samba 4 running so that it is able to use the existing LDAP and

If this is a member server. Just install minimal debian server + ssh. Point dns (resolv.conf) to AD-DC. search ada.de nameserver IP_AD_DC Now apt-get install samba winbind acl attr krb5-user Keep all default, you dont need to change anything.. After the install off all packages. systemctl stop smbd winbind (optional nmbd) (optional : systemctl disable nmbd) Setup the correct smb.conf for a

Hi Lucas, Am 17.10.2016 um 17:19 schrieb Lucas Ferrari Correa via samba: > So what i need to know is, even with the difference between the LDAP > server and Samba4 structure, it is possible to use Samba4 for an > external LDAP server authentication and other LDAP purposes? Sure you can authenticate to Samba AD using the LDAP(S) protocol. Additionally, it enables you to authenticate

Samba4 4.0.0beta4, CentOS 6.3 I have a 3*DC Samba4 domain in which everything tested so far appears to be working OK: ldap, kerberos, dns, windows client joins, replication, etc. My question concerns binding Linux clients (CentOS 6) to the Samba4 LDAP server using sssd. If in /etc/sssd/sssd.conf I have several test boxes that use: [domain/SAMBA4] ..... ldap_default_bind_dn =

Hello, I am facing a strange situation: I have downloaded the sources with git, configure and compiled (Samba Version 4.1.0pre1-GIT-76fa5ee) just like in the HowTo doc, here: https://wiki.samba.org/index.php/Samba4/HOWTO All the tests were ok. I am using internal DNS of Samba4. I have successfully added one XP machine to the domain controlled by samba server. On this XP system I have

I have setup a Samba4 server and would like to report my experiences in the hope that it may be helpful to others. I basically followed the official Samba4 HowTo, which is very good. Based on what I have seen, this is the only document I would recommend people to follow. I will try not to repeat things that are covered in the HowTo, but rather focus on what I did differently or additionally,

Hi, I think it is great that samba4 has a single sign on solution for Windows platforms and it seems to work well too, but I am wondering is it possible to do the same for a Linux environment? I have been studying how to implement single sign on using the Ubuntu way through this document: https://help.ubuntu.com/community/SingleSignOn and I am wondering if I can do the same with samba4 where the

Things goes further. To use GSSAPI and so the Kerberos ticket obtained with kinit I was missing "-Y GSSAPI". It seems GSSAPI and TLS are meant to be used together: ---------------------------------------- ldapsearch -Y GSSAPI -LLL -H ldaps://SAMBA.DOMAIN.TLD SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Server is unwilling to perform (53) additional info:

Question: Right now samba4 is great as in all-in-one solution (samba, kerberos, ldap, dns) into one service. Is it possible to split it up so that for example, I run openldap on one server, kerberos on another server, and then dns/samba on a third server? br, Quinn