[Samba] stuck windows machines after last samba ad-dc update?

[Michael Tokarev]

Hi!

We're seeing some very strange behavior of windows machines
(domain members) after updating our samba-based AD to the latest
stable samba version (4.24.7).

I'm not saying this behavior is especially due to samba update,
because windows has been updated at about the same time too, so
the prob can be windows.  However, the problem started happening
closer to samba update than to windows update :)

The symptoms is that one can't login to windows machine and can't
shut it down, can't run taskmgr.exe, and many other tools.

For example,  `shutdown -r -r -t 0` just gets stuck, doing nothing
at all.  One can interrupt it with Ctrl+C, and re-run it - with the
same effect.

When starting taskmgr.exe, it opens an empty window and, after a
while, windows says the application is stuck, offering to terminate
it or wait for longer.

The only way we found to get out of this lockup is to run
notmyfaultc.exe /crash 1 -- this way, it reboots after a BSoD.
Or one can hit the Reset button on the PC.

There's nothing interesting in the eventlog (and windows event
logging service is stuck too when this happens, so no surprise
here).  Attempts to run procmon or something during the freeze
failed too, so far.

We've several different machines here (mostly with windows 10 ltsc),
and so far only one haven't experienced such behavior.  Other
machines had to be force-rebooted this way at least once, some
more than once.

I'll try to downgrade samba to 4.24.6 to see if the problem is
repeatable with that version.

Has anyone seen this too, maybe?

Thanks,

/mjt