On Mon, 2021-10-18 at 11:45 +0200, Gerd Peter via samba wrote:> HI, > If I can help to find the Problem and the reason ... > We have the same Problem: > fresh new debian bullseye Installation > L.P.H. van Belle Repositories bullseye-samba415 main > DNS is bind; every DNS test is working well, on the DC and on the > Windows Systems; signed chrony Timeserver; > > Windows Server 20219 and Windows 10 same result: > No Problem to join the Domain - after the first reboot - > authenticate tells then that the username or password is wrong > > C:\Windows\system32>nltest /dsgetdc:exampledomain.net - give the > right > answer. > > If I can make some further tests ... > regards, > gerd peterOK, a user 'Ingo Asche' has been git-bisecting the code to find where the problem started. he has found that it appears to be this commit: commit 997fbcbc902d945eb5261ddc6667f830fbcd5931 (HEAD) 4.15.0pre1-GIT-997fbcbc902 Which now has the devs scratching their heads because it only added one line and they cannot see why it would cause this problem. They are looking into it, so we mere mortals must just wait :-) Rowland
thanks for the answer, is it a working solution to downgrade my fresh 4.15 installation to 4.14 (with changing the L.P.H. van Belle Repositories to bullseye-samba414) Or is a new installation the only worthwhile way for production ... regards, gerd peter Am Montag, dem 18.10.2021 um 11:24 +0100 schrieb Rowland Penny via samba:> On Mon, 2021-10-18 at 11:45 +0200, Gerd Peter via samba wrote: > > HI, > > If I can help to find the Problem and the reason ... > > We have the same Problem: > > fresh new debian bullseye Installation > > L.P.H. van Belle Repositories bullseye-samba415 main > > DNS is bind; every DNS test is working well, on the DC and on the > > Windows Systems; signed chrony Timeserver; > > > > Windows Server 20219 and Windows 10 same result: > > No Problem to join the Domain - after the first reboot - > > authenticate tells then that the username or password is wrong > > > > C:\Windows\system32>nltest /dsgetdc:exampledomain.net - give the > > right > > answer. > > > > If I can make some further tests ... > > regards, > > gerd peter > > OK, a user 'Ingo Asche' has been git-bisecting the code to find where > the problem started. he has found that it appears to be this commit: > > commit 997fbcbc902d945eb5261ddc6667f830fbcd5931 (HEAD) > 4.15.0pre1-GIT-997fbcbc902 > > Which now has the devs scratching their heads because it only added one > line and they cannot see why it would cause this problem. > > They are looking into it, so we mere mortals must just wait :-) > > Rowland > > >
Wait for 4.15.1 coming soon that bug in .0 is found. I suggest for now stay on 4.14. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Gerd > Peter via samba > Verzonden: vrijdag 22 oktober 2021 16:41 > Aan: Rowland Penny; samba at lists.samba.org > Onderwerp: Re: [Samba] Problem after update version 4.15.0 > > thanks for the answer, > > is it a working solution to downgrade my fresh 4.15 > installation to 4.14 > (with changing the L.P.H. van Belle Repositories to bullseye-samba414) > Or is a new installation the only worthwhile way for production ... > regards, > gerd peter > > Am Montag, dem 18.10.2021 um 11:24 +0100 schrieb Rowland > Penny via samba: > > On Mon, 2021-10-18 at 11:45 +0200, Gerd Peter via samba wrote: > > > HI, > > > If I can help to find the Problem and the reason ... > > > We have the same Problem: > > > fresh new debian bullseye Installation > > > L.P.H. van Belle Repositories bullseye-samba415 main > > > DNS is bind; every DNS test is working well, on the DC and on the > > > Windows Systems; signed chrony Timeserver; > > > > > > Windows Server 20219 and Windows 10 same result: > > > No Problem to join the Domain - after the first reboot - > > > authenticate tells then that the username or password is wrong > > > > > > C:\Windows\system32>nltest /dsgetdc:exampledomain.net - give the > > > right > > > answer. > > > > > > If I can make some further tests ... > > > regards, > > > gerd peter > > > > OK, a user 'Ingo Asche' has been git-bisecting the code to > find where > > the problem started. he has found that it appears to be this commit: > > > > commit 997fbcbc902d945eb5261ddc6667f830fbcd5931 (HEAD) > > 4.15.0pre1-GIT-997fbcbc902 > > > > Which now has the devs scratching their heads because it > only added one > > line and they cannot see why it would cause this problem. > > > > They are looking into it, so we mere mortals must just wait :-) > > > > Rowland > > > > > > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > >
oh Hi Louis, first: Thank you for your Work, that's great! (OT: and greeting to Stefan K. whose book is right next to me ;-) since I work with Proxmox, I take a snapshot and try both: one in reserve for the update to 4.15.1, one for test purposes for the downgreate to 4.14.. Unless 4.15.1 comes in the next few days ...> L.P.H. van Belle belle at bazuin.nl > Fri Oct 22 14:49:43 UTC 2021 > Wait for 4.15.1 coming soon that bug in .0 is found. > I suggest for now stay on 4.14. > > Greetz, > Louis@Rowland, that's good to hear, I will give it a try regards, gerd> Rowland Penny rpenny at samba.org > Fri Oct 22 15:32:26 UTC 2021 > You should be able to downgrade to 4.14.* and then wait for 4.15.1 > Rowland>>is it a working solution to downgrade my fresh 4.15 installation >> to 4.14 (with changing the L.P.H. van Belle Repositories to >> bullseye-samba414) Or is a new installation the only worthwhile >> way for production ...