Displaying 20 results from an estimated 8000 matches similar to: "Van Belle Repo - 4.10 for Bionic"
2019 Mar 31
2
Van Belle Repo - 4.10 for Bionic
On Sun, 31 Mar 2019 13:55:18 +0200
Viktor Trojanovic via samba <samba at lists.samba.org> wrote:
> On Sat, 30 Mar 2019 at 17:45, L.P.H. van Belle <belle at bazuin.nl>
> wrote:
> >
> > you can upgrade from 4.7 to 4.9.
> > but you must run samba-tool dbcheck
> > that should work also. after the check run samba-tool dbcheck
> > --reindex
>
> I
2019 Mar 31
3
Van Belle Repo - 4.10 for Bionic
On Sun, 31 Mar 2019 14:29:32 +0200
Viktor Trojanovic <viktor at troja.ch> wrote:
> On Sun, 31 Mar 2019 at 14:22, Rowland Penny via samba
> <samba at lists.samba.org> wrote:
> >
> > On Sun, 31 Mar 2019 13:55:18 +0200
> > Viktor Trojanovic via samba <samba at lists.samba.org> wrote:
> >
> > > On Sat, 30 Mar 2019 at 17:45, L.P.H. van Belle
2019 Mar 31
0
Van Belle Repo - 4.10 for Bionic
On Sat, 30 Mar 2019 at 17:45, L.P.H. van Belle <belle at bazuin.nl> wrote:
>
> you can upgrade from 4.7 to 4.9.
> but you must run samba-tool dbcheck
> that should work also. after the check run samba-tool dbcheck --reindex
>
I thought that maybe indeed I did something wrong the last time so I
followed your advice. Unfortunately, it broke my DC again. (Luckily, I
made a
2019 Mar 31
0
Van Belle Repo - 4.10 for Bionic
On Sun, 31 Mar 2019 at 14:22, Rowland Penny via samba
<samba at lists.samba.org> wrote:
>
> On Sun, 31 Mar 2019 13:55:18 +0200
> Viktor Trojanovic via samba <samba at lists.samba.org> wrote:
>
> > On Sat, 30 Mar 2019 at 17:45, L.P.H. van Belle <belle at bazuin.nl>
> > wrote:
> > >
> > > you can upgrade from 4.7 to 4.9.
> > > but
2019 Mar 31
0
Van Belle Repo - 4.10 for Bionic
On Sun, 31 Mar 2019 at 14:45, Rowland Penny via samba
<samba at lists.samba.org> wrote:
>
> On Sun, 31 Mar 2019 14:29:32 +0200
> Viktor Trojanovic <viktor at troja.ch> wrote:
>
> > On Sun, 31 Mar 2019 at 14:22, Rowland Penny via samba
> > <samba at lists.samba.org> wrote:
> > >
> > > On Sun, 31 Mar 2019 13:55:18 +0200
> > >
2020 Aug 24
2
problem whith samba and dnsupdate command
Problem whith dnsupdate -->
/etc/samba# samba_dnsupdate --all-names --fail-immediately
Failed to get Kerberos credentials, falling back to samba-tool: kinit for
DOMAIN-SERVER2$@POLICIA2.RIONEGRO.GOV.AR failed (Cannot contact any KDC for
requested realm)
ERROR(runtime): uncaught exception - (9711,
'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS')
File
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 Apr 26
2
DNS forwarding not working.
I followed this url to set up Samba AD DC.
https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt
I do have it working. I am testing with a Windows 10 VM as a member of
the domain.
The machine joins the domain. Also, as administrator, I can create and
enforce
Group Policies. from this Windows machine.
I have a Fedora 29 server which serves DHCP and DNS (and
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
2018 May 24
5
Samba 4.8 RODC not working
Hi,
It's my first try to setup RODC using Samba 4.8. We have latest Samba 4.7 environnement with 2 DC and some file servers.
Joining the DC to the domain is OK using samba-tool domain join command. The domain controller appears in the DC list (MMC)
However, users cannot be authenticated. Samba is running but these ports are closed :
netbios-ssn 139/tcp # NETBIOS session service
2018 Mar 16
2
samba 4.7->4.8 in place upgrade
On 3/16/2018 10:07 AM, barış tombul via samba wrote:
> same problem.
> Never pass the 4.8 version.
>
> samba-tool dbcheck --cross-ncs --fix
> Unable to determine the DomainSID, can not enforce uniqueness constraint on
> local domainSIDs
>
> Searching for dsServiceName in rootDSE failed: operations error at
> ../source4/dsdb/samdb/ldb_modules/rootdse.c:516
> Failed
2018 Dec 31
3
AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade
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.
Greetz,
Louis
> Op 31 dec. 2018 om 18:35 heeft Král Gergely via samba <samba at lists.samba.org> het volgende geschreven:
>
> 2018-12-31 17:29 id??pontban Rowland Penny via samba ezt írta:
>
>>>
>>
>> OK,
2018 Dec 23
2
After upgrade to 4.9.4, internal DNS no longer working
I was too quick to send my previous email. It can't really be a problem of
the package since I have, as mentioned, another system with the exact same
setup and the exact same package versions and it all works there...
On Sun, 23 Dec 2018 at 11:18, Viktor Trojanovic <viktor at troja.ch> wrote:
> Yes, I tried running dbcheck (see first email), it showed 0 errors from
> the start, I
2019 Mar 30
1
Van Belle Repo - 4.10 for Bionic
4.10 is not yet in the repo.
almost.. im preparing for it.
i think next week.
Greetz,
Louis
Op 29 mrt. 2019, om 21:28, Viktor Trojanovic <viktor at troja.ch> schreef:
Hi Louis,
I see that you already offer 4.10 in your repo for Stretch. Would be great if you could make it available for Bionic, too.
Thanks.
- Viktor
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 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
2019 Jun 19
4
DLZ Backend DNS Hosed
Hello,
I'm in trouble here with what appears to be a total meltdown of my DNS on my Domain Controllers.
I only have two DCs right now and I cannot resolve anything on either of them. I am on Ubuntu 16.04 with a compiled version of Samba 4.10.4.
I also have a compiled version of BIND 9.10.3-P4-Ubuntu <id:ebd72b3>
# service bind9 status
? bind9.service - BIND Domain Name Server
?
2018 Dec 26
3
After upgrade to 4.9.4, internal DNS no longer working
On Wed, 26 Dec 2018 14:40:10 +0100
Viktor Trojanovic <viktor at troja.ch> wrote:
> Hi Rowland,
>
> Thanks for taking an interest.
>
> On Wed, 26 Dec 2018 at 14:27, Rowland Penny via samba
> <samba at lists.samba.org> wrote:
>
> > On Wed, 26 Dec 2018 11:43:37 +0100
> > Viktor Trojanovic <viktor at troja.ch> wrote:
> >
> > > I
2018 Dec 23
2
After upgrade to 4.9.4, internal DNS no longer working
The two systems I'm referring to are on different domains, different
locations. No connection whatsoever except me being the one administering
both.
According to oEMInformation the server was provisioned by 4.3.3. I just
checked the Samba log file and it seems that version 4.7.4 was running
before the update.
I'm now looking at the logs right before the upgrade and indeed, there have
2016 Apr 28
3
RNDC errors using SAMBA_INTERNAL_DNS
Hi all,
I've set up a simple domain using Samba 4.4.2 from source under Ubuntu
16.04.
I accepted the usual defaults and basically followed wiki.samba.org to
the letter. The main thing is I'm using Samba's internal DNS and not
Bind (Bind is not even installed on the system).
In the log.samba file on the first DC I kept getting this:
[2016/04/28 17:01:02.716292, 0]