Charles L. Phillips said:
Hello,
Is there a standard checklist for checking a Windows 2000 network???
There are probably dozens if not hundreds
of checklists for Windows networking.
Many are formal (you can find them written
down in the KB, the help, or various web sites,
etc.
If there is can someone send it to me...
Many are built right into the help. Search:
[ checklist TOPIC ]
If there is no standard checklist, can someone tell me what I should be
looking for...
What problem do you have?
The most important principles are to be
very SPECIFIC about the problem symptoms
including precise error messages until you
can prove what works and what is broken
and specifically how it is broken.
Phrases like "the network is broken" should
be removed from the troubleshooters vocabulary,
or at least be a RED FLAG for asking "How
specifically?" "What specifically is happening?".
The most simple basic networking it so try to
show ANY connectivity with Ping, both by name
and number -- now we may know whether the
problem is name resolution or basic connectivity
itself.
If ping by IP fails then we try local machines
and remote machines with Tracert to see "how
far" we can get. If we get total failure we try
to find OTHER machines that work.
Notice that most "steps" will be contingent on
the precise results of previous steps so linear
checklist is very counter-productive for many
situations and we will prefer to have a deep
understanding of "how things must work" and
then use that to logically develop "next test"
plans.
will instead
