1

Until at least Windows 2008R2 it was possible to add multiple NetBIOS names to the same machine, with each additional name resolveable via NetBIOS broadcasts (ie: the classical NetBIOS resolution, not involving DNS). It even was one of the recommended approaches for file server consolidation.

While on Windows Server 2016 you can still adding new NetBIOS names, it seems that the only resolveable name is the first (main) one. For example, taking a server with MAINNAME and ALTNAME as primary and secondary names, only MAINNAME is resolveable via the NetBIOS-specific broadcast method. ALTNAME is resolveable via DNS, and its records are added to the DNS server indeed.

So, I ask:

  • do you know why the default behavior was changed?
  • do you have any suggestions on how to make secondary NetBIOS names resolveable?
shodanshok
  • 44,038
  • 6
  • 98
  • 162
  • 1
    Why are you relying on NetBIOS for name resolution in 2018? – MDMarra Jun 06 '18 at 22:38
  • 1
    Because the server is installed in a domain-less environment. While I am introducing a domain now, this will require some time. In the meantime, I need NetBIOS name resolution to work. – shodanshok Jun 07 '18 at 05:24
  • you can use DNS without being in an Active Directory domain. Nothing in 2018 should require NetBIOS. – MDMarra Jun 12 '18 at 10:56
  • 1
    Yeah, and I did that. However, a legacy MS Access application tried the NetBIOS resolution first, slowing down the initial connection. I fixed it, however, this does not explain why and when Microsoft changed the default behavior described in the blog post I linked. Thanks anyway. – shodanshok Jun 12 '18 at 11:18

0 Answers0