upgrading and repairing PCs technicians ... - 400 Bad Request

288
Chapter 11—Networking
Troubleshooting Networks in Use
Table 11.17 Troubleshooting Networks On-the-Fly
Problem Symptoms Solution
Connection to network Other users can use shared First, have the user use Start,
not working for one user printers, drives, and so on. Close All Programs and log in
as new user. Pressing Cancel
or Esc instead of logging in
keeps the user off the network.
Use Network Neighborhood to
browse other computers on
network. If browse won’t
work, make sure correct
Network name is listed in
properties and that correct
protocols and protocol configurations
are present. All computers
in a workgroup must
use same the workgroup name
and protocol(s).
Next, check cable connections
at the server and workstation.
Check NIC for proper operation.
Use diagnostics software
provided with most cards to
test NVRAM, interrupt, loopback,
and send/receive signal
functions. Use the diagnostics
on two NICs on the same network
to send and receive signals
from each other.
Use Windows 9x or 2000’s
Device Manager and check
NIC’s properties. If any
resource conflicts are present,
card won’t work. Note that
IRQ steering on PCI cards with
recent chipsets enables multiple
devices to share an IRQ
without a conflict.
Connection to network No one can access Loose terminators or BNC
not working for network. T-connectors will cause trouble
multiple users for all workstations on Thinnet
cable segment.
Hub power or equipment failure
will cause trouble for all
stations using UTP.
Have read-only access Can’t save files to shared If you save your passwords in a
instead of full access drive. password cache, entering the
read-only password instead of
the full-access password will
limit your access with peer
servers.