Module 20: Troubleshoot Common Network Problems Flashcards
here we may see
- Cables which are not connected
- Cables connected to the wrong port
- Loose cable connections
- Damaged cables and connectors
- Use of the wrong type of cable
using
sight
name 5 types of layer 1 (physical) problems might we encounter
when troubleshooting a wired or wireless issue
what 3 steps can we take using ping to verify proper communication
here we can:
- Ping from a wireless client to the default gateway. This verifies if the wireless client is connecting as expected.
- Ping from a wired client to the default gateway. This verifies if the wired client is connecting as expected.
- Ping from the wireless client to a wired client. This verifies if the wireless router is functioning as expected.
using
smeel and taste, touch and sound
how might we discover
layer 1 (physical)
problems
- smell and taste
- can you smell or taste any burning or overheating components
- touch
- is there a lack of vibration or too much vibration this could indicate a cooling fan is not running or running to fast perhaps something else is causing excessive vibration
- sound
- can you hear any clicking or whirling from the device or unfamiliar sounds this may signal a component is damaged or working incorectly
when documenting
previous troubleshooting
what information could we include
here we can include information about if the problem occured before. is there any documentation
specifically we may include
- Steps taken
- Results achieved
what is
ipconfig
used for
this command is used to view current IP configurations. this is a handy tool for knowing if a host has an ip address or other IP configurations
describe the command
nslookup host name | IP address
will make a query to the DNS server about the host name or IP address
the information we would include here is found by questioning end users about any symptoms or error messages seen
when including the
nature of the problem
in the documentation what information might we include
describe the
top-down troubleshooting method
this approach is best employed when it is suspected that an application is causing the issue and so determining the problem in the application would be the first step
when including the
nature of the problem
in the documentation what information might we include
the information we would include here is found by questioning end users about any symptoms or error messages seen
display detailed IP configuration. including DHCP, DNS server and MAC address
describe the command
ipconfig /all
this involves comparing a non working device with a working one and assesssing differences such as configurations, software version, installed hardware. the non working system can then be configured identically to the working one. this approach may work in solving the problem but may not reveal the root cause
describe the
comparison / spot the difference troubleshooting method
displays all connections and listening ports
describe the command
netstat -a
when a
networking problem arises
what are the first 3 steps to take
the steps include:
- confirm if there is really a problem
- asses what areas of the network have been affected
- start taking documentation
name 4 technical cable problems that could arise
these include:
- straight through vs crossover
- correct termination T568A vs T568B
- cable length
- is the correct port being used
describe the
substitution / swap-the-component troubleshooting method
this simply involves swapping out a device with a working device if the problem persists then it can be assumed that the problem lies elsewhere
this command can be used to trace the path that a packet takes from the source to a destination. this command can be usefull when ping has failed since it can be seen exactly where the packet failed to be routed and in turn did not acheive communication
what is
tracert
useful for
when making
the initial documentation
what 4 peices of information might we include
this may include:
- nature of the problem
- equipment
- configuration and topology
- previous troubleshooting
describe the
bottom-up troubleshooting method
this involves working from the bottom of the OSI model and working your way up. this approach typically works best when it is suspected that physical equipment has failed (EXAMPLE: if the NIC lights are flashing then it can be assumed that layer 1 (physical) layer is not where the problem lies and so we can move up to layer 2)
describe the command
ipconfig /all
display detailed IP configuration. including DHCP, DNS server and MAC address
if pinging a remote server or local host appears to be working then it can be assumed that there are no problems on the layer 3 (network) and it is time to move up.
a device which deals with and might cause problems at the layer 4 (transport) is a firewall. it may be configured to block specific TCP or UDP packets such as TCP 80 which is HTTP traffic if this were being inspected and blocked by source then you would not receive any HTTP traffic
describe a scnenario where you might encounter a
layer 4 (transport)
problem while troubleshooting
will make a query to the DNS server about the host name or IP address
describe the command
nslookup host name | IP address
describe the
comparison / spot the difference troubleshooting method
this involves comparing a non working device with a working one and assesssing differences such as configurations, software version, installed hardware. the non working system can then be configured identically to the working one. this approach may work in solving the problem but may not reveal the root cause
describe the command
ipconfig /release
this will release all current IP configurations if they were configured dynamically
when documenting the
equipment
involved in the problem where might we look for information and what information might we include
when documenting this we can look at log files and documentation. documentation may reveal recent changes
the information we can include in the documentation are
- Manufacturer
- Make / model
- Firmware version
- Operating system version
- Ownership / warranty information
describe the command
nslookup
will show the DNS configuration for the host. and enter the nslookup programme
the default maximum hops that tracert will use is 30. this command can be used to increase the number of hops it seraches for
describe the command
tracert ip address | host name -h maximum_hops
this involves working from the bottom of the OSI model and working your way up. this approach typically works best when it is suspected that physical equipment has failed (EXAMPLE: if the NIC lights are flashing then it can be assumed that layer 1 (physical) layer is not where the problem lies and so we can move up to layer 2)
describe the
bottom-up troubleshooting method
display basic IP configuration information
describe the command
ipconfig
describe a scnenario where you might encounter a
layer 4 (transport)
problem while troubleshooting
if pinging a remote server or local host appears to be working then it can be assumed that there are no problems on the layer 3 (network) and it is time to move up.
a device which deals with and might cause problems at the layer 4 (transport) is a firewall. it may be configured to block specific TCP or UDP packets such as TCP 80 which is HTTP traffic if this were being inspected and blocked by source then you would not receive any HTTP traffic