search for: fs582087

Hi I've had success building & using my own Samba4 Debian package using the instructions on the SambaWiki, specifically: https://wiki.samba.org/index.php/OS_Requirements Distribution Specific Package Installation Debian / Ubuntu # apt-get install build-essential libacl1-dev libattr1-dev \ libblkid-dev libgnutls-dev libreadline-dev python-dev libpam0g-dev \ python-dnspython gdb

I have the following setup in a samba 4.2.1 multi-dc domain DC1 - 10.10.2.50 DC2 - 10.10.2.60 DC3 - 192.168.103.2 I have a site and subnet setup for each DC in Active Directory Sites and Services DC1 server in site DC1 with subnet 10.10.2.50/32 DC2 server in site DC2 with subnet 10.10.2.0/24 DC3 server in site DC3 with subnet 192.168.103.0/24 DC3 has dhcpd setup giving machines on it's

Hi Mathias I can confirm that this fixed the RDP issue for me whilst not breaking share authentication. I'm still a bit wary of what other affects these configuration options might have though. Thanks Fred On Fri, Apr 24, 2015 at 6:37 PM, mathias dufresne <infractory at gmail.com> wrote: > Hi Carsten, > > Until yesterday I had the same issue. In thread titled "[Samba]

Hi all On latest samba 4.2.1 I have provisioned a new domain on DC1 that successfully reads RFC2307 attributes set on a user account through ADUC. wbinfo (correct uid gets resolved from sid) wbinfo -n fsmith S-1-5-21-1273750850-484487853-1026460749-1120 SID_USER (1) wbinfo -S S-1-5-21-1273750850-484487853-1026460749-1120 1000006 ldbsearch sudo ldbsearch -H

Hi Current wiki suggestion (https://wiki.samba.org/index.php/Configure_BIND_as_backend_for_Samba_AD#Interaction_with_AppArmor_or_SELinux) is to add the following to /etc/apparmor.d/local/usr.sbin.named # Samba4 DLZ and Active Directory Zones (default source installation) /usr/local/samba/lib/** rm, /usr/local/samba/private/dns.keytab r, /usr/local/samba/private/named.conf r,

I'm trying to confirm that LDAP traffic is encrypted on my Samba 4 DC. I have read and followed https://wiki.samba.org/index.php/Setup_LDAPS_on_a_DC but when I attempt to connect to the DC on port 636 or via ldaps:// or both via ldapsearch (linux) and ldp (windows) I cannot connect. Failed tests: *ldapsearch -I -H ldaps://dc* ldap_sasl_interactive_bind_s: Can't contact LDAP server (-1)