Specifications

Chapter #5 - O/S 2.0 - Network Configuration 143 000001628
MaxAttach NAS 6000 Administration Guide
Chapter #5 - O/S 2.0 - Network Configuration
NetBIOS LMHOSTS File
11/07/01 -- Revision 2.0.03A
The following example below shows how these keywords are used.
102.54.94.98 localsrv #PRE
102.54.94.97 trey #PRE #DOM:networking #net group's PDC
102.54.94.102 "appname......\0x14" #special app server
102.54.94.123 popular #PRE #source server
#BEGIN_ALTERNATE
#INCLUDE \\localsrv\public\LMHOSTS #adds LMHOSTS files from this server
#INCLUDE \\trey\public\LMHOSTS #adds LMHOSTS files from this server
#END_ALTERNATE
Note the following points from the example above:
n The servers named localsrv and trey are preloaded so they can be used later in an
#INCLUDE statement in a centrally maintained LMHOSTS file.
n The server named "appname \0x14" contains a special character after the 15th
character, including blanks, in its name, so its name is enclosed in quotation marks.
n The server named popular is preloaded, based on the #PRE keyword.
Guidelines for LMHOSTS Files
When you use a host table file, be sure to keep it up-to-date and organized. Use the
following guidelines:
n Update the LMHOSTS file whenever a computer is changed or removed from the
network.
n Use #PRE statements to preload popular entries into the local computer's name cache.
Also use
#PRE statements to preload servers that are included with #INCLUDE
statements.
n Because LMHOSTS files are searched from the beginning one line at a time, you can
increase the search speed for the most commonly-used entries by placing statements for
the most frequently-used servers near the top of the file. Follow these with statements
for less frequently-used servers, and then follow these server statements with remote
#INCLUDE statements. Type the #PRE entries at the end of the file because these
#END_ALTERNATE Marks the end of an #INCLUDE grouping.
\0xnn Supports nonprinting characters in NetBIOS names. Enclose the NetBIOS name in quotation
marks and use \0xnn hexadecimal notation to specify a hexadecimal value for the character. This
allows custom applications that use special names to function properly in routed topologies.
However, LAN Manager TCP/IP does not recognize the hexadecimal format, so you surrender
backward compatibility if you use this feature.
Notice that the hexadecimal notation applies only to one character in the name. The name should
be padded with blanks so the special character is placed as the last, or 16th, character in the
string).
Table #1 - LMHOSTS Keywords and Definition
LMHOST
Keywords
Keyword Definitions