From: "Geo." 

Picture running WINS on a network where there is no DHCP and every machine
has 200 IP addresses assigned to it.  That's a webfarm..

Geo.

"Rich"  wrote in message news:3eb9a60f{at}w3.nls.net...
   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\nullsessi
  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.

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