similar to: AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade

Displaying 20 results from an estimated 2000 matches similar to: "AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade"

2018 Dec 12
0
Problem after upgrading to 4.9
Hai, Can you post /etc/krb5.conf /etc/resolv.conf /etc/hosts Output off: samba-tool dbcheck --cross-ncs And last question, are there any DC removed from the domain. 50abc2a4-574d-40b3-9d66-ee4fd5fba076/0x00000005,localaddress=> 192.168.50.40] My guess here the UUID is a removed DC. You samba config looks fine to me. Greetz, Louis > -----Oorspronkelijk bericht----- >
2018 Dec 12
0
Problem after upgrading to 4.9
about that systemd part.   systemctl daemon-reload systemctl samba-ad-dc stop   clear the logs in /va/log/samba   systemctl samba-ad-dc start   and and extra check on the dns part. sudo /usr/sbin/samba_dnsupdate --verbose and check your logs again to make sure your all ok.   Greetz,   Louis   Van: Sergio Belkin [mailto:sebelk at gmail.com] Verzonden: woensdag 12 december 2018 14:16 Aan:
2018 Dec 12
3
Problem after upgrading to 4.9
Hi, I use the Van Bell repo, I've upgraded from samba 4.7 to samba 4.9 but now it fails, these are the errors: dic 12 09:14:49 samba4 samba[4881]: task[dnsupdate][4881]: [2018/12/12 09:14:49.372290, 0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) dic 12 09:14:49 samba4 samba[4881]: task[dnsupdate][4881]: /usr/sbin/samba_dnsupdate: Failed to bind to uuid
2018 Dec 12
5
Problem after upgrading to 4.9
Thanks Louis; /etc/krb5.conf [libdefaults] default_realm = EXAMPLE.COM dns_lookup_realm = false dns_lookup_kdc = true /etc/resolv.conf search example.com nameserver 192.168.50.40 /etc/hosts 127.0.0.1 localhost samba4.example.com 192.168.50.40 samba4.example.com samba4 ldap.example.com Output off: samba-tool dbcheck --cross-ncs NOTE: old (due to rename
2019 Jan 02
0
AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade
2018-12-31 20:50 időpontban L.P.H. van Belle via samba ezt írta: > Can you try to upgrade to any 4.8 version then to 4.9.4? > might work, atleast my guess this will have a better chance get passed > this bug. > I can confirm that an upgrade to 4.7.3 to 4.8.5 works. But! After upgrading the dnsupdate did not work, giving these log messages: [2019/01/02 19:18:42.908955, 0]
2015 Aug 28
0
More on bind_dlz - documentation I have not found
On 08/28/2015 11:04 AM, Rowland Penny wrote: > On 28/08/15 15:56, Robert Moskowitz wrote: >> >> >> On 08/28/2015 10:42 AM, L.P.H. van Belle wrote: >>> Are you setting up a AD DC or old style NT PDC ? >>> >>> see : >>> /etc/default/sernet-samba to "classic". for NT PDC >>> /etc/default/sernet-samba to "ad". for AD
2017 Feb 08
0
ntp and samba43 on FreeBSD-103.
On Wed, February 8, 2017 10:40, James B. Byrne wrote: > > Samba43 was installed on FreeBSD-10.3 as a binary package using the > pkg utility. Other than ignorance I had no problems with provisioning > a Domain with it. On the other hand Samba44 could not be successfully > provisioned at the time I was setting Samba up which is why we went > with Samba43. > > The ports
2020 Oct 22
0
new dc does not allow login..?
On 22/10/2020 19:49, Joachim Lindenberg wrote: > Password for Administrator at SAMBA.LINDENBERG.ONE: > > Failed to bind to uuid 50abc2a4-574d-40b3-9d66-ee4fd5fba076 for ncacn_ip_tcp:192.168.177.19[49153,sign,target_hostname=cobra.samba.lindenberg.one,abstract_syntax=50abc2a4-574d-40b3-9d66-ee4fd5fba076/0x00000005,localaddress=192.168.177.19] NT_STATUS_LOGON_FAILURE > ERROR: Connecting
2019 Jan 02
0
AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade
On Wed, 2 Jan 2019 19:35:04 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Wed, 02 Jan 2019 20:09:44 +0100 > Král Gergely via samba <samba at lists.samba.org> wrote: > > > 2018-12-31 20:50 időpontban L.P.H. van Belle via samba ezt írta: > > > Can you try to upgrade to any 4.8 version then to 4.9.4? > > > might work, atleast my
2019 Jan 02
0
AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade
This bug affects only upgrade via source or via packages (louis's apt) too? On Wed, Jan 2, 2019 at 8:38 PM Viktor Trojanovic via samba < samba at lists.samba.org> wrote: > > > > On 2 Jan 2019, at 22:43, Rowland Penny via samba <samba at lists.samba.org> > wrote: > > > > On Wed, 2 Jan 2019 19:35:04 +0000 > > Rowland Penny via samba <samba at
2015 Aug 28
0
More on bind_dlz - documentation I have not found
Progress... On 08/28/2015 11:59 AM, Rowland Penny wrote: > On 28/08/15 16:45, Robert Moskowitz wrote: >> >> >> On 08/28/2015 11:04 AM, Rowland Penny wrote: >>> On 28/08/15 15:56, Robert Moskowitz wrote: >>>> >>>> >>>> On 08/28/2015 10:42 AM, L.P.H. van Belle wrote: >>>>> Are you setting up a AD DC or old style NT PDC
2015 Aug 28
2
More on bind_dlz - documentation I have not found
On 28/08/15 16:45, Robert Moskowitz wrote: > > > On 08/28/2015 11:04 AM, Rowland Penny wrote: >> On 28/08/15 15:56, Robert Moskowitz wrote: >>> >>> >>> On 08/28/2015 10:42 AM, L.P.H. van Belle wrote: >>>> Are you setting up a AD DC or old style NT PDC ? >>>> >>>> see : >>>> /etc/default/sernet-samba to
2019 Jan 02
2
AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade
> On 2 Jan 2019, at 22:43, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Wed, 2 Jan 2019 19:35:04 +0000 > Rowland Penny via samba <samba at lists.samba.org> wrote: > >> On Wed, 02 Jan 2019 20:09:44 +0100 >> Král Gergely via samba <samba at lists.samba.org> wrote: >> >>> 2018-12-31 20:50 időpontban L.P.H. van Belle
2019 Jan 02
2
AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade
On Wed, 02 Jan 2019 20:09:44 +0100 Král Gergely via samba <samba at lists.samba.org> wrote: > 2018-12-31 20:50 időpontban L.P.H. van Belle via samba ezt írta: > > Can you try to upgrade to any 4.8 version then to 4.9.4? > > might work, atleast my guess this will have a better chance get > > passed this bug. > > > > I can confirm that an upgrade to 4.7.3 to
2013 Oct 28
1
bug with redirect output samba-tool ?
? Hai, ? When i try to use this line: ? samba-tool dns query 192.168.249.225 mydomain.lan @ ALL -UAdministrator | less ? Failed to bind to uuid 50abc2a4-574d-40b3-9d66-ee4fd5fba076 for 50abc2a4-574d-40b3-9d66-ee4fd5fba076 at ncacn_ip_tcp:192.168.249.225[49175,sign] NT_STATUS_NET_WRITE_FAULT ERROR(runtime): uncaught exception - (-1073741614, 'NT_STATUS_NET_WRITE_FAULT') ? File
2018 Mar 23
0
samba 4.7->4.8 in place upgrade
On 3/23/2018 8:50 AM, Sven Vogel via samba wrote: > Hi, > > i have the same problem. Inplace upgrade and i get the following > error. > > Mar 23 13:46:50 orion2 systemd[1]: Started Session 30346 of user root. > Mar 23 13:46:50 orion2 systemd-logind[1316]: Removed session 30346. > Mar 23 13:46:50 orion2 sernet-samba-ad[7358]: Shutting down SAMBA AD > services : ..done
2024 Jun 30
1
Looking for Python docs/examples to modify DNS via keytab
On Sun, 30 Jun 2024 00:22:57 -0700 christian baltini <christian.baltini at gmail.com> wrote: > > This is the output I get: > > (venv) root at ubu1:~/py_krb# samba-tool dns zonelist localhost > --use-krb5-ccache=/tmp/krb5cc_0 Failed to bind to uuid > 50abc2a4-574d-40b3-9d66-ee4fd5fba076 for >
2015 Aug 28
2
More on bind_dlz - documentation I have not found
On 28/08/15 15:56, Robert Moskowitz wrote: > > > On 08/28/2015 10:42 AM, L.P.H. van Belle wrote: >> Are you setting up a AD DC or old style NT PDC ? >> >> see : >> /etc/default/sernet-samba to "classic". for NT PDC >> /etc/default/sernet-samba to "ad". for AD DC. > More: > > # service sernet-samba-ad status > Checking for SAMBA
2018 Mar 23
2
samba 4.7->4.8 in place upgrade
Hi, i have the same problem. Inplace upgrade and i get the following error. Mar 23 13:46:50 orion2 systemd[1]: Started Session 30346 of user root. Mar 23 13:46:50 orion2 systemd-logind[1316]: Removed session 30346. Mar 23 13:46:50 orion2 sernet-samba-ad[7358]: Shutting down SAMBA AD services : ..done Mar 23 13:46:50 orion2 systemd[1]: Stopped LSB: initscript for the SAMBA AD services. Mar 23
2015 Jul 27
0
4.2.2 as AD with 2 DCs: database incoherency
Thank you Rowland for this. I tried using Sernet's Samba 4.2.2 and failed: All the following command were ran on DC20 samba-tool dns zonecreate dc20.ad.domain.tld 0.0.10.in-addr.arpa Password for [administrator at AD.DOMAIN.TLD]: Failed to bind to uuid 50abc2a4-574d-40b3-9d66-ee4fd5fba076 for