For the people still using Clearos. And use it as a domain server.
KB5028166 breaks the trust in your domain.
I believe the last samba update was 5 years ago you need Samba 4.16 or higher to have an updated windows 10 or 11 client.
COS is stuck at 4.10.16 (now 3 years old) I believe. And you can't update any further without breaking the rest.
If someone has a better idea, then to remove the update, I am happy to learn.
KB5028166 breaks the trust in your domain.
I believe the last samba update was 5 years ago you need Samba 4.16 or higher to have an updated windows 10 or 11 client.
COS is stuck at 4.10.16 (now 3 years old) I believe. And you can't update any further without breaking the rest.
If someone has a better idea, then to remove the update, I am happy to learn.
Share this post:
Responses (4)
-
Accepted Answer
Hi Theodosios,
you are my personal hero and the rescuer of all the ClearOS users
I've added your repository and did the "yum reinstall ..." you've mentioned.
But it seems, I had installed samba samba-4.10.16-17, which is not in your repo.
Because then it still didn't work, additonally I did a "yum upgrade" and did all available upgrades.
After that, the problem was solved.
All my Win10/11 clients with all updates installed can now logon again to the domain ! Yeah
Thank you very, very much !
PS:
The dashboard still displays samba version 3.5.9
A "smbd -V" on the console shows "Version 4.10.16"
The yum log shows "samba-4.10.16-19.el7_9.x86_64" -
Accepted Answer
Hello everyone
I made some test repos with the following samba version with patch from https://bugzilla.redhat.com/show_bug.cgi?id=2222250
samba-4.10.16-19
samba-4.10.16-20
samba-4.10.16-14
I made some test on my test Server and seems that works fine with Windows 10 and KB5028166.
cat >/etc/yum.repos.d/clearos-samba-test.repo <<EOL
[ClearOS-samba-4.10.16-19]
name=ClearOs-samba-4.10.16-24
baseurl=https://repos.click2c.eu/samba-4.10.16-19-RPMS
enabled=1
gpgcheck=0
priority = 1
[ClearOS-samba-4.10.16-20]
name=ClearOs-samba-4.10.16-24
baseurl=https://repos.click2c.eu/samba-4.10.16-20-RPMS
enabled=0
gpgcheck=0
priority = 1
[ClearOS-samba-4.10.16-24]
name=ClearOs-samba-4.10.16-24
baseurl=https://repos.click2c.eu/samba-4.10.16-24-RPMS
enabled=0
gpgcheck=0
priority = 1
EOL
yum reinstall libsmbclient libwbclient samba amba-client samba-client-libs samba-common samba-common-libs samba-common-tools samba-libs samba-winbind samba-winbind-clients samba-winbind-modules
or yum upgrade if you enable version repo over 4.10.16-19 -
Accepted Answer
This link https://sfj48-fkj200.heiksthsd.cf/clearfoundation/social/community/migrate-samba4-dc-to-samba-directory#reply-158701 rooftop snipers is my case for classicupgrade. Thank you. -
Accepted Answer
Thanks for the heads-up, this was very helpful last week.
I don't have a better solution than removing the update (and pausing updates) on the Windows side.
However, since the problem is mostly with NT4-style domains, upgrading to Active Directory-style may work in most cases:
https://sfj48-fkj200.heiksthsd.cf/clearfoundation/social/community/migrate-samba4-dc-to-samba-directory#reply-158701
https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade)
Except for RDP using network-level authentication per:
https://www.reddit.com/r/sysadmin/comments/14xmkw6/for_people_using_samba_and_windows_10_latest/
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »