Dear Maintainer,
I don't know when this has happened but now domain users can't join any
more old NT domain. If I try to join the domain I get the error

# net rpc join -S servercsa -U admin
Enter admin's password:
Failed to join domain: failed to lookup DC info for domain 'DOMINIOCSA' over rpc: The transport connection is now disconnected.

furthermore PC's previously joined to the domain now get the error

# net rpc testjoin
Join to domain 'DOMINIOCSA' is not valid: NT_STATUS_CONNECTION_DISCONNECTED

I know that NT domain is very old and that we have to migrate to AD but
in my opinion if samba has decided to continue support NT old style domain the join to NT style old domain should works.

Hi, I add some more infos to the bug hoping will be useful to shoot the
problem. Using wbinfo command line program in a pc joined to the domain
and dist-upgraded to bullseye I can see that some parameters return
correctly, other doesn't. For example --domain-info option or
--dsgetdcname shows the correct return value but --getdcname doesn't:

$ wbinfo --getdcname DOMINIOCSA
Could not get dc name for DOMINIOCSA

But winbind service seems to be started correctly:

$ systemctl status winbind.service
● winbind.service - Samba Winbind Daemon
      Loaded: loaded (/lib/systemd/system/winbind.service; enabled;
vendor prese>
      Active: active (running) since Wed 2020-01-08 08:41:40 CET; 20min ago
        Docs: man:winbindd(8)
man:samba(7)
man:smb.conf(5)
    Main PID: 494 (winbindd)
      Status: "winbindd: ready to serve connections..."
       Tasks: 5 (limit: 1144)
      Memory: 16.3M
      CGroup: /system.slice/winbind.service
              ├─494 /usr/sbin/winbindd --foreground --no-process-group
              ├─510 winbindd: domain child [DEBIAN64BIT]
              ├─511 winbindd: idmap child
              ├─512 winbindd: domain child [BUILTIN]
              └─553 /usr/sbin/winbindd --foreground --no-process-group

I'm a little bit confused...

Have a great year

Piviul

Not a bug, try

wbinfo --getdcname=internal.domain.tld
Then it queries the hostname within the AD domain.
And not the NETBIOS domain name.

Wbinfo --help show it really..

 Hello,
Will you be Interested in a PARTNERSHIP DEAL? Let me know for full details.
Peter Owen