search for: e2eservices

Folks   I've managed (due to me being fat-fingered that morning) to get a DNS zone in a Samba-4 DNS setup screwed up.   Basically I was trying to add a new A record to an internal domain "e2eservices.co.uk" using the MS administration tools (not the samba-tool CLI). However instead of adding the entry "styx" to the domain, I accidently added "styx.e2eservices.co.uk"; this basically generated a child entry called "uk" under the "e2eservices.co.uk" zon...

Thanks for the suggestion, however it is not a seperate zone, i.e. it appears to be a part of the "e2eservices.co.uk" zone with child objects (analogous to "_tcp" and "_udp" in a domain zone).   Alan   -----Original message----- From:Rowland penny <rpenny at samba.org> Sent:Fri 11-12-2015 13:16 Subject:Re: [Samba] Samba-4 DNS issue To:samba at lists.samba.org; On 11/12/15 13...

On 11/12/15 13:00, Alan Hughes wrote: > Folks > > > I've managed (due to me being fat-fingered that morning) to get a DNS zone in a Samba-4 DNS setup screwed up. > > > Basically I was trying to add a new A record to an internal domain "e2eservices.co.uk" using the MS administration tools (not the samba-tool CLI). However instead of adding the entry "styx" to the domain, I accidently added "styx.e2eservices.co.uk"; this basically generated a child entry called "uk" under the "e2eservices.co.uk" zon...

...samba.org > Onderwerp: [Samba] Samba-4 DNS issue > > Folks > > > I've managed (due to me being fat-fingered that morning) to get a DNS zone > in a Samba-4 DNS setup screwed up. > > > Basically I was trying to add a new A record to an internal domain > "e2eservices.co.uk" using the MS administration tools (not the samba-tool > CLI). However instead of adding the entry "styx" to the domain, I > accidently added "styx.e2eservices.co.uk"; this basically generated a > child entry called "uk" under the "e2eservices....

Last night we updated out Samba-4 AD server to version 4.2.14 usng the SERNEt packages, running on SLES 12. We have a number of services (mail services, MANTIS, etc) that access the server via the LDAP interface and in all cases we discovered that none of them where able to establish a successful LDAP connection after the upgrade.   Previously we used plain LDAP to access the server, i.e. we did

Hello Alan, I had the same issue and I needed to add this line: ldap server require strong auth = no to smb.conf. Then, just restart/reload samba and it should work. On Fri, Jul 8, 2016 at 8:37 AM, Alan Hughes <alanhughes at e2eservices.co.uk> wrote: > Last night we updated out Samba-4 AD server to version 4.2.14 usng the > SERNEt packages, running on SLES 12. We have a number of services (mail > services, MANTIS, etc) that access the server via the LDAP interface and in > all cases we discovered that none of them...