From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0B4D_01C3158E.553A9DB0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Why is that a problem?  The number of IP addresses is irrelevant.  I =
wouldn't use NetBIOS on the Internet facing systems anyway.  DNS should =
work just fine.  For something other than a web farm, whether a small =
office or a large enterprise like Microsoft with tens of thousands of =
desktops, DHCP and DDNS and/or WINS is much less hassle.

Rich

  "Geo."  wrote in message =
news:3ebafc4c$1{at}w3.nls.net...
  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\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_0B4D_01C3158E.553A9DB0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Why is that a =
problem?  The=20
number of IP addresses is irrelevant.  I wouldn't use NetBIOS on = the=20
Internet facing systems anyway.  DNS should work just
fine.  = For=20
something other than a web farm, whether a small office or a large = enterprise=20
like Microsoft with tens of thousands of desktops, DHCP and DDNS and/or = WINS is=20
much less hassle.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:3ebafc4c$1{at}w3.nls.net...Picture=20
  running WINS on a network where there is no DHCP and every =
machinehas 200=20
  IP addresses assigned to it. <g> That's a=20
  webfarm..Geo."Rich"
<{at}> wrote in message news:3eb9a60f{at}w3.nls.net...&nbs=
p; =20
  Or use WINS and/or DNS and don't distribute=20
  anything.Rich 
"Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote in =
message news:3eb999ce$1{at}w3.nls.net...=
 =20
  "Rich" <{at}> wrote in message news:3eb7e7c0$1{at}w3.nls.net...=
 =20
  >>   Why?  WINS is fully
dynamic.  Manually =
editing=20
  and distributingLMHOSTS  is
crazy.  # =
Specifying=20
  "#INCLUDE <filename>" will force the RFC NetBIOS
(NBT)  =
#=20
  software to seek the specified <filename> and parse it as if it=20
  were  # local. <filename> is generally a
UNC-based =
name,=20
  allowing a  # centralized lmhosts file to be maintained on a=20
  server.  # It is ALWAYS necessary to provide a mapping for =
the IP=20
  address of the  # server prior to the #INCLUDE. This mapping =
must use=20
  the #PRE directive.  # In addtion the share
"public" in the =
example=20
  below must be in the  # LanManServer list of =
"NullSessionShares" in=20
  order for client machines to  # be able to read the lmhosts =
file=20
  successfully. This key is under =20
  =
#\machine\system\currentcontrolset\services\lanmanserver\paramete=
rs\nullsessi =20
  onshares  # in the registry. Simply add
"public" to the list =
found=20
  there.  #  # The #BEGIN_ and
#END_ALTERNATE keywords =
allow=20
  multiple #INCLUDE  # statements to be grouped together. Any =
single=20
  successful include  # will cause the group to =
succeed. =20
  Nothing crazy about it, any web hosting outfit is probably using =
static=20
  IP  for all their servers. You need the include and one entry =
for the=20
  server  holding the included lmhosts file and your all set. =
All you=20
  do then is  maintain one lmhosts file which is distributed=20
  automagically.  =
Geo.

------=_NextPart_000_0B4D_01C3158E.553A9DB0--

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