samba - Nov 2022 - accidentally upgraded DC to 4.17.3 ... didn't work

Am 24.11.22 um 17:17 schrieb Stefan G. Weichinger via samba:
> maybe I should demote adc1 again, then check for spn and remove, if it 
> exists, then rejoin ... ?
after some other things ...

currently the spns look good

dbcheck ok on both DCs

drs showrepl good on both DCs  ...

logs quite quiet (no obvious errors)

But still that winbind-issue on adc1

I can't tell how much of a problem that is for a DC right now. To me it 
seems that no clients connect to adc1 ... but maybe I am wrong.

After a day of fiddling I let it as it is and look forward to some 
helpful hint .. thanks all.

Good morning (here)

Replication still seems to work

All three winbind-child-processes are there, although stuff like 
"winbind -t" still fail on that adc1 DC.

It *seems* that windows PCs talk successfully to that DC but I am not 
100% sure if things are really OK.

Because for example I can't access \\adc1\sysvol

# smbclient -L localhost

SPNEGO login failed: The object was not found

# adc1 ... log.smbd

auth_check_password_recv: sam authentication for user 
[\administrator at ARBEITSGRUPPE.MY.TLD] FAILED with error NT_STATUS_NOT_FOUND

# wbinfo -i administrator
failed to call wbcGetpwnam: WBC_ERR_WINBIND_NOT_AVAILABLE
Could not get info for user administrator

-

So far the PCs seem to not notice, but I think I shouldn't let it that 
way longer than necessary.

I appreciate any help on this.