samba - Oct 2022 - Upgrade Woes

Dear All,

After ages of enjoying samba-4.12.9 on CentOS7, I've had to upgrade to 4.17
to fix a Windows 11 22H2 issue that stopped authentication.

I read all the change logs before and didn't see anything that would affect
me, but now my Windows clients (both 10 and 11) cannot 'browse' the
samba servers or map printers.
>From the Windows clients, I can use the cmd line to attach successfully to
all the file shares like this:
net use \\DC2\IPC$
net use * \\DC2\netlogon

However, if I try to browse ('start \\dc2') or add a printer:
rundll32 printui.dll,PrintUIEntry /in /n"\\DC2\PRINTER"

Then I get a 0x80070035 error from Windows, remarkably quickly back. Same for
using IP addresses.

Name resolution appears to be working - ping is resolving the hostname properly.

I've turned Samba's debug up to 3 and I see this in the log:
[2022/10/18 13:09:15.528808,  3]
../../source3/smbd/smb2_service.c:855(make_connection_snum)
  192.168.9.172 (ipv4:192.168.9.172:55652) signed connect to service IPC$
initially as user SAMDOM\tim.odriscoll (uid=2000, gid=100) (pid 28736)
[2022/10/18 13:09:15.536804,  3]
../../source4/samba/service_stream.c:67(stream_terminate_connection)
  stream_terminate_connection: Terminating connection - 'dcesrv:
NT_STATUS_CONNECTION_DISCONNECTED'
[2022/10/18 13:09:15.610423,  3]
../../source3/smbd/smb2_server.c:3956(smbd_smb2_request_error_ex)
  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1]
status[NT_STATUS_CONNECTION_DISCONNECTED] || at
../../source3/smbd/smb2_create.c:339

But I can't find out what "smbd_smb2_request_error_ex: idx[1]"
means or how to fix it, or even if that is the actual source of the problem.

Can anyone offer some advice on where to look next?

Many thanks,
Tim

Hi All,

I've tried using a minimal smb.conf from a working DC1 on my problematic DC2
and the issue is still there - I'm not able to?browse any shares like the
default sysvol and netlogon via Explorer in Windows, only via the command line.

The error is still '0x80070035 the network path was not found'.

So, if the issue isn't in my smb.conf which could have different
requirements after the update, where would the issue be? In the AD database?

I wonder if removing the DC from the domain and re-joining it would work, or
would that mess something else up? But surely that won't fix it if it was
working before the update, meaning the AD was OK?

Hmmm..
Tim