Displaying 4 results from an estimated 4 matches for "526d14a585a1".
2025 Feb 04
1
Windows 11 24H2, Samba 4.21.3 AD DC and domain users cannot log in
...re investigation, that might be the same 'fix' I pointed
> to earlier, but from a different direction.
>
> So I dug deeper and found this:
>
> https://answers.microsoft.com/en-us/windowsclient/forum/all/after-update-to-latest-win-11-24h2-rdp-kerberos/d0f95e77-eb25-4604-bfd7-526d14a585a1?page=3
>
> Which appears to be a lot closer to what the problem the OP is getting.
> If it is, then it appears to be a Windows bug that they are not
> accepting.
>
I'll check this also. Changing allowed kerberos algorihms had no effect.
Although for me fully updated 23H2 is...
2025 Feb 04
1
Windows 11 24H2, Samba 4.21.3 AD DC and domain users cannot log in
...t;
>
After a bit more investigation, that might be the same 'fix' I pointed
to earlier, but from a different direction.
So I dug deeper and found this:
https://answers.microsoft.com/en-us/windowsclient/forum/all/after-update-to-latest-win-11-24h2-rdp-kerberos/d0f95e77-eb25-4604-bfd7-526d14a585a1?page=3
Which appears to be a lot closer to what the problem the OP is getting.
If it is, then it appears to be a Windows bug that they are not
accepting.
Rowland
2025 Feb 05
1
Windows 11 24H2, Samba 4.21.3 AD DC and domain users cannot log in
...ght be the same 'fix' I
> > pointed to earlier, but from a different direction.
> >
> > So I dug deeper and found this:
> >
> > https://answers.microsoft.com/en-us/windowsclient/forum/all/after-update-to-latest-win-11-24h2-rdp-kerberos/d0f95e77-eb25-4604-bfd7-526d14a585a1?page=3
> >
> > Which appears to be a lot closer to what the problem the OP is
> > getting. If it is, then it appears to be a Windows bug that they
> > are not accepting.
> >
>
> I'll check this also. Changing allowed kerberos algorihms had
> no effect....
2025 Feb 04
1
Windows 11 24H2, Samba 4.21.3 AD DC and domain users cannot log in
On Tue, 4 Feb 2025 15:07:30 +0200
Virgo P?rna via samba <samba at lists.samba.org> wrote:
> And there has been some developement...
>
> test-computersecurechannel
> still reports True.
> But now
> test-computersecurechannel -repair
> now fails with
> "Test-ComputerSecureChannel: Cannot reset the secure channel password
> for the computer account in the