TROUBLESHOOTING YOUR SCHOOLS NETWORK

1
TROUBLE-SHOOTING YOUR SCHOOLS NETWORK

2
MINIMIZE PROBLEMS

• Do you have your act together?

3
KNOW YOUR NETWORK!!!!

• Campus map
• Network connections-what goes where
• Types of cable
• Equipment
• Pictures of MDF, IDFs

4
KNOW YOUR NETWORK!!!!

• Document IP, MAC addresses
• Wireless locations and configurations
• Register wireless APs with NSSB
• Logins and passwords

5
PREVENTION

• Who do you take advice from? Be careful!!
• Do you use volunteers?
• Vendors?
• Other school tech coordinators (who tell you not
  to use Macafee)?
• Who will be left holding the bag? (You)
• Do you have line power protection?
• Monitor wireless APs.
• Communicate openly with NSSB including all
  wiring.

6
PREVENTION

• Protect equipment from power surges
• Keep equipment clean
• Take steps to reduce heat for equipment
• Control rodents
• Keep out outside computers

7
INSTALL MCAFEE EPO AGENT. IF USING STAND-ALONE
VERSION KEEP IT UPDATED WEEKLY.
8
KEEP WINDOWS SERVICE PACKS AND SECURITY PATCHES
UPDATED.
9
CANNOT CONNECT!

• Obtain accurate description avoid broad
  generalizations.
• Obtain the truth
• What applications are involve?
• Lotus Notes? Where is the Notes server?
  Internet Explorer?
• Is the computer plugged in - electrical, network?

10
CANNOT CONNECT!

• What IP address are you getting?
• Check IP configuration, especially for first-time
  set-ups. 169.xxx.xxx.xxx may indicate that
  computer is not getting DHCP address from router.
  192.xxx.xxx.xxx or 10.xxx.xxx.xxx may indicate
  that there is a wireless router giving out DHCP.
• Check gateway, DNS, subnet mask, on the
  computer.

11
CAN OTHER COMPUTERS IN THE BUILDING GET OUT?

• YES the problem is confined to that
  computer/connection to the IDF.
• NO the problem may be with the IDF/MDF/Wide
  Area Connection. Call the NSSB staff in the
  Liliuokalani Bldg. basement, 586-3206 and ask if
  the router at your school is OK. Ask if they can
  see beyond the router into the schools devices.

12
AT THE COMPUTER

• Is the green link light on the computer NIC card
  on (none for iMacs)? Is the yellow activity
  light flashing?
• Unplug and plug in the patch cord into the wall
  and into the computer again.
• Make sure that the clip on the plug clicks into
  place.
• Swap patch cords with one that you know works

13
AT THE COMPUTER

• Plug a computer that you know works into the
  questionable wall drop.
• Ping another computer in the same
  building/different building/another school.
• This will tell you if there the network
  connection between your computer and the computer
  you are pinging is good. Note The computer must
  be on, of course.

14
At the IDF

• Is that port connected from the patch panel to
  the switch?
• Is the green link light on the switch/hub for
  that port on be careful, some switch link lights
  (switch 4400) show yellow for 10Mbs connections?
  
• Are link lights for other ports on? Are yellow
  activity lights flashing?
• Is the green link light for the fiber
  module/transceiver on and steady (1100/3300 on
  the back of the hub/switch, 4400 module on
  front)? Is the yellow activity light flashing?

15
At the MDF

• Is the green link light on the core switch
  5500G or 7700 - for that particular port on? Is
  the yellow activity light flashing?

16
THINGS TO AVOID DOING

• Panic
• Disconnect the IPS
• Restart equipment without first contacting NSSB
• Lie

17
TOOLS

• Ping
• Mac Ping (Pre-OSX)
• Cable tester
• Termination tools
• A logical mind

18
TOP 10 COUNTDOWN
19
10

• Bad NIC - Network Interface Card

20
9

• Duplicate IP address
• Or incorrect IP configuration

21
8

• Bad cable
• Or cable not connected correctly

22
7

• Loop on network

23
6

• Virus, spyware

24
5

• Wide Area Down
• Oceanic
• SONET
• DSL/Frame Relay

25
4

• Wireless AP
• Rogue
• Un- or misconfigured

26
3

• Problems at MDF
• Power failure
• Reboot problem
• Environment heat, dust

27
2

• IDF
• Bad switch or fiber module
• Data drop not connected
• Fiber jumper incorrectly connected

28
1

• Tipping Point (IPS)
• When is it or not the problem?