similar to: [Announce] Samba 4.8.1 Available for Download

Hai, i've looked it up. /quote Rowland. > > I'll go search for this a bit, and start with the build of 4.8.1 > > while doing that. > > I would hang on with that, Denis has just asked if the 'don't upgrade > to 4.8.0 bug' has been fixed, it isn't mentioned in the release notes. > It seems to have gone in, just not mentioned in the release notes

======================================================== "In politics stupidity is not a handicap." Napoleon Bonaparte ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.7 release series. Changes since 4.7.6: -------------------- o Jeremy Allison <jra at

======================================================== "In politics stupidity is not a handicap." Napoleon Bonaparte ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.7 release series. Changes since 4.7.6: -------------------- o Jeremy Allison <jra at

======================================================== "Every once in a while, a new technology, an old problem, and a big idea turn into an innovation." Dean Kamen ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.8 release series. Major bug fixes include:

======================================================== "Every once in a while, a new technology, an old problem, and a big idea turn into an innovation." Dean Kamen ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.8 release series. Major bug fixes include:

Thanks for getting back to me. I managed to restore my domain from a backup that I forgot I had. Glad you know about the bug! On Fri, Apr 13, 2018 at 4:04 AM, Andrew Bartlett <abartlet at samba.org> wrote: > On Thu, 2018-04-12 at 13:02 -0400, Andrew Dumaresq via samba wrote: > > Hello, > > > > Today I tried to upgrade to samba 4.8.0, the upgrade seems to have >

On 5/22/2018 9:41 AM, Carlos Bordon via samba wrote: > What is the problem of 4.8.0 and 4.8.1? > > 2018-05-22 9:38 GMT-03:00 Stefan G. Weichinger via samba < > samba at lists.samba.org>: > >> Am 2018-05-22 um 14:35 schrieb Rowland Penny via samba: >> >>> If everything is working okay, you can stick with 4.7.x , but you can, >>> if you so wish,

On 5/22/2018 9:50 AM, Carlos Bordon via samba wrote: > i installed in one DC, > > Could I go from 4.8.1 to 4.82? > > 2018-05-22 10:46 GMT-03:00 lingpanda101 <lingpanda101 at gmail.com>: > >> On 5/22/2018 9:41 AM, Carlos Bordon via samba wrote: >> >>> What is the problem of 4.8.0 and 4.8.1? >>> >>> 2018-05-22 9:38 GMT-03:00 Stefan G.

Am 2018-05-22 um 14:35 schrieb Rowland Penny via samba: > If everything is working okay, you can stick with 4.7.x , but you can, > if you so wish, upgrade to 4.8.2. Just steer clear of 4.8.0 and 4.8.1 > > It doesn't seem to matter whether you upgrade or join using 4.8.0 and > 4.8.1 , they both seem to cause problems which have been fixed in 4.8.2 We have no real problems with

On Thu, 2018-03-15 at 14:34 -0400, Justin Foreman wrote: > The problem does not happen if I recreate the domain from scratch. I’m able to successfully join 4.8.0 to a 4.6.7 domain built from scratch (just tried it). One thing that I will note is that I also saw SPN creation failures when attempting to join Windows 2008 R2. So it’s not a Samba 4.8.0 problem. It’s a problem with my database

On Thu, 2018-03-15 at 16:10 -0400, Justin Foreman wrote: > Okay. The master build worked on the join. Excellent. So it was 4.8.0 having a problem. > > I’ve attempted to join 2008 R2 now to 4.8.0 but it still blue screens. Should I start a new thread for clarity’s sake? So, I think this, the upgrade issues and even the old servicePrincipalName handling bug is all the same thing. What

As guidance, we look forward to Samba 4.8.1 for upgrade. However, the same bug remains in version 4.8.0 Again I will go back to the previous version (4.7.5) Does anyone else share this problem? samba4.service - LSB: start and stop samba4 Loaded: loaded (/etc/rc.d/init.d/samba4; bad; vendor preset: disabled) Active: active (running) since Thu 2018-04-26 16:32:31 -04; 6 minutes ago

Can anyone tell me in which likely version will fix this problem. If this bug will really be fixed? I noticed that it does not appear in the list of known defects of samba 4.8.0 and 4.8.1. Thank you for your help; *Atte.* *Rafael d'Ávila.* *"O único lugar onde o sucesso vem antes do trabalho é no dicionário."* Em qui, 26 de abr de 2018 às 16:55, Rowland Penny via samba <

Am 2018-05-21 um 09:31 schrieb Rowland Penny via samba: > On Mon, 21 May 2018 09:21:42 +1200 > Andrew Bartlett via samba <samba at lists.samba.org> wrote: > >> On Fri, 2018-05-18 at 14:44 +0200, Micha Ballmann via samba wrote: >>> Is it possible to Mix Samba 4.8.2 with Samba 4.7.7? >>> >>> I have three domain controller (up to 10000 users) running

On Fri, 18 May 2018 09:51:29 -0300 Carlos via samba <samba at lists.samba.org> wrote: > Hi! > > uhum..... > > I upgraded DC3(4.7.7 to 4.8.0) to some months ago but an error > occurred, then demote dc and join again, Is it some rubbish that got > stuck? Did you run 'sambaundoguididx' before the demote and speaking of demote, why did you demote, you could just

On Fri, 18 May 2018 08:50:44 -0300 Carlos via samba <samba at lists.samba.org> wrote: > Hi! > > Thanks very much agian, but a really think is "good"  all dcs > replication(full  mesh). > > I read more about "sites"(link send for you). > > But i dont understand msg the erro: > > ------------------- > > May 17 16:54:44 dc2

Hi Louis, normally you are building these wonderful samba debian packages for us :-) Is there a reason, that you didnt create packages for samba 4.8? Tfh! Oliver

After performing the update of samba version 4.7.3 to version 4.8.0, an error occurred while starting the service. The samba seems to have trouble finding its way through the db: 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 to

Hi! I upgraded DC2 and DC3, i will upgrade DC1,, but i will wait In DC3 dont correct message... :-| In DC2/DC3 new msg in syslog many messages equal to this in syslog: May 18 11:50:43 DC3 samba: conn[named_pipe] c[unix:] s[unix:/opt/samba/var/run/ncalrpc/np/netlogon] server_id[2157][2157]:   schannel_check_required: [LOJA09A] is not using schannel What this it is ? Regards On

Is there a sensible way for me to manually remove the duplicate SPNs in the mean time? Justin > On Mar 17, 2018, at 3:09 PM, Andrew Bartlett <abartlet at samba.org> wrote: > > On Sat, 2018-03-17 at 07:34 +1300, Andrew Bartlett via samba-technical > wrote: >> On Thu, 2018-03-15 at 16:10 -0400, Justin Foreman wrote: >>> Okay. The master build worked on the join.