search for: ldpa

...ntes particionados con windows(xp) y linux (mandrake),con un servidor samba sobre redhat, tengo windows comunicandose bien con samba, funciona muy bien, pero no s? como conectarme desde linux, y si es posible con los mismos username y password. Creo!, no estoy segura, de que necesito configurar ldpa pero ?Qu? tendr?a que agregar al samba.conf para que trabaje? gracias!!

...clients and Samba AD for Windows clients, establishing a trust between domains. I have done long ago the other way of the original poster problem, NFS Kerberized NFS shares from a domain using MIT Kerberos (via FreeIPA), shares to Windows clients with Samba, but Samba standalone shares, doing LDPA integration with FreeIPA 389 server, but I would not recommend that now that the AD implementation of Samba is robust enough. Note: Now that CentOS 8 where mentioned early on the list, CentOS 8 clients joined to a Samba domain using SSSD works pretty well. Some tips at https://lists.samba.org/a...

...lients, establishing a trust between >> domains. I have done long ago the other way of the original poster >> problem, NFS Kerberized NFS shares from a domain using MIT Kerberos >> (via FreeIPA), shares to Windows clients with Samba, but Samba >> standalone shares, doing LDPA integration with FreeIPA 389 server, but >> I would not recommend that now that the AD implementation of Samba is >> robust enough. >> >> Note: Now that CentOS 8 where mentioned early on the list, CentOS 8 >> clients joined to a Samba domain using SSSD works pretty...

...ween >>>> domains. I have done long ago the other way of the original poster >>>> problem, NFS Kerberized NFS shares from a domain using MIT Kerberos >>>> (via FreeIPA), shares to Windows clients with Samba, but Samba >>>> standalone shares, doing LDPA integration with FreeIPA 389 server, >>>> but I would not recommend that now that the AD implementation of >>>> Samba is robust enough. >>>> >>>> Note: Now that CentOS 8 where mentioned early on the list, CentOS 8 >>>> clients joined to...

...AD for Windows clients, establishing a trust between > domains. I have done long ago the other way of the original poster > problem, NFS Kerberized NFS shares from a domain using MIT Kerberos > (via FreeIPA), shares to Windows clients with Samba, but Samba > standalone shares, doing LDPA integration with FreeIPA 389 server, but > I would not recommend that now that the AD implementation of Samba is > robust enough. > > Note: Now that CentOS 8 where mentioned early on the list, CentOS 8 > clients joined to a Samba domain using SSSD works pretty well. Some > tip...

...hing a trust between >>> domains. I have done long ago the other way of the original poster >>> problem, NFS Kerberized NFS shares from a domain using MIT Kerberos >>> (via FreeIPA), shares to Windows clients with Samba, but Samba >>> standalone shares, doing LDPA integration with FreeIPA 389 server, >>> but I would not recommend that now that the AD implementation of >>> Samba is robust enough. >>> >>> Note: Now that CentOS 8 where mentioned early on the list, CentOS 8 >>> clients joined to a Samba domain usin...

On 7/24/2020 7:25 AM, Peter Milesson via samba wrote: > > On 2020-07-24 12:57, Jason Keltz via samba wrote: >> Hi Rowland, >> >> In effect, I'm still using Samba on the DC, which is why I still >> thought this was relevant on the mailing list. :) >> >> The reason in particular that I was looking at sssd client as opposed >> to winbind was that?

...ave a samba4 server and want to use postfix+dovecot - dovecot version is 2.0.11 as for the postfix side everything is OK (all the LDAP lookups works without any error, tested also manually with postmap -q) the real pain is with dovecot deliver: it seems that sometimes lda tries to lookup to the LDPA (samba 4) server, got a reply, an then report(after 2 minutes) a lookup timeout error the really strange thing is that (very seldom) lda works, but most of the times I got the timeout error. The strange thing is that if I use ldapsearch I never got timeout neither late replies, and even postf...