From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0551_01C75A9E.2C83B470
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Now you are trying to read more into what symantec wrote.  If you =
want to express your own opinions, go ahead.  I don't see the point as I =
remember them.  Don't try to attribute this to others though.

   The best way to change your system config is to first understand what =
it is you are changing.  I do not believe you are qualified to recognize =
when you have broken something.

Rich

  "Geo."  wrote in message =
news:45e4e663$1{at}w3.nls.net...
  The first sentence is complete, the second merely gives a few obvious=20
  examples. While windows may not have the obvious examples it has =
plenty,=20
  PLENTY of services that are not critical. But lets not get into that=20
  argument, ftp can be critical to a web server for example so it's =
completely=20
  subjective as to what is or isn't critical.

  (examples of non-critical the dns client, function discovery, infrared =

  monitor, ssdp, etc)

  As for your "breaking the system" comment. The best way to find out if =
a=20
  service is critical or not is to manually stop it and see if anything=20
  breaks, if nothing you need breaks then I guess it's not critical huh?

  Geo.

  "Rich"  wrote in message news:45e465c1$1{at}w3.nls.net...
     The three examples are not enabled by default on any Windows client =
OS.=20
  For Windows Server OS releases I don't believe these three were ever =
enabled=20
  by default but my memory is fuzzy for Windows 2000.  Windows Server =
2003 did=20
  not and Windows NT 4.0 and earlier didn't include these features in =
the base=20
  product.

     What you do is randomly disable services which you don't even =
understand.=20
  You have broken your system with your flailing.

  Rich

    "Geo."  wrote in message news:45e45c00{at}w3.nls.net...
    Oh and one for Rich:

    Recommendations
    Symantec Security Response encourages all users and administrators =
to=20
  adhere
    to the following basic security "best practices":

    Turn off and remove unneeded services. By default, many operating =
systems
    install auxiliary services that are not critical, such as an FTP =
server,
    telnet, and a Web server. These services are avenues of attack. If =
they=20
  are
    removed, blended threats have less avenues of attack and you have =
fewer
    services to maintain through patch updates.

    So remember this Rich when you start complaining about me shutting =
down=20
  all
    those extra services in Vista...

    Geo.


------=_NextPart_000_0551_01C75A9E.2C83B470
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Now you
are trying to read =
more into=20
what symantec wrote.  If you want to express your own opinions,
go=20 ahead.  I don't see the point as I remember them. 
Don't try = to=20
attribute this to others though.
 
   The best
way to change =
your system=20
config is to first understand what it is you are changing.  I do = not=20
believe you are qualified to recognize when you have broken=20
something.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:45e4e663$1{at}w3.nls.net...The=20
  first sentence is complete, the second merely gives a few obvious=20
  examples. While windows may not have the obvious examples it has =
plenty,=20
  PLENTY of services that are not critical. But lets not get into =
that=20
  argument, ftp can be critical to a web server for example so it's=20
  completely subjective as to what is or isn't =
critical.(examples of=20
  non-critical the dns client, function discovery, infrared monitor, =
ssdp,=20
  etc)As for your "breaking the system"
comment. The best way to =
find=20
  out if a service is critical or not is to manually stop it and see =
if=20
  anything breaks, if nothing you need breaks then I guess it's not =
critical=20
  huh?Geo."Rich"
<{at}> wrote in message news:45e465c1$1{at}w3.nls.net...=
  =20
  The three examples are not enabled by default on any Windows client =
OS.=20
  For Windows Server OS releases I don't believe these three were =
ever=20
  enabled by default but my memory is fuzzy for Windows 2000.  =
Windows=20
  Server 2003 did not and Windows NT 4.0 and earlier didn't include =
these=20
  features in the base
product.   What you do is =
randomly=20
  disable services which you don't even understand. You have broken =
your=20
  system with your
flailing.Rich 
"Geo." <geo{at}nls.net>">mailto:geo{at}nls.net">geo{at}nls.net>
wrote in message news:45e45c00{at}w3.nls.net...&nbs=
p; Oh=20
  and one for Rich: 
Recommendations  Symantec =
Security=20
  Response encourages all users and administrators to =
adhere  to=20
  the following basic security "best
practices":  Turn off =
and=20
  remove unneeded services. By default, many operating systems  =
install=20
  auxiliary services that are not critical, such as an FTP =
server, =20
  telnet, and a Web server. These services are avenues of attack. If =
they=20
  are  removed, blended threats have less
avenues of attack =
and you=20
  have fewer  services to maintain through patch =
updates. =20
  So remember this Rich when you start complaining about me shutting =
down=20
  all  those extra services in
Vista... =20
Geo.

------=_NextPart_000_0551_01C75A9E.2C83B470--

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