2 Windows 10 machines. Machine1 can access \\Server1 via NetBIOS. Machine2 can not. However Machine2 can access \\Server2 via NetBIOS and Machine1 can not. If you use the FQDN it works without issue for both.
Machine1 and Machine2 can ping both Servers via NetBIOS names without issue.
When Machine1 tries to access \\Server2 a credentials box appears. Typing in correct credentials does not do anything. It simply shows the credential box again as seen via this url. https://i.imgur.com/eXb6XB3.png (My rep is not high enough to embed images)
Both machines have listed the same LogonServer which happens to be Server2. Both Machines use DHCP, both Servers use static IPs and all 4 devices are in the same subnet. Both servers are 2008 and are DCs.
This only happens with Windows 10. We have hundreds of Windows 7 machines that work without issue using the same user accounts.
The most annoying thing however is it is not constant. Machine1 will randomly after no changes have no issues using NetBIOS to access Server2. But will then also stop for no reason later.
We are in the process of building a Win10 SOE however this obviously is holding that back.
Best Answer
NetBios is a seriously legacy protocol and should not be used anywhere that has DNS implemented; everything should be using FQDN. Microsoft has been deprecating NetBT in Windows 10 / Server 2016 ever so slowly and eventually it will be outright removed.
To address your symptoms, you can append custom DNS suffixes in your IP properties for your NIC. Add each of your DNS names in the list and it will automatically append them to the server name and attempt DNS resolution. For logins, you can switch to using a UPN which looks like an email address.