Windows 10: Netbios and resolving local DNS names

I am having a couple issues with one of my Windows 10 PCs (Windows 10 Pro 64 ver 1909) that appeared after I replaced my LAN's router (replaced D-Link DIR-885L with a TP-Link AX6000).

Issue #1) Registry entry hklm\system\currentcontrolset\services\netbt\parameters\interfaces\tcpip_{xxx] netbiosoptions data doesn't change when I change an adapter's (wired or wifi) Tcpv4 WINs netbios options (auto, on, off). The option for the entry should change from (0=auto, 1=0n, and 2=off) to one of the other options when I change the adapter's properties. All entries remain at 0 (auto), but in the adapter's status/details window it shows no mater what option I select:
Connection-specific DNS Suffix:
Description: Intel(R) Gigabit CT Desktop Adapter
Physical Address:xx-xx....
DHCP Enabled: Yes
IPv4 Address: 192.168.x.x
IPv4 Subnet Mask: 255.255.255.0
Lease Obtained: Sunday, May 3, 2020 4:20:07 AM
Lease Expires: Wednesday, June 9, 2156 4:31:28 PM
IPv4 Default Gateway: 192.168.x.x
IPv4 DHCP Server: 192.168.x.x
IPv4 DNS Servers: 1.1.1.1, 1.0.0.1
IPv4 WINS Server:
***NetBIOS over Tcpip Enabled: No***
Link-local IPv6 Address: xx...
IPv6 Default Gateway:
IPv6 DNS Server:

I have confirmed that the data entry ought to change by changing the parameters on my other Windows 10 PCs.

Anyone have any ideas on where to look? Do I even need netbios anymore (some websites I've found say to disable it on all adapters)?

Issue #2) (Same Windows 10 Pro 64 PC) The PC wouldn't/couldn't translate the routers share host name (\\TP=Share) to the routers ip address when trying to connect to router attached Networked hard-drive (all other PCs had no problem connecting using the host name). I could enter \\(ipaddress) and the PC would connect to the share immediately. The PC is having no problem resolving hostnames of the other PC on the network.

My work around was the manually add the ip address and host name to the Hosts file.

Any ideas on where to look to solve this one?

Are these two issues possibly related to a common problem?

:)

 

Windows 10 local DNS names intermittently not resolving

Ever since I upgraded my Windows 7 Pro machine to Windows 10 Pro, I have intermittent issues resolving local DNS names. I've checked my primary and secondary DNS servers and the logs don't show any issues that would point to a potential issue on the server
side. I can ping IP addresses with no problem and internet names are resolving normally, but the local DNS names won't resolve. I end up having to run 'ipconfig /flushdns' to get local DNS to resolve correctly. Is my local DNS cache resolver data becoming
corrupted? What could be causing this? Any ideas?

 

NAS looses DNS name

Welcome to the forum locally DNS isn't used it's NetBIOS how many PCs on the network they look to the PC that is Master browser for the resolution of the name so it's not updating fast enough

 

Local DNS server is not resolving names when machine is connected to VPN

I'm trying to set up a small VPN Network using OpenVPN which will allow me to connect to my workstation in the office from home.

I've already set up OpenVPN server, generated keys and client config files.
Everything works I can connect to my work machine in the office from home via RDP but there is one issue - DNS names for local resources cannot be resolved when work PC is connected to my VPN:

I've add our local DNS server to client config file and also added a static route for that, it doesn't work. Here are the current settings on the client:

Client PC OS: Windows 10

client_config.ovpn:

ipconfig /all on the client:

Local DNS server is available via ping:

Static route to it is also working fine judging by tracert:

What am I missing?