LAB 20.

01 Step 1:

Step 2: Tool TDR Butt Set Protocol Analyzer Certifier Temp Monitor Multimeter Punchdown Tool Cable Tester Toner Probe OTDR Wire Stripper Crimping Tool Manufacturer LANSmart TDR Eclipse Data Diver Beagle USB Byte Brothers Springfield Craftsman TRENDnet Klein Tools Swell Schlumberger Irwin Emerson Typical Use Troubleshooting Troubleshooting Troubleshooting Troubleshooting Assembly/Repair Troubleshooting Assembly/Repair Both Troubleshooting Troubleshooting Assembly/Repair Assembly/Repair

LAB 20.03 Step 1: Ping in generally the first tool used when diagnosing connection issues. Ipconfig would also be used to diagnose network adapter issues. Nslookup may be used to see if the problem is DNS related. Tracert can determine how far the signal is reaching out from the troublesome node. Possibly Wireshark to see in which part of the attempt to communicate the error is occurring. Dig, route, My traceroute, and traceroute Step 2: IP Address 192.168.1.122 Step 3: DNS Server - 192.168.1.1 Step 4: Default Gateway Yes Step 5: DNS server Yes Subnet Mask 255.255.255.0 Default Gateway 192.168.1.1

Step 6:

Step 7:

Step 8:

Step 9: Protocol, Local Address, Source Address, State of connection.

LAB 20.05 Step 1: 1 Identify the Problem 2 Establish a Theory of probably cause. 3 Test the theory to determine cause. 4 Establish plan of action and identify potential effects. 5- Implement and test the solution or escalate as necessary. 6 Verify Full system functionality and implement preventative measures. 7 Document findings, actions, and outcomes. Step 2: 1 Gather info, identify symptoms, ask questions, determine changes, and find the root of the problem. Ask all users what when and where this went wrong. 2 Use your knowledge and information obtained to try and theorize a probably cause. 3 Test your theory without make any actual changes, as you may not have the authority to do so. Search for probable causes that dont require heavy modification. 4 Dont jump strait in, plan out your procedures and operate carefully. Move one step at a time. 5 Implement one solution at a time. Document your findings and/or changes you make. Dont be afraid of asking for assistance, possible try to recreate the problem. 6 Verify that the problem is solved, and record how you solved it. Double check that all components are functioning optimally. 7 Document the problem, the findings, the solutions, the symptoms, and pretty much everything else. The more you know about an issue the quicker you can fix and prevent it. Step 3: Exactly what was happening when the problem first occurred? Has anything been changed recently? Has the system been moved lately? Have you experienced and unusual network behavior lately?