From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0904_01C314BF.411C7940
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Or use WINS and/or DNS and don't distribute anything.

Rich

  "Geo."  wrote in message =
news:3eb999ce$1{at}w3.nls.net...
  "Rich"  wrote in message news:3eb7e7c0$1{at}w3.nls.net...
  >>   Why?  WINS is fully dynamic.  Manually editing and distributing =
LMHOSTS
  is crazy.

  # Specifying "#INCLUDE " will force the RFC NetBIOS (NBT)
  # software to seek the specified  and parse it as if it were
  # local.  is generally a UNC-based name, allowing a
  # centralized lmhosts file to be maintained on a server.
  # It is ALWAYS necessary to provide a mapping for the IP address of =
the
  # server prior to the #INCLUDE. This mapping must use the #PRE =
directive.
  # In addtion the share "public" in the example below must be in the
  # LanManServer list of "NullSessionShares" in order for client =
machines to
  # be able to read the lmhosts file successfully. This key is under
  #
  =
\machine\system\currentcontrolset\services\lanmanserver\parameters\nullse=
ssi
  onshares
  # in the registry. Simply add "public" to the list found there.
  #
  # The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
  # statements to be grouped together. Any single successful include
  # will cause the group to succeed.

  Nothing crazy about it, any web hosting outfit is probably using =
static IP
  for all their servers. You need the include and one entry for the =
server
  holding the included lmhosts file and your all set. All you do then is
  maintain one lmhosts file which is distributed automagically.

  Geo.


------=_NextPart_000_0904_01C314BF.411C7940
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Or use
WINS and/or DNS and =
don't=20
distribute anything.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:3eb999ce$1{at}w3.nls.net..."Rich"=20
  <{at}> wrote in message news:3eb7e7c0$1{at}w3.nls.net...=
>>  =20
  Why?  WINS is fully dynamic.  Manually editing and =
distributing=20
  LMHOSTSis crazy.# Specifying "#INCLUDE
<filename>" =
will=20
  force the RFC NetBIOS (NBT)# software to seek the specified=20
  <filename> and parse it as if it were# local. =
<filename> is=20
  generally a UNC-based name, allowing a# centralized lmhosts file =
to be=20
  maintained on a server.# It is ALWAYS necessary to provide a =
mapping for=20
  the IP address of the# server prior to the #INCLUDE. This mapping =
must use=20
  the #PRE directive.# In addtion the share "public" in
the example =
below=20
  must be in the# LanManServer list of
"NullSessionShares" in order =
for=20
  client machines to# be able to read the lmhosts file successfully. =
This=20
  key is=20
  =
under#\machine\system\currentcontrolset\services\lanmanserver\par=
ameters\nullsessionshares#=20
  in the registry. Simply add "public" to the list found =
there.## The=20
  #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE# =
statements to=20
  be grouped together. Any single successful include# will cause the =
group=20
  to succeed.Nothing crazy about it, any web hosting outfit is =
probably=20
  using static IPfor all their servers. You need the include and one =
entry=20
  for the serverholding the included lmhosts file and your all set. =
All you=20
  do then ismaintain one lmhosts file which is distributed=20
 
automagically.Geo.

------=_NextPart_000_0904_01C314BF.411C7940--

--- BBBS/NT v4.01 Flag-4