6 Appendix A: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Windows NT operating system

  • Windows 2000 operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

  • Windows Vista operating system

  • Windows Server 2008 operating system

  • Windows 7 operating system

  • Windows Server 2008 R2 operating system

  • Windows 8 operating system

  • Windows Server 2012 operating system

  • Windows 8.1 operating system

  • Windows Server 2012 R2 operating system

  • Windows 10 operating system

  • Windows Server 2016 operating system

  • Windows Server operating system

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 1.8: Unless a protocol using the recommended convention specifies otherwise, Windows protocols use the machine system code page for NetBIOS names; this means that two computers with different code pages cannot interoperate by using such a protocol with anything other than ASCII names.

<2> Section 1.8: Some commonly used NetBIOS suffix values are given in [MSKB-163409].

<3> Section 2.2.1: Windows 2000, Windows XP, and Windows Server 2003 allow the SMB protocol to add the name "*SMBSERVER" to the Local Name Table.

<4> Section 2.2.3: On Windows, this file is in the systemroot\System32\Drivers\Etc folder.

<5> Section 3.1.1: In Windows NT, Windows 2000, Windows XP, and Windows Server 2003, the default setting is TRUE.

<6> Section 3.1.3: When a DHCP option is received, Windows stores the value in its Node Type, so that the most recent one received is the one used for subsequent operations.

<7> Section 3.1.3: On Windows, except Windows NT, Windows 2000, Windows XP, and Windows Server 2003 the read is from the registry using HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\ReadLMHostsFile if the key exists. A value of 1 means ReadLMHostsFile will be set to TRUE. If the key is not present in the registry the value of ReadLMHostsFile does not change.

<8> Section 3.1.3: On Windows because no user name is associated with the computer during startup, NBT uses a null user name for its credentials when accessing the shared folder where the central LMHOSTS file is located.

<9> Section 3.1.3: To allow null access to a shared folder that contains an LMHOSTS file on a Windows machine, the name of the folder can be set to the registry value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\Lanmanserver \Parameters\NullSessionShares.

<10> Section If the last byte of the group name is not 0x1C, Windows follows the RFC behavior of replacing addresses. For group names with the last byte equal to 0x1C, Windows appends addresses. For any group names except those with a last byte of 0x1C, Windows returns in response to queries as if it had stored