It's been more than 4 weeks and no patch yet from ClearOS. I'm thinking this is not going to happen. We will probably move to Uninvention or Nethserver at some point, might be soon if we can't find a solution to the samba issue.

The patch is a few lines to change in two files then samba needs recompiling

Got the patch. Can it be safely applied to mainstream CentOS 'samba-4.10.16-24.el7_9.x86_64.rpm' and then that installed? If not how would we get source rmp for samba samba-4.10.16 ClearOS 7.9 runs?

Heard back from support. Was told:

We plan on having a fix for the issue, but until then we recommend uninstalling the problematic update within Windows.

If support were to suggest to you to remove KB5028166 without any expectation of fixing samba, then I would say it was irresponsible but then you are between a rock and a hard place.

That's what I was told by ClearOS support. Got back to them saying this is not good enough...Will post their reply once I get it.

Sorry to say, the permanent fix is changing to an OS that still gets updates. Zentyal and Univention don't have this issue.

We have a Business subscription so expect this resolved - we pay for verified updates.
Why would we pay them if it's not resolved? That would mean migrating what we have to other providers.

There are 2 threads to monitor:



Title

Fast fix: It's the KB5028166 Microsoft Update. Uninstall!

Thanks, clients can login after uninstalling it.

Will update this post if find a potential long term solution. Please post if you have something that will work long-term.

W11 domain - trust relationship failed

Hi

Suddenly a lot of our W11 clients can't login to samba domain on ClearOs7.

The message displayed is "Trust relationship failed...". Removing / readding to domain doesn't help - we can re-add but after re-adding the msg displayed is still "Trust relationship failed...".

Our standard reg file for W11 clients is:

Windows Registry Editor Version 5.00




The culprit might be one of latest W11 updates as everything was fine for years.

Any help will be greatly appreciated.

We uninstalled it as it wasn't used.

Is enp7s0 mentioned in /etc/clearos/multiwan.conf? If so, please remove it.

It was - we removed all entries mentioning enp7s0.

I don't like the message log either. Perhaps a full restart is in order.

Full restarted helped - DHCP and internet are working on our new HotLAN

We can ping 192.168.25.1 (HotLAN gatewa). We can also ping 192.168.2.1 (main LAN gateway) which is a bit strange. Our local domain is not visible from a client connected to HotLAN though.

Output of '/etc/dnsmasq.conf':



In '/etc/dnsmasq.d' folder we have 2 files:
- 'app-adamone.conf' which is empty
- 'dhcp.conf' which contains:


Output of 'tcpdump -nni enp7s0 portrange 67-68' when client PC unsuccessfully tried to obtain a lease from DHCP:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp7s0, link-type EN10MB (Ethernet), capture size 262144 bytes
16:22:51.588666 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
16:22:55.124773 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
16:23:00.136082 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
16:23:08.883978 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
16:23:25.839126 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
16:23:58.210216 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
16:24:03.047948 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
16:24:10.554854 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
16:24:26.462497 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
^C
9 packets captured
9 packets received by filter
0 packets dropped by kernel

'var/log/messages' filtered by 'enp7s0' contains plenty of: