Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

TM129: Networking > Module 20: Troubleshoot Common Network Problems > Flashcards

Module 20: Troubleshoot Common Network Problems Flashcards

(74 cards)

Start Studying
1
Q

here we may see

  1. Cables which are not connected
  2. Cables connected to the wrong port
  3. Loose cable connections
  4. Damaged cables and connectors
  5. Use of the wrong type of cable
A

using

sight

name 5 types of layer 1 (physical) problems might we encounter

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

when troubleshooting a wired or wireless issue

what 3 steps can we take using ping to verify proper communication

A

here we can:

  1. Ping from a wireless client to the default gateway. This verifies if the wireless client is connecting as expected.
  2. Ping from a wired client to the default gateway. This verifies if the wired client is connecting as expected.
  3. Ping from the wireless client to a wired client. This verifies if the wireless router is functioning as expected.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

using

smeel and taste, touch and sound

how might we discover

layer 1 (physical)

problems

A
  1. smell and taste
    1. can you smell or taste any burning or overheating components
  2. touch
    1. 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
  3. sound
    1. can you hear any clicking or whirling from the device or unfamiliar sounds this may signal a component is damaged or working incorectly
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

when documenting

previous troubleshooting

what information could we include

A

here we can include information about if the problem occured before. is there any documentation

specifically we may include

  1. Steps taken
  2. Results achieved
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

what is

ipconfig

used for

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

describe the command

nslookup host name | IP address

A

will make a query to the DNS server about the host name or IP address

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

the information we would include here is found by questioning end users about any symptoms or error messages seen

A

when including the

nature of the problem

in the documentation what information might we include

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

describe the

top-down troubleshooting method

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

when including the

nature of the problem

in the documentation what information might we include

A

the information we would include here is found by questioning end users about any symptoms or error messages seen

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

display detailed IP configuration. including DHCP, DNS server and MAC address

A

describe the command

ipconfig /all

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

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

A

describe the

comparison / spot the difference troubleshooting method

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

displays all connections and listening ports

A

describe the command

netstat -a

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

when a

networking problem arises

what are the first 3 steps to take

A

the steps include:

  1. confirm if there is really a problem
  2. asses what areas of the network have been affected
  3. start taking documentation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

name 4 technical cable problems that could arise

A

these include:

  1. straight through vs crossover
  2. correct termination T568A vs T568B
  3. cable length
  4. is the correct port being used
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

describe the

substitution / swap-the-component troubleshooting method

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

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

A

what is

tracert

useful for

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

when making

the initial documentation

what 4 peices of information might we include

A

this may include:

  1. nature of the problem
  2. equipment
  3. configuration and topology
  4. previous troubleshooting
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

describe the

bottom-up troubleshooting method

A

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)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

describe the command

ipconfig /all

A

display detailed IP configuration. including DHCP, DNS server and MAC address

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

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

A

describe a scnenario where you might encounter a

layer 4 (transport)

problem while troubleshooting

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

will make a query to the DNS server about the host name or IP address

A

describe the command

nslookup host name | IP address

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

describe the

comparison / spot the difference troubleshooting method

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

describe the command

ipconfig /release

A

this will release all current IP configurations if they were configured dynamically

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

when documenting the

equipment

involved in the problem where might we look for information and what information might we include

A

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

  1. Manufacturer
  2. Make / model
  3. Firmware version
  4. Operating system version
  5. Ownership / warranty information
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
describe the command ## Footnote **nslookup**
will show the DNS configuration for the host. and enter the nslookup programme
26
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*
27
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 ## Footnote **bottom-up troubleshooting method**
28
display basic IP configuration information
describe the command ## Footnote **ipconfig**
29
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
30
describe the ## Footnote **educated guess / shoot from the hip troubleshooting method**
this is an approach for more experienced technicians and relies on past kowledge to take a guess at where the problem lies
31
what is **tracert** useful for
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
32
describe the command **tracert** *ip address | host name*
this will send 3 packets with a time to live set for each router. when a router receives a packet that has a time to live of 0 then it will drop the packet and return information about itself to the source
33
describe the command ## Footnote **ipconfig /renew**
this will ask the DHCP server for new IP configurations. if a new IP address is not given this could point to problems at a lower level or a problem with the DHCP server
34
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
what is **ipconfig** used for
35
what is a consideration to take into account when pinging a domain name
when pinging a domain name and there is no reply it is wise to ping the IP address if known. this is because when pinging a domain name a DNS lookup must occur if this method fails it could point to a DNS problem
36
these include: 1. straight through vs crossover 2. correct termination T568A vs T568B 3. cable length 4. is the correct port being used
name 4 technical cable problems that could arise
37
this approach takes the documentation into account and from there making an educated choice as to where to start troubleshooting in the OSI model EXAMPLE: if you started troubleshooting at layer 3 (transport layer) and found that you cannot get an ip address then you would move down the OSI model however if this layer works correctly it can beassumed lower levels do aswell and so you move up
describe the ## Footnote **divide and conqeur troubleshooting method**
38
this command is used to view current network statistics such as current connections with other hosts. this command could reveal connections to your host which should not be there this may indicate that someone is connected to your host when they shouldnt be
what is **netstat** usefull for
39
once initial documentation has been taken what is the next step
starting the process of troubleshooting would be the next step after this
40
starting the process of troubleshooting would be the next step after this
once initial documentation has been taken what is the next step
41
this command is used to directly make a query to a dns server
what is **nslookup** useful for
42
this will release all current IP configurations if they were configured dynamically
describe the command ## Footnote **ipconfig /release**
43
this will send an echo request packet to the ip address or domain name
describe the command **ping** *ip-address | domain name*
44
describe the ## Footnote **divide and conqeur troubleshooting method**
this approach takes the documentation into account and from there making an educated choice as to where to start troubleshooting in the OSI model EXAMPLE: if you started troubleshooting at layer 3 (transport layer) and found that you cannot get an ip address then you would move down the OSI model however if this layer works correctly it can beassumed lower levels do aswell and so you move up
45
the steps include: 1. confirm if there is really a problem 2. asses what areas of the network have been affected 3. start taking documentation
when a **networking problem arises** what are the first 3 steps to take
46
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 1. Manufacturer 2. Make / model 3. Firmware version 4. Operating system version 5. Ownership / warranty information
when documenting the **equipment** involved in the problem where might we look for information and what information might we include
47
this may include: 1. The problem encountered 2. all attempts and steps taken to determine the cause of the problem 3. all attempts and steps taken to correct the problem and ensure that it will not reoccur
**whilst we are resolving an issue** what 3 types of notes might we make in the documentation
48
**whilst we are resolving an issue** what 3 types of notes might we make in the documentation
this may include: 1. The problem encountered 2. all attempts and steps taken to determine the cause of the problem 3. all attempts and steps taken to correct the problem and ensure that it will not reoccur
49
when documenting the **configuration and topology** what information can we include
here we can include information about where are we in the network, who are we connected to is there any network monitoring logs that we can gather specifically we may include 1. Physical and logical topology 2. Configuration files 3. Log files
50
this may include: 1. nature of the problem 2. equipment 3. configuration and topology 4. previous troubleshooting
when making **the initial documentation** what 4 peices of information might we include
51
this will send 3 packets with a time to live set for each router. when a router receives a packet that has a time to live of 0 then it will drop the packet and return information about itself to the source
describe the command **tracert** *ip address | host name*
52
1. smell and taste 1. can you smell or taste any burning or overheating components 2. touch 1. 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 3. sound 1. can you hear any clicking or whirling from the device or unfamiliar sounds this may signal a component is damaged or working incorectly
using **smeel and taste, touch and sound** how might we discover **layer 1 (physical)** problems
53
will show the DNS configuration for the host. and enter the nslookup programme
describe the command ## Footnote **nslookup**
54
what is **ping** usefull for
this command can verify communication between two IP hosts
55
using **sight** name 5 types of layer 1 (physical) problems might we encounter
here we may see 1. Cables which are not connected 2. Cables connected to the wrong port 3. Loose cable connections 4. Damaged cables and connectors 5. Use of the wrong type of cable
56
describe the command **ping** *ip-address | domain name*
this will send an echo request packet to the ip address or domain name
57
describe the ## Footnote **follow-the-path troubleshooting method**
this troubleshooting methods requires knowing the source and destination of the problem from here you assess each of the links disregarding any devices that are not in the path
58
this will ask the DHCP server for new IP configurations. if a new IP address is not given this could point to problems at a lower level or a problem with the DHCP server
describe the command ## Footnote **ipconfig /renew**
59
describe the command **tracert** *ip address | host name* **-h** *maximum\_hops*
the default maximum hops that tracert will use is 30. this command can be used to increase the number of hops it seraches for
60
here we can: 1. Ping from a wireless client to the default gateway. This verifies if the wireless client is connecting as expected. 2. Ping from a wired client to the default gateway. This verifies if the wired client is connecting as expected. 3. Ping from the wireless client to a wired client. This verifies if the wireless router is functioning as expected.
**when troubleshooting a wired or wireless issue** what 3 steps can we take using ping to verify proper communication
61
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
describe the ## Footnote **top-down troubleshooting method**
62
when pinging a domain name and there is no reply it is wise to ping the IP address if known. this is because when pinging a domain name a DNS lookup must occur if this method fails it could point to a DNS problem
what is a consideration to take into account when pinging a domain name
63
describe the command ## Footnote **ipconfig**
display basic IP configuration information
64
what is **netstat** usefull for
this command is used to view current network statistics such as current connections with other hosts. this command could reveal connections to your host which should not be there this may indicate that someone is connected to your host when they shouldnt be
65
these include: 1. bottom-up 2. top-down 3. divide and conquer 4. follow the path 5. substitution / swap the component 6. comparison / spot the difference 7. educated guess / shoot from the hip
what are 7 **troubleshooting methods** that can be used to isolate and find a problem
66
here we can include information about where are we in the network, who are we connected to is there any network monitoring logs that we can gather specifically we may include 1. Physical and logical topology 2. Configuration files 3. Log files
when documenting the **configuration and topology** what information can we include
67
what are 7 **troubleshooting methods** that can be used to isolate and find a problem
these include: 1. bottom-up 2. top-down 3. divide and conquer 4. follow the path 5. substitution / swap the component 6. comparison / spot the difference 7. educated guess / shoot from the hip
68
what is **nslookup** useful for
this command is used to directly make a query to a dns server
69
this is an approach for more experienced technicians and relies on past kowledge to take a guess at where the problem lies
describe the ## Footnote **educated guess / shoot from the hip troubleshooting method**
70
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
describe the ## Footnote **substitution / swap-the-component troubleshooting method**
71
describe the command ## Footnote **netstat -a**
displays all connections and listening ports
72
this command can verify communication between two IP hosts
what is **ping** usefull for
73
here we can include information about if the problem occured before. is there any documentation specifically we may include 1. Steps taken 2. Results achieved
when documenting **previous troubleshooting** what information could we include
74
this troubleshooting methods requires knowing the source and destination of the problem from here you assess each of the links disregarding any devices that are not in the path
describe the ## Footnote **follow-the-path troubleshooting method**

TM129: Networking (19 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions