From: "Geo." 

The first sentence is complete, the second merely gives a few obvious
examples. While windows may not have the obvious examples it has plenty,
PLENTY of services that are not critical. But lets not get into that
argument, ftp can be critical to a web server for example so it's
completely 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 service is critical or not is to manually stop it and see if
anything 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.
For Windows Server OS releases I don't believe these three were ever
enabled by default but my memory is fuzzy for Windows 2000.  Windows Server
2003 did not and Windows NT 4.0 and earlier didn't include these features
in the base product.

   What you do is randomly disable services which you don't even understand.
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
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
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
all
  those extra services in Vista...

  Geo.

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