samba - Apr 2020 - NBT name resolution

For many years now I have been using smbclient to copy nightly backups
of my server to a Windows server.  This is no longer working because the
name resolution fails.  It appears that MS, in their infinite wisdom, no
longer are using NBT name resolution.  How am I supposed to resolve the
server's IP address now?  My first thought was using nslookup to use the
Windows DC as the name server and querying that way, but that does not
seem to work either.

On Wed, Apr 8, 2020 at 2:56 PM Phillip Susi via samba <samba at
lists.samba.org>
wrote:
> How am I supposed to resolve the server's IP address now?
>
Netbios has been effectively replaced by DNS for a long time now. It sounds
like you don't have a properly functioning DNS in your environment. I would
start there.

Jonathon Reinhart via samba writes:
> Netbios has been effectively replaced by DNS for a long time now. It sounds
> like you don't have a properly functioning DNS in your environment. I
would
> start there.
I had my own perfectly functioning dns server using 8.8.8.8 as the
upstream.  Aparently I now have to use the Windows DC as the DNS server
to resolve windows host names.  I guess NetBIOS made life too easy so it
had to be disabled a few months ago.

( man smb.conf )
      dns proxy (G)

           Specifies that nmbd(8) when acting as a WINS server and finding
           that a NetBIOS name has not been registered, should treat the
           NetBIOS name word-for-word as a DNS name and do a lookup with the
           DNS server for that name on behalf of the name-querying client.

           Note that the maximum length for a NetBIOS name is 15 characters,
           so the DNS name (or DNS alias) can likewise only be 15 characters,
           maximum.

           nmbd spawns a second copy of itself to do the DNS name lookup
           requests, as doing a name lookup is a blocking action.

           Default: dns proxy = yes

And that works fine since i use it also. 
And/or add one server that runs as member and has nmbd enabled. 

Should work if dns, primary domain and search domains are setup correcty. 
Besides that, you also did take NTLM, NTLMv2 or Kerberos changes in account
also?


> -----Oorspronkelijk bericht-----
> 
> I had my own perfectly functioning dns server using 8.8.8.8 as the
> upstream.  Aparently I now have to use the Windows DC as the 
> DNS server
> to resolve windows host names.  I guess NetBIOS made life too 
> easy so it had to be disabled a few months ago.
> 
So, setup AD-DC, integrate the DNS and use it, or forward it to an other DNS.
1000 ways to Rome ;-) 

Greetz, 

Louis