Top Banner
Network Troubleshooting and Tools Domain 5.0
153

Network Troubleshooting and Tools

Dec 11, 2021

Download

Documents

dariahiddleston
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Network Troubleshooting and Tools

NetworkTroubleshootingandTools

Domain5.0

Page 2: Network Troubleshooting and Tools

5.0NetworkTroubleshootingandTools• 5.1Explainthenetworktroubleshootingmethodology.• 5.2Givenascenario,usetheappropriatetool.• 5.3Givenascenario,troubleshootcommonwiredconnectivityandperformanceissues.• 5.4Givenascenario,troubleshootcommonwirelessconnectivityandperformanceissues.• 5.5Givenascenario,troubleshootcommonnetworkserviceissues.

Page 3: Network Troubleshooting and Tools

5.1ExplainTheNetwork

TroubleshootingMethodology

• IdentifytheProblem• EstablishaTheoryofProbableCause• TesttheTheorytoDeterminetheCause• EstablishaPlanofActiontoResolvetheProblemandIdentifyPotentialEffects• ImplementtheSolutionorEscalateasNecessary• VerifyFullSystemFunctionalityand,ifApplicable,ImplementPreventiveMeasures• DocumentFindings,Actions,andOutcomes

Page 4: Network Troubleshooting and Tools

IdentifytheProblem

Page 5: Network Troubleshooting and Tools

GatherInformation

• Lookatsymptomsoftheproblem• Reviewproblemswithusers• Reviewchangesinsoftware,hardware,appliedpolicies(bothnetworkandsecurity

• Lookatthedevice/slogs• Reviewallerrormessages• Reviewallsecuritymessages

• Beawareoflatestsecuritynews• Whatadvisoriesandknownattacksexistthatpertaintoyourenvironment?• Arethereanynewexploitsthatyouneedtobewatchfulfor?

Page 6: Network Troubleshooting and Tools

DuplicatetheProblem,includingwithusers

• Workwithuser/sandobserveproblem• Carefullyaskuser/squestionsandlistentotheirresponses• Observeeachstepthatistakentocausetheproblem• Doestheproblemhappentoasingleuser,groupofusers,entirebuildingororganization

• Replicateproblemasanadministratordetective• Usesamestepsasobserved• Tryacompletelydifferentmethodtocompleteatasktoseeifproblemcontinuestoexist

Page 7: Network Troubleshooting and Tools

IdentifySymptoms

• Whatsymptomsareobserved• Couldthisbeahardwareissue,connectivityissue,policiesappliedtodevicesorsoftware

• Considersymptomsandpinpointwhatarea/sbeingaffected• Isthisaproblemthatpointstoasingledeviceoruser

• Usererror,deviceerror,acombination• Isthisaproblemthatpointstoaparticularserver• Isthisadirectoryservicesproblem• Isthisasecurityproblem• Isthisafirewallproblem• Isthisacableorwirelessproblem

Page 8: Network Troubleshooting and Tools

DetermineIfAnythingHasChanged

• Whenconsideringsymptomsoftheproblem,hasanythingchanged• Isthesymptomsoftheproblemoccurringonasinglemachinethathasrecentlybeenchangedorreplaced• Wasthereachangeinanyconfigurationofswitches,routers,firewalls• Wasthereachangeindirectoryservices• WasthereachangeinDHCP• WasthereachangeinDNS• Wasthereachangeinpoliciesappliestousersorcomputer• Canyouundoorwishtoundoanyofthem

Page 9: Network Troubleshooting and Tools

ApproachMultipleProblemsIndividually

• Ifduringobservations,multipleproblemsseemtobeoccurring• Approachonlyoneproblematatime• Attimes,fixingthemostcommonproblemsandfixtheotherobservedproblems

• Attemptingtofixmultipleproblemscanaddconfusionandnotfixanyandaddadditionalproblems

Page 10: Network Troubleshooting and Tools

EstablishaTheoryofProbableCause

Page 11: Network Troubleshooting and Tools

QuestiontheObvious

• Oftenbestfirststepistoeliminatetheobvious• Theeasiestfixisoftenthebestone

• Sometimesthefirststepisnotthecorrectanswer,butstillhelpswiththesolution• Eachstepusuallytakesyouclosertothesolutionoftheproblem• Networkscanhaveswitchmisconfigurations• Portspeed,duplex/simplex,wrongVLAN,wrongIPinformation,etc.

Page 12: Network Troubleshooting and Tools

ConsiderMultipleApproaches

• Therearetwostandardapproaches• Top-to-bottom/bottom-to-topOSIModel• Divideandconquer

Page 13: Network Troubleshooting and Tools

Top-to-bottom/Bottom-to-topOSIModel

• Top-to-bottomstartswiththeuserapplicationandworkdownthroughtheOSImodel• Findthelayerwhereaproblemexists• Correcttheproblematthatlayer

• Bottom-to-topstartsatthephysicalanddatalinklayersandworkuptheOSImodel• Downsideismoreworkcheckingalldevices

Page 14: Network Troubleshooting and Tools

DivideandConquer

• SelectanOSIlayer• Doahealthcheck• WorkupordowntheOSImodel• ConsidertheTCP/IPDODmodelvs.OSImodel

Page 15: Network Troubleshooting and Tools

OSIModelvs.TCP/IP(DOD)Model

OSIModel7Application6Presentation5 Session4 Transport3 Network2DataLink1Physical

TCP/IP(DOD)ModelApplication

Transport

InternetNetwork Interface

Page 16: Network Troubleshooting and Tools

TesttheTheorytoDeterminetheCause

Page 17: Network Troubleshooting and Tools

OncetheTheoryIsConfirmed,DeterminetheNextStepstoResolvetheProblem• Oncedeterminethetheory,checktoseeifyoucanfixtheproblem• Formulateanddocumentstepsusedwiththetheorytoresolvetheproblem• Ifyoursolutiondoesnotfixtheproblem,BESUREtorestoretheoriginalconfiguration• Youdonotwanttointroducenewproblems/variables

Page 18: Network Troubleshooting and Tools

IftheTheoryIsNotConfirmed,EstablishaNewTheoryorEscalate• Ifthetheoryandstepsformulatedtoresolvetheproblemdoesnotfixtheproblemanewtheorymustbeformortheproblemescalated• Devicemisconfigurationshouldbeconsideredanddependingonorganizationpolicies,escalationtoahigherlevelofexpertisewillbedone• Whenandhowescalationwillbedecidedbyanorganization’spoliciesandprocedures

• Examplesmightbeswitchingloops,routermisconfigurations,ARPproblems,powerproblems

Page 19: Network Troubleshooting and Tools

EstablishaPlanofActiontoResolvetheProblemandIdentifythePotentialEffects

Page 20: Network Troubleshooting and Tools

EstablishaPlanofActiontoResolvetheProblemandIdentifythePotentialEffects• Whentheproblemisidentified,theplanofresolutionsiscarriedout,thesolutionneedstoappliedandtestedforeffectsthroughoutthenetwork

Page 21: Network Troubleshooting and Tools

ImplementtheSolutionorEscalateasNecessary

Page 22: Network Troubleshooting and Tools

ImplementtheSolutionorEscalateasNecessary• Whenthesolution/fixisappliedandfullfunctionalityofthenetworkisevaluated• Solutionsteps,causeoffailure,completedocumentationneedstobeimplemented• Futurepreventionshouldalsobedocumented• Ifthesolutionisfoundtoaffectothernetworkoperations,anothersolutionshouldbeconsideredaswellasescalation

Page 23: Network Troubleshooting and Tools

VerifyFullSystemFunctionalityand,IfApplicable,ImplementPreventiveMeasures

Page 24: Network Troubleshooting and Tools

Verifyfullsystemfunctionalityand,ifapplicable,implementpreventivemeasures• Runregressionteststouncoveranychangestothesystemornetwork• Regressiontestsareare-runofanyoriginalfunctionality/securitytests

Page 25: Network Troubleshooting and Tools

DocumentFindings,Actions,andOutcomes

Page 26: Network Troubleshooting and Tools

DocumentFindings,Actions,andOutcomes

• Thisstepissometimesavoidedandisoneofthemostimportantinthetroubleshootingprocess• Thiscanbeusedinthefuturebyothernetworkadministrators• Importantdocumentationincludes• Whentheproblemoccurredandwhenthesolutionwasimplemented• Whytheparticularsolutionwasused• Whatchangesorfixesweremade• Otherfixesthatmighthavebeenconsideredandwhytheywerenotused• Whodocumentedandappliedthesolution

• EstablishasearchableknowledgebaseofproblemsandsolutionsforallITstafftoreferto

Page 27: Network Troubleshooting and Tools

5.2GivenaScenario,Use

theAppropriateTool

• HardwareTools– BasicHandHeld• HardwareTools- Analyzers• SoftwareTools– TestersandAnalyzers• SoftwareTools– CommandLine

Page 28: Network Troubleshooting and Tools

HardwareTools– BasicHandHeld

Page 29: Network Troubleshooting and Tools

Crimper

• Acrimperisbasictoolusedtoproperlyattachconnectorstotheendofcables• RJ-45onunshieldedtwisted-pair(UTP)• BNCorFoncoaxialcable• Similartoapairofpliersbutspecializedforthecableandends• Eventalentedusersshouldhaveextraends

Page 30: Network Troubleshooting and Tools

CableTester

• Acabletesterisusedtotesttheviabilityofthecableandconnector• Open/brokenwires/connections• Shorts• Incorrectpin-out

• High-endtestersalsoreportsignallossoncableandatconnectors• Therearetwocommonwaystotestaconnection:

• A continuitytest• A resistance test

• Therearetwocommonwaystotestforashort:• A lowvoltage test• A highvoltage test

Besuretomovethecablearoundwhiletestingtocheckforloose/intermittentconnections!

Page 31: Network Troubleshooting and Tools

Laser/LightSource• YoucanshootalaserorLEDlightsourcedownafiberopticcable• Checktheotherendtoseeifthelightiscomingthrough• Becarefulwithlasers– donotlookdirectlyintothesource

Page 32: Network Troubleshooting and Tools

Punch-downTool

• Usedtoterminatecableincableclosets• Pushesindividualwiresintwistedpairintotheircorrespondingconnectorona66- or110-blockpatchpanelorwalljack• Mosthaveabladebuiltintothetiptocutoffexcesswire

Page 33: Network Troubleshooting and Tools

LoopbackAdapter

Aloopbackadaptercanberefertoseveralthings:• Ahardwareplugthattakesoutputandredirectsitbacktotheport’sinput• Checkstoseeifsignalcanbesentandreceivedonthatport

• Avirtualinterfaceonahost/device• AssignedanIPaddress• Doesn’tdirectlyconnecttothenetwork• Isreachedthroughaphysicalportonthedevice(thedeviceroutesincomingsignalinternallytotheloopback)• Usedasan“alwaysup”interfaceforremoteaccesstothedevice,diagnosticslikeping,orassigninganIPaddress-baseddeviceID

Page 34: Network Troubleshooting and Tools

Multimeter

• Amultimeterisoneofthesimplestcable-testingtools• Checkscontinuity(nobreaks)inacable• CanalsobeusedtocheckDCresistanceonacable

• Canalsobeusedforvoltagetestsonapowersource• ACorDC• Variouspowerranges

Page 35: Network Troubleshooting and Tools

BasicElectricityCharacteristics

• Electricalcircuitshavethreebasiccharacteristics:• Voltage=E

• Measuredinvolts• CanbeAC(alternatingcurrent)orDC(directcurrent)

• Resistance=R• Measuredinohms

• Current=I• Measuredinamperes(ormilliamperes)• MostmetersonlymeasureDCamps

OhmsLaw:E=IR(volts=ampsxohms)PowerFormula:P=IE(powerinwatts=ampsxvolts)

Page 36: Network Troubleshooting and Tools

-

+

VoltageTests• Putmultimeterprobesinparallelwithtarget• AC– forwalloutlets/powerstrips,ACmotors• DC– forbatteries,powersupplies– putredprobeon+positiveside,blackprobeon– negative/commonside• VoltageRanges– choosetherangetargetisin,ifunknownstartwithhighestandthendialdown!• Devicesusuallyneedtohavethevoltagewithinaparticularrange• Somedevicesneedthefrequencytobeeither50Hzor60Hz

AC DC

Page 37: Network Troubleshooting and Tools

Resistance/ContinuityTests

• Placesavoltageonthecircuittocalculatetheresistance• MAKESUREthecircuityouaremeasuringisNOTenergized!• Youcandamagethemeter!

• Putmultimeterprobesoneithersideofthecable/target• SelectResistanceRangeappropriatefortarget• Ifnotsureofrange,startwithhighestanddialdown

Power

Page 38: Network Troubleshooting and Tools

Current(Amperage)Tests• Current• Puttheprobesinserieswiththeload,betweenthepowersourcecontacts• Ifuncertain,startwithhighestsettinganddialdown• DoNOTEVERperformacurrenttestonacircuitwithnoload!

• HighCurrent• Specialtestifthecurrentdrawisknowntobeupto10amps• Usesaspecialpositivejackfortheredprobe

• MostmultimetersonlymeasureDCcurrent• Currenttestsareveryunusualforanetworktechnician

-

+

DC

Page 39: Network Troubleshooting and Tools

HardwareTools–Analyzers

Page 40: Network Troubleshooting and Tools

TDRandOTDR

• Timedomainreflectometer(TDR)sendsasignalthroughacabletocheckcontinuity• Signalbouncesbackatthebreak/end• Thereflectedsignalisanalyzed

• Timeittook• Levelofsignal/light

• Veryusefulforfindingwherethebreak/openpointisininstalledcable• Opticaltimedomainreflectometer(OTDR)ususedforfiber-opticcables

Page 41: Network Troubleshooting and Tools

OTDRTest Launchcableconnectstocablebeingtested

OTDRTrace

Page 42: Network Troubleshooting and Tools

TypicalFeaturesofanOTDRTrace

Page 43: Network Troubleshooting and Tools

Lightmeter

• Lightmeterisasimplertoolusedtocertifyandtroubleshootfiber-opticcable• Canmeasure/detectloss/breakagebysendinglightthroughafiberopticcable

Page 44: Network Troubleshooting and Tools

ToneGenerator• Usedtolocateacable

• Onapatchpanel/jack• Inagroupofinstalledcables

• Veryusefulwhenyoudon’tknowwhichisthecableinquestionorwherethecableleadsto• Usethetonertoinjectawarblingsignal• Usethewandtolocatewhichcable/jackhasthesignal• Becareful:crosstalkbetweencablescanbemisleading

• Prefertousethisonnon-livecircuits• Alsoknownas:

• Foxandhound• Telephonetracer• Cabletracer• Toner

Page 45: Network Troubleshooting and Tools

SpectrumAnalyzer• Measuresthelevelofsignal(includingnoise)acrossarangeoffrequencies• UsedtofindinterferencelevelsondifferentWi-Fichannels• Usuallyrequires:• A specializedhardwaredonglethatcanprocessANYsignaltype,notjustWi-Fi• Softwarethatcaninterpretthereading

• Somedevicesareself-contained• SomedevicesrequireaPC

Page 46: Network Troubleshooting and Tools

Activity5.2.1– TroubleshootingwithHardwareTools• Let’susesomeanalyzertoolstohelpuslocateandfixaproblem

Page 47: Network Troubleshooting and Tools

SoftwareTools– TestersandAnalyzers

Page 48: Network Troubleshooting and Tools

PacketSnifferTools• Usedtocaptureandanalyzetrafficonanetwork• Requireanetworkadapterinpromiscuousmode• Mostaresoftware-based• Mosthaveprotocolanalysiscapabilities• PartofIDS/IPSfunctionality• Commonexamplesinclude:

• Wireshark• SolarWindowsBandwidthAnalyzer• PTRG• Airmon-ng• Kismet• tcpdump• Snort• MicrosoftNetworkMonitor

Page 49: Network Troubleshooting and Tools

PortScanner• Asoftwareapplicationthatscansnetworkhostsforopenports• Anactivereconnaissancetacticbypentestersandhackers

• Usedtosearchfortargets• Openportsimplyservicesonahostthatareacceptingconnections

• Anorganization’snetworkadministratorcanscanthenetworkforopenportstohelpmakesureonlyportslegitimatelyneededarebeingused• Portstates:

• Open/listening– TCPSYNelicitsaSYN/ACKresponse– portisopenforbusiness• Closedordenied– TCPSYNelicitsaRST(reset)response– noserviceislisteningonthatport

• filteredorblocked– noresponseofanykindduetofirewallorthehostdoesnotexistatthatIPaddress

Page 50: Network Troubleshooting and Tools

ProtocolAnalyzer

• Ahardware/softwaretoolthatcapturesandanalyzesnetworktraffic• Canidentify:

• Protocolsusedonthenetwork• Percentageofprotocoluse• Bandwidthutilizationbyprotocolorhost• Unauthorized,unknown,orpotentiallymalicioustraffic(byprotocol)• Peaktimesofutilization• Hostswithnetworkinterfacesinpromiscuousmode

• Mostlyusedbysniffers• Examplesinclude:

• SolarWindsDeepPacketInspectionandAnalysisTool• NetFlow• sFlow

Page 51: Network Troubleshooting and Tools

ProtocolAnalyzerExample

Page 52: Network Troubleshooting and Tools

Wi-FiAnalyzer

• AWi-Fianalyzerissimilartothenetworkanalyzerexceptitisusedforwirelessnetworks• Collectspacketsfromthewirelessnetworksanddetects:

• Acceptablenetworks,hiddennetworks,interferencebyothernetworks,devices,andothermachinery

• Canuseforwirelesssurveysforplacementofwirelessaccesspoints(WAPs)

Page 53: Network Troubleshooting and Tools

BandwidthSpeedTester

• Softwarethatallowsyoutocheckthebandwidth(speed)ofanInternetconnection• HelpsidentifyperformanceissueswithyourISP

• Onlymeasuresspeedtoaparticularsite,nottoallwebsitesontheInternet

• Vendorsofferthisserviceasapartoftheirwebsite• Measuresdownloadanduploadspeed• Somesoftwarevendorsalsoofferlinequalitychecks• Looking-glasssitesrunasoftwarethatallowsviewingofroutingdataaswell

Page 54: Network Troubleshooting and Tools

Activity5.2.2– TroubleshootingWithSoftwareTools• Let’susesomesoftwaretoolstotroubleshootaproblem

Page 55: Network Troubleshooting and Tools

SoftwareTools–CommandLine

Page 56: Network Troubleshooting and Tools

CommandLine(CLI)• Atext-baseduserinterfacetoacomputer'soperatingsystemoran application• A usertypesincommandsandreceivestext-basedoutput

• Nomouse• Nographics• Mightincludedcoloredtextormenus

• AlsoknownasaTUI(text-baseduserinterface)• AsopposedtoaGUI(graphicaluserinterface)

• Generallyusedbyadministrators/ITsupport,hackers,Linuxusers,andadvancedusers• Examples:

• CiscoCLI• Windowscmd.exeorMS-DOSprompt• Linuxbashshell

Page 57: Network Troubleshooting and Tools

Ping

• An application that uses ICMP echo request and echo response• Used by virtually all operating systems and platforms

• The most basic network connectivity test• Verifies connectivity at Layer 3• Might be blocked by firewalls• Ping6 and Ping -6 tests connectivity on IPv6 networks

Page 58: Network Troubleshooting and Tools

Tracert,Traceroute

• CommandlinenetworkdiagnostictoolsthattrackthepathofapacketasittraversesanIPv4network• Windowsusestracert• Unix,Linux,andMacOSusetraceroute

• Tracert-6,traceroute6,andtraceroute-6testconnectivitybetweendevicesonaIPv6network• UsesincreasingTTLvaluesintheIPheadertoinducerouters(hops)downthepathtoexpirethepacketsandsendbackinformationtothesender

Page 59: Network Troubleshooting and Tools

HowTracerouteWorks1. Sendersendsaseriesofpackets(eitherICMPorUDP)toadestination2. Startingpacket(s)havetheTime-to-LiveintheIPheadersetto“1”3. ThefirsthoptoreceivethepacketdecrementstheTTLto“0”4. Thathopdiscardsthepacket,sendinganICMPexpiredintransitmessage

tothesender(thehopalsoidentifiesitselfinthatmessage)5. ThesendersendsafewmorepacketstothedestinationwithaTTLof“2”6. ThefirsthopdecrementstheTTLto17. ThesecondhopdecrementstheTTLto0,discardsthepacket,andsends

amessagetothesender8. Theprocessrepeatsuntilthepacketreachesthefinaldestination9. Gaps(***)intheoutputindicatethathopdidnotrespond

• It’seitherafirewallortoobusy

Page 60: Network Troubleshooting and Tools

NslookupandDig

• Command-linenetworkutilitiesusedtoqueryaDNSserver• CanquerytheDNSserverforvarioustypesofrecords,includingafullzonetransfer(completedumpofalloftherecordsforadomain)• NslookupisusedwithWindows• Dig(domaininformationgrouper)isusedwithLinuxandUnix

Page 61: Network Troubleshooting and Tools

Ipconfig

• AcommandlinenetworkutilityusedbyWindowsthatdisplaysthedevice’scurrentIPconfiguration• Hasvariousswitchestoreturndifferenttypesofinformation• Ipconfig/allreturnsallinformation

• Informationincludes:• IPaddress,subnetmask,defaultgateway,DNS,WINS,DHCPleaseandexpiretimes,hardware(MAC)address,DNSdomainnameonthatinterface• Informationisreturnedforeveryinterface,whetherphysical,virtual,ortunnel

• UsedtoreleaseandrenewDHCPlease• Ipconfig/release;ipconfig/renew

Page 62: Network Troubleshooting and Tools

Ifconfig

• TheLinux/Unix/Macequivalentofipconfig• Doesnotshowexactsameinformationasipconfig• Forexample,doesnotshowtheaddressoftheDNSserver

Page 63: Network Troubleshooting and Tools

Iptables

• Usedtoconfigure,maintain,andinspectthetablesofIPv4packetfilterrulesintheLinuxkernelfirewall• Multipletablesmaybeconfigured• Eachtablecontainsanumberofbuilt-inchainsandmayalsocontainuser-definedchains• Achainisalistofrulesthatcanmatchasetofpackets• Eachrulespecifieswhattodowithapacketthatmatcheswhichisreferredtoasa`target',whichmaybeajumptoauser-definedchaininthesametable

Page 64: Network Troubleshooting and Tools

Netstat• Acommand-linenetworkutilitytoolthatshowsthestatus/statisticsofportsonacomputer• UsedbynearlyallPCtypeoperatingsystems• Dependingontheversion,canshow:

• Listeningports• Portswithestablishedsessions• Thestatusofanestablishedsession(LISTEN,ESTABLISHED,TIME_WAIT,CLOSE_WAIT,etc.)• Knownroutes• Amountofpacketsinandout• Numberofpacketerrors• ThePID(processID)oftheapplicationthatisusingtheport

• Examples:• netstat-nao• netstat--help• netstat/?

Page 65: Network Troubleshooting and Tools

CommonMicrosoftNetstatSwitchesSwitch Function-a Displaysallconnectionsandlisteningports.-r Displaysthecontentsoftheroutingtable.

-n SpeedsexecutionbytellingNetstatnottoconvertaddressesandportnumberstonames.

-s Showsper-protocolstatisticsforIP,ICMP,TCP,andUDP.

-p<protocol>

Showsconnectioninformationforthespecifiedprotocol.TheprotocolcanbeTCP,UDP,orIP.Whenusedwiththe-soption,showsstatisticsforthespecifiedprotocol.Inthiscase,theprotocolcanbeTCP,UDP,IP,orICMP.

-e ShowsEthernetstatistics,andcanbecombinedwith-s.

Interval Showsanewsetofstatisticseachinterval(inseconds).YoucanstoptheredisplayingofNetstatstatisticsbytypingCTRL-C.

Page 66: Network Troubleshooting and Tools

Tcpdump

• A commandlinepacketanalyzer• DisplaysthecontentsTCP/IPandothernetworkpacketstransmittedfromorreceivedbyahost• Availableon*NIXsystems

Page 67: Network Troubleshooting and Tools

PathPing

• Aroutetracingtoolthatcombinestracertwithsomequalityofservicefeatures• PathPing outputincludes:• Eachhop/routerIPaddress• Lengthoftimetoreachdestination• Packetssuccessfully/unsuccessfullysent(loss)

Page 68: Network Troubleshooting and Tools

NetworkMapper(Nmap)

• Acommandlinenetworkscannerandsecurityutility• Usedto:• Pingsweepandportscan• Identifyservicesandoperatingsystemsbasedontheirresponsetonetworkpackets• Inventoryhostsandservicesonthenetwork• Performsomevulnerabilitytesting

• Builtinto*NIXoperatingsystems• CanbedownloadedandrunonWindows

Page 69: Network Troubleshooting and Tools

Route

• AcommandthatallowsanadministratortoviewandconfigureroutingtablesonWindowsand*NIXhosts• Examples:

routeprint=displaycurrentroutingtable

routeADD157.0.0.0MASK255.0.0.0157.55.80.1METRIC3IF2destination^^mask ^gatewaymetric^^interface#

Page 70: Network Troubleshooting and Tools

Arp

• AprotocolformappingMACaddresstoIPaddresses• Acommandtodisplayoreditthehost’sARPcache

Example:

arp-a=displaythecurrentarpcachearp-s157.55.85.21200-aa-00-62-c6-09=addastaticmappingarp-d=clearthearpcacheofaspecificmappingoralldynamicallylearnedmappings

Page 71: Network Troubleshooting and Tools

Dig

• A*NIX command-line toolforquerying DNSserversandtroubleshootingDNSfunctionality• Digcanfunctionincommandlinemodeorinbatchmode• Usesaspecifiednameserverordevice’sdefaultresolverconfiguredinthe /etc/resolv.conf file• Digispartofthe BIND domainnameserversoftwaresuite• Digisacomplimentarytooltonslookup

Page 72: Network Troubleshooting and Tools

Activity5.2.3– UsingCommandLineTools

• Let’susesomecommandlinetoolstotroubleshootaproblem

Page 73: Network Troubleshooting and Tools

5.3GivenaScenario,

TroubleshootCommonWired

Connectivityand

PerformanceIssues

• SignalIssues:• Attenuation• Latency• Jitter• Crosstalk• EMI

• PhysicalIssues:• Open/short• Incorrectpin-out• IncorrectCableType• BadPort• Damagedcable• Bentpins

• TransceiverIssues:• Transceivermismatch• TX/RXreverse• Duplex/speedmismatch

• TrafficFlowIssues:• Bottleneck• VLANmismatch• NetworkconnectionLEDstatusindicators

Page 74: Network Troubleshooting and Tools

SignalIssues

Page 75: Network Troubleshooting and Tools

Attenuation

• A termthatreferstoanyreductioninthestrengthofa signal• Attenuationoccursnaturallyasasignal, digital or analog,travelsfartherfromitssource• Alsoknownassignalloss• Incopperandfiberopticcables,attenuationismeasureindecibelsperfoot,kilometer,ormile• Lesstheattenuationperunitdistancemeansmoreefficientcable• Repeaterscanbeinsertedtoovercomeattenuation

Page 76: Network Troubleshooting and Tools

Latency

• Latencyreferstoatimeintervalordelaywhenadeviceiswaitingforanotherdevicetodosomething• One-waylatencyismeasuredbycountingthetimeittakesapackettotravelfromitssourcetoitsdestination• Round-triplatencyismeasuredbyaddingone-waylatencytimeandthetimeittakesforthepackettoreturntothesource• Usedtodiagnosenetworkperformanceissues

• Sometypesoftraffic(especiallyrealtimevoiceandvideo)cannottoleratemuchlatency

Page 77: Network Troubleshooting and Tools

Jitter

• Variablelatencyfrompackettopacket• Especiallyproblematicforreal-timestreamingtransmissions(voiceandvideo)• Makescallqualitychoppy

• Worstformoflatency• Devicesareconstantlychangingtheirreceivebuffersizestotrytoadapttovariabledelaytimes

Page 78: Network Troubleshooting and Tools

Crosstalk

• Crosstalkisadisruptioncausedbytheelectricormagneticfieldsofonetelecommunication signal affectingasignalinanadjacent circuit• Crosstalkiscausedbycalledelectromagneticinterference(EMI)• Occurinmicrocircuitswithincomputers,audioequipment,andwithinnetworks• Occurswhenusingcoaxialcable,unshieldedtwistedpair(UTP),andevenattimeswithopticalfiber• Nearendcrosstalk(NEXT)– interferenceclosetotheoriginofthedata• Farendcrosstalk(FEXT)– interferenceatthereceivingendofthedata

• Shieldingandincreasedtwistsintwistedpairhelpreducecrosstalk

Page 79: Network Troubleshooting and Tools

ElectromagneticInterference(EMI)

• Interferencecausedbyanelectromagneticfield• Occurswhencablesareinstallednearelectricaldevices,evennormalofficefixtures• Unshieldedtwistedpair(UTP)canbeaffected• Fiberopticcableisresistant

• Commoncausesinclude:• Motors• Elevators• Fans• Fluorescentlights• Anythingthatgeneratesanelectricalfieldarounditself

• CarefulcableplacementisessentialtoavoidEMI

Page 80: Network Troubleshooting and Tools

Activity5.3.1– TroubleshootingSignalProblems• Let’stroubleshootsomesignalproblems

Page 81: Network Troubleshooting and Tools

PhysicalIssues

Page 82: Network Troubleshooting and Tools

Open/Short

• AnOpenfaultisatermthatdescribesaconditionwhereafullcircuitisnotmade• Usuallycausedbycutincableoralooseconnection

• Ashortisatermthatdescribesaconditionwherethereisaunintendedconnectionbetweenthesourceanddestinationallowingthedatatoflowtounintendeddestinations• Usuallycausedbybadwire,cutinwiresthatallowbarewirestotouch

Page 83: Network Troubleshooting and Tools

IncorrectPin-out

• Pin-outisatermthatdescribeshowwiresincablesareinstalledinanend• Notaproblemifpurchasingfromareputablevendor• Ifnetworktechnicianmakecablesneedtousecorrectpinouts• Problemscaninclude:

• Noconnectivity,improper/problematicconnectivity,veryshortdistanceconnectivity

• Canbedetectedbyvisualinspectionorbyusingacablechecker• Aconnectorthathasbeencrimpedwiththewrongpin-outwillhavetobecutoff,andanewconnectorcrimpedonproperly

Page 84: Network Troubleshooting and Tools

IncorrectCableTypeTherearemanypossibilitiesforchoosinganincorrectcabletype• Usingastraightthroughcablewhenyouneedacrossovercable• Usingacrossovercablewhenyouneedastraightthroughcable• Usingastraightthroughorcrossovercablewhenyouneedarollovercable• Usingacabletypethatisnotstandardscompliant• YoushoulduseEIA/TIA568Aor568B(mostuseB)

• Usingalowercablecategorywhenahigheroneisneeded• Speed,interferenceresistance,orPoEdistanceisinsufficient

• Canalsooccurfrombaddesignchoices• Insufficientcabletypechosen

Page 85: Network Troubleshooting and Tools

BadPort

• Abadportcanmeanthataportonarouterorswitchisnotworkinginaphysicalsense• Theport’smetalpinscouldbebentorcorroded• Theelectricalcircuitryforthatportisdamaged• Thelaserdiode/LEDforafiberopticportisnotproducinglightproperly• Whentroubleshootingbadports,ensurethatthedevicedidnotdeliberatelyshuttheportoffasasafetymeasure• Happensalotwhenswitchtrunksdetectswitchingloops

Page 86: Network Troubleshooting and Tools

DamagedCables

• Whentroubleshootingnetworkconnectivity,startingwiththesimplestsolutionsfirstisagoodidea• Checkingfordamagedcablesandwiringisagoodplacetostart• Bystartingandchangingoutacable,agreatdealoftimecanbesaved• Cablesandwiringcanbecheckusingamultifunctioncabletester

Page 87: Network Troubleshooting and Tools

BentPins

• Pinsinendscanbebentifadeviceischangedorbentduringinstallation• Preventsconnectivity• Useadifferentport

Page 88: Network Troubleshooting and Tools

TransceiverIssues

Page 89: Network Troubleshooting and Tools

TransceiverMismatch

• Thetransceiverisincompatiblewiththecabling,oranothertransceiverattheotherendofthecabling• Configurationbetweendevicescouldbeincompatible:• Speedmismatch• Duplexmismatch• Singleormultimodefiberopticmismatch• Frequencyorsignaltypemismatch

• Mismatchesusuallydisplayerrorsintheportstatistics

Page 90: Network Troubleshooting and Tools

TX/RXReverse

• TXisatermusedfortransmitandRXisatermusedforreceive• TheTXhastoconnecttoRXforeverypairofwireinnetworkcables• Usinganordinarypatchcabletoconnectsimilardevicesusuallycausesaconnectionoftransmittotransmitandreceivetoreceive• Newerdeviceshavethecapacitytoautosensethetypeofcableandcorrecttheproblem;olderdevicesmaynot

Page 91: Network Troubleshooting and Tools

Duplex/SpeedMismatch

• Configurationscanbeincorrectifthenetworkadministratordoesnotconsiderportspeedandduplexsettings• Youmayhavemultiplechoices• AutoNegotiation• Static,suchasspeedandhalfduplexorfullduplex

• Withoutthecorrectsettings,communicationcouldbeproblematic(lotsoferrors)orimpossible

Page 92: Network Troubleshooting and Tools

Activity5.3.2– TroubleshootingTransceiverProblems• Let’stroubleshoottransceiverproblems

Page 93: Network Troubleshooting and Tools

TrafficFlowIssues

Page 94: Network Troubleshooting and Tools

Bottlenecks• Thetermbottleneckinanetworkisusedtodescribeaconditionthatinwhichonedevice,interface,ornetworksegmenthastoomuchtraffic• Itholdsuppacketflowfortherestofthenetwork

• Canhavemanycauses:• Growthofnetworkandorganization• Baddeviceornetworkcard• Malware• Securitybreach

• Identifybottlenecksusing:• Network/packetanalyzer• Statusreportsfromthedeviceinterfaces(especiallyswitchandrouterports)• Statusreportsfromserversthatprovideservicesonthesegment

• Examininglogsisagoodwaytolookformalwareandsecuritybreaches

Page 95: Network Troubleshooting and Tools

VLANMismatch

• AgeneralconditionwhentwodevicesareerroneouslyconnectedtothesameVLAN• A“NativeVLANMismatch”occurswhenthenativeVLANofaswitchportisdifferentfromthenativeVLANoftheportofanother(connected)switch• IfaswitchdetectsthatanotherswitchisconnectedbutconfiguredwithadifferentnativeVLAN,youwillseeconsoleerrormessages

Page 96: Network Troubleshooting and Tools

NetworkConnectionLEDStatusIndicators

• Lightsondevicesthatprovidestatusinformationaboutthedevice• Caninclude:

• Power• Portinanormal(forwarding)state(green)• Portblocked(amber)• Normalactivitydetected(blinking)• Speedorduplexmismatch(rapidblinking)• Currentbandwidth/throughput/duplex• Differentlightsthatflashduringbootuptoindicatedifferentselfdiagnostictests

Page 97: Network Troubleshooting and Tools

5.4GivenaScenario,

TroubleshootCommonWireless

ConnectivityandPerformance

Issues

• SignalLoss• Attenuation• Reflection• Refraction• Absorption

• Latency&Jitter• AntennaIssues

• Incorrectantennatype• Incorrectantennaplacement

• IncorrectWAPtype• WAPIssues

• Interference• Channeloverlap

• Overcapacity• Distancelimitations• Frequencymismatch• Powerlevels• Signal-to-noiseratio

• WAPMisconfiguration• WrongSSID• Wrongpassphrase• Securitytypemismatch

Page 98: Network Troubleshooting and Tools

SignalLoss

Page 99: Network Troubleshooting and Tools

Attenuation

• Signalstrengthweakensnaturallyoverlongerdistance• Absorptive,reflective,andrefractivematerialswillalsodistortorattenuateasignal

Page 100: Network Troubleshooting and Tools

Reflection

• Reflectionisatermusedtodescribeasignalbouncingoffanobject• Inawirednetwork,thesignalreflectsoffofabreakinthewire,ortheunterminatedendofthewire• Inawirelessnetwork,thesignalreflectsoffofahardobjectsuchasawall,furniture,concrete,metal,etc.

• Areflectedsignalbouncesbackonitself,causingphasecancellation,attenuation,ordistortion• Occursalotinofficesthathavecomplexandintricatelydesignedstructuresandfurniture/equipmentplacement• Ifalargeamountofreflectionoccurs,signalscanbeweakenedandalsocauseinterferenceatthereceiver

Page 101: Network Troubleshooting and Tools

Refraction• Thebendingofasignalwaveformwhenitentersamediumwherethespeedisdifferent• Changesthedirectionofthewave• Forexample,glassorwatercanrefractwaves• ThiscanaffectWAPplacement

• Watchoutforglasswallsorfishtanks!• Ifasignalchangesdirectionintravelingfromsendertoreceiver, thiscancause:• lowerdatarates• highretries• overalllesseningofcapacity

Page 102: Network Troubleshooting and Tools

Absorption

• Oneofthemostcommonreactionsawirelesssignalhaswhenitencountersdifferenttypesofmaterial• Thematerialconvertsthesignal’senergyintoheat• Thesignaldoesnotreflectoffoforpassthroughanabsorptivematerial• Thiseffectivelyblocksthereceiverfromreceivingthesignal

Page 103: Network Troubleshooting and Tools

RFAbsorptionRatesbyCommonMaterials

Material AbsorptionRate Amountofsignalabsorbed

Amount ofsignalthatpassesthrough

Plasterboard/drywall

3– 5db 50– 70% 30– 50%

Glasswallandmetalframe

6db 75% 25%

Metaldoor 6– 10db 80– 90% 10– 20%Window 3db 50% 50%Concretewall 6– 15db 75– 97% 3– 25%Blockwall 4– 6 db 40– 75% 25– 60%

Page 104: Network Troubleshooting and Tools

Latency&Jitter

Page 105: Network Troubleshooting and Tools

Latency

• Justasthereislatencyonawirednetwork,thereisalsolatencyonwireless• Usessamecarriersensemultipleaccessaswired,butmustputupwithmuchmorenoiseandobstacles

• Causedby:• Distance• Interferenceandretransmissions• Arrangementandplacementofwirelessaccesspoints(WAP’s)• Typeandpositionofantennae• Numberofusersonthewirelessnetwork

Page 106: Network Troubleshooting and Tools

Jitter

• TherootcausesofjitterandlatencyonaWIFInetwork:• availablebandwidth• numberofpeopleusingtheconnection• interference

• Jitteriscausedbyvarianceintheamountofbandwidthbeingusedinthewirelessnetwork

Page 107: Network Troubleshooting and Tools

AntennaIssues

Page 108: Network Troubleshooting and Tools

IncorrectAntennaType• Antennaselection willhaveamajorimpactonwirelessperformance• TherearetwobasictypesofantennasforWLANs• Directional/Uni-directional

• Themorefocusedthesignalisinaparticulardirection,thestrongerthesignalisinthatdirection

• Canbe90or180degrees,oruni-directionalYAGI(straightline)• Higher gainantennascanbeusedoutdoorstoextend point-to-pointlinksoveralongerdistanceand/orcreatea point-to-multipointnetwork

• Usetohelpcontainsignalinacertainarea• Omni-directional

• Designedtoradiatesignalsequallyinalldirection,butwithaweakersignalforall• Useifyouneedtotransmitfroma centralnodetousersscatteredallaround anarea

• TherearealsoCPE(customerpremisesequipment)antennas

Page 109: Network Troubleshooting and Tools

IncorrectAntennaPlacement

• Positionantennawhereitcanprovidethemaximumbenefitwiththeminimuminterference• Createaheatmap/spectrumanalysistolookfordeadspots• Ensureenoughantennas/WAPsexisttoprovidedesiredcoverage• Makesuredirectionalantennasarepointedintherightdirection,andnotevenslightlyoff

• Makesure90degreeantennasareinthecornerofanareapointedinward• Makesure180degreeantennasareontheborderwallpointedinward

• Inpoint-to-pointlinks,maintainline-of-sightbetweenthetransmitterandreceiverantennas asmuchaspossible• Placethereceiverantennasothatit’satacorrectdistancefromthe transmitter• Usetherighttypeofreceiverantenna• Locateantennasawayfromanysuspectedsourcesofinterference• Carefullyaligntheantennasformaximumsignalgain

Page 110: Network Troubleshooting and Tools

IncorrectWAPType

Page 111: Network Troubleshooting and Tools

IncorrectWirelessDeviceType

• ChooseaWAPtypethatisappropriateforyourenvironment• Don’tuseawirelessPtPbridgeasanAP– frequencymaybewrong• Don’tuseaCPE(customerpremisesequipment)asanAP– beamisnarrowlyfocused,meanttotravel15kmormore;notsuitableforuserswhomaybebroadlyscatteredaroundthesite

• EnsureyouuseWAPsandcontrollersthatcanhandletheaggregatetraffic/numberofconnections• Forexample,aSOHOWAPcanusuallyonlyhandle10connectionsatanyonetime• ACiscoLWAPPWAPcanhandle50ormoreconnectionsatatime• DedicatedwirelesscontrollerscantelltheWAPstoloadbalanceclientconnections(whenpractical)

Page 112: Network Troubleshooting and Tools

Non-APWirelessStationExamples

Wirelessconnectivity+PoEforvideosurveillance

CPEwithline-of-sightconnectivitytoISP(couldalsobeaPtPbridgeonyourcampus)

Page 113: Network Troubleshooting and Tools

CPEPoint-to-PointWirelessLinkExample

CPErangecanreachprovidertowerat15kmormore

Mightbe2.4GHz,butantennashapeisfordirectional,not

omni-directionallink.NotmeanttobeanAPforusersatthe

customersite.

Page 114: Network Troubleshooting and Tools

CPEPoint-to-MultipointWirelessLinkExample

EachcustomerhasaCPEtoreachtheprovider’stower.Again,thisisnotmeanttobeanAPforendusersatthe

customerlocation.

Page 115: Network Troubleshooting and Tools

WAPIssues

Page 116: Network Troubleshooting and Tools

Interference• Wirelessinterferenceisatermthatreferstoanythingthatwouldimpedethewirelesssignal• Somecauses/solutionsinclude• Physicalobjects– moveantennas• Busychannels– changechannels• RFI/EMI– moveWAPsawayfromsourcesofinterference• Toomanyusersonthewireless– addaccesspoints,configuregoodplacement,loadbalanceusers• Nonwirelessdevices– wirelessphones,microwaves,wirelessvideocameras– changechannel

• BadelectricalconnectionscancausebroadRFspectrumemissions– fixconnections• RFjamming– DDoSattacks– shieldthenetworkifpossible

Page 117: Network Troubleshooting and Tools

ChannelOverlap

• Inthe2.4GHzband,1,6,and11aretheonlynon-overlappingchannels• Overlappingchannelsarenotaproblemifnooneisusingtheadjacentchannels• Thereare25non-overlappingchannelsinthe5GHzspectrum• Putachannelplaninplacetoavoidaself-inducedperformanceproblem• Useaspectrumanalyzertoidentifypotentialchanneloverlap

Page 118: Network Troubleshooting and Tools

Overcapacity

• WhenplanningaWirelessnetworkitisimportanttodoalegitimatewirelesssurvey• Takeintoconsiderationtheareaofcoverage• Numberofexpectedusersintheareacoverage,includingnumberofdevicesperuserandguests• Typeofantennaneeded• Placementofantennas• Objectsthatmayinterferewiththewirelesssignals

• EnsureyoudopropercapacityplanningincludingaggregatedatathroughputonalluplinksandswitchestheWAPSconnectto• Useyourwirelesscontrollertoenforceconnectionlimitsandpolicies

Page 119: Network Troubleshooting and Tools

DistanceLimitations

• Planningwillhelpwithdistancelimitations,butasanorganizationgrowssignalsmayreachlimits• UseanRFamplifiertoincreasesignalstrength• Considerusingarepeater/rangeextenderbeforeinstallingadditionalAPs• ConsiderrelocatingAPs• Considerreplacingantennas• Consideraddingbridges(orinstallingawiredconnection)toreachadditionalareas

Page 120: Network Troubleshooting and Tools

FrequencyMismatch

• Makesurethatclientscanusethesamefrequency/channelastheWAP• Don’tuseaJapanesemodel(thatgoesuptoChannel14)intheUS

• Makesureyouprovideforboth2.4GHzand5GHzclients• Considerifsomeclientsalsouse900MHz• CertainproductssuchastheUbiquitiNanoStationNSM3orNSM365usedifferentfrequencies(3GHz,3.65GHz)tocreateawirelesspoint-to-pointbridge• TheymightlooklikearegularAP,buttheyarenotdesignedtohandleclientconnections

Page 121: Network Troubleshooting and Tools

PowerLevels

• Somedevicesallowyoutoconfigurehigherpowerlevels• Ifyoucannotincreasethepowerofadevice,upgradethedeviceoraddmoreAPsforcoverage

Page 122: Network Troubleshooting and Tools

Signal-to-NoiseRatio

• Therelativepoweroftheradiosignaltothenoisefloor• AkaS/N• Youwanttheradiosignalleveltobeasfarabovethenoiseflooraspossible• Ifitisbelowthenoisefloor,itbecomesharderto“digitout”ofthesurroundingnoise• TheSignaltoNoise(S/N)ratiocanbeincreasedbyprovidingthesourcewithahigherlevelofsignaloutputpower

Page 123: Network Troubleshooting and Tools

WAPMisconfiguration

Page 124: Network Troubleshooting and Tools

WrongSSID

• YoumightchoosetonotbroadcasttheSSIDforsecurityreasons• Theuserattemptstomanuallyconfiguretheconnection• UseswrongSSID• NotrealizingthattheSSIDiscasesensitive

• Or,theuserisattachedtoaneviltwin

Page 125: Network Troubleshooting and Tools

WrongPassphrase

• TheencryptionorpassphraseisnotconfiguredproperlyontheWirelessAccessPoint(WAP)• Theuserdoesnotknowthecorrectpassphraseorthatthepassphraseiscasesensitive

Page 126: Network Troubleshooting and Tools

SecurityTypeMismatch

• Clientmightbetryingtousethewrongencryptiontype• MostclientdevicescanautodetectifthesecurityisWEP,WPA,orWPA-2• Olderclientsmighthavetobemanuallyconfigured

Page 127: Network Troubleshooting and Tools

Activity5.4- TroubleshootingWAPIssues

• Let’stroubleshootsomecommonWAPissues

Page 128: Network Troubleshooting and Tools

5.5GivenaScenario,

TroubleshootCommonNetwork

ServiceIssues

• CommonNetworkIssues• PhysicalConnectivity• IncorrectIPAddress• IncorrectGateway• IncorrectNetmask• NamesNotResolving• UntrustedSSLCertificate

• DHCPIssues• DuplicateIPAddresses• ExpiredIPAddress• RogueDHCP• ExhaustedDHCPScope

• Firewall/ACLIssues• BlockedTCP/UDPPorts• IncorrectHost-basedFirewallSettings

• IncorrectACLSettings

• AdvancedNetworkIssues• DNSServerIssues• DuplicateMACAddresses

• IncorrectTime

• UnresponsiveService• HardwareFailure

Page 129: Network Troubleshooting and Tools

CommonNetworkIssues

Page 130: Network Troubleshooting and Tools

PhysicalConnectivity

• Verifylinklights• Sendandreceiveonbothsides

• Verifycable• Cablemightbeinsufficientforneed

• Wrongcategory• Toolongforrequirement

• Mightstillseelinklights• Onebrokenwirewillbreakthesignalbalance

• PermittingEMI/RFI

Page 131: Network Troubleshooting and Tools

IncorrectIPAddress

• Useipconfigtoverifycurrentconfiguration• Ensureinterfaceisusingappropriateaddressingmethod• DHCP,static

• BounceinterfaceorchangeIPconfigurationmethodtoclearconfig

Page 132: Network Troubleshooting and Tools

IncorrectSubnetMask

• Causesahosttomakeawrongforwardingdecision• IfthedestinationIPaddressisinthesamesubnet,thehostARPstofindtheMACaddressofthedestinationandthensendsthepacketdirectlytothedestination• Ifthedestinationisinadifferentnetwork,thehostARPstofindtheMACaddressofthedefaultgateway,andthensendsthepackettothegateway• Subnetmaskmust:• Bethesameforallhostsonasubnet• NotallowIPaddressoverlapbetweensubnets

Page 133: Network Troubleshooting and Tools

IncorrectGateway

• Willpreventtrafficfromleavingthelocalnetwork• Hosthasamissingorincorrectdefaultgateway• Routerhasthewrongaddressorsubnetmask

• Verifyconfigurationonlocaldevice• ipconfig/all

• VerifyconfigurationonDHCPserver• Verifyconfigurationonrouter• showipinterfacebrief(Cisco)

Page 134: Network Troubleshooting and Tools

NamesNotResolving

• Checkfornetworkconnectivity• Pingbyname• VerifyyourDNSserverIPaddressesarecorrect• PingtheIPaddressofthehostyouaretryingtogetto(ifitisknown)• VerifywhichDNSserverisbeingusedwithnslookupordig• VerifyyourDNSsuffix• ReleaseandrenewyourDHCPServerIPaddress(andDNSinformation)• Rebootyourcomputerand/orrouter

Page 135: Network Troubleshooting and Tools

UntrustedSSLCertificate

• AnUntrustedSSLCertificateisacertificatethat• Hasexpired• Isnotsignedbyalegitimatevendor• Shouldnotbetrusted• Canbearesultofusinganolderandnonsupportedwebbrowser

• Usersneedtobeinstructedtonotvisitthesite• Browsersthatusersarerunningshouldbecurrentforsecurityreasons

Page 136: Network Troubleshooting and Tools

DHCPIssues

Page 137: Network Troubleshooting and Tools

DuplicateIPAddresses

• Thecomputerordeviceshouldshowanerror• ThecomputerordevicecouldhavebeengivenaddressinformationstaticallywhileontheDHCPserverconfigurationwasnotreservedoroutsidetheDHCPrange• AttempttogetadifferentleasefromtheDHCPserver• Rebootthehosttoclearconfig

Page 138: Network Troubleshooting and Tools

ExpiredIPAddress

• ClientsthatreceivedIPaddressinformationfromaDHCPserverattempttorenewtheirlease• Usuallywhen½oftheleasetimehasexpired,andthenatregularintervals• TheDHCPservercouldbedownorunavailable• DHCPclientmightnotbeawarethattheDHCPserverwaschanged• AWindowsorMacclientwillself-assignanAPIPAaddress– 169.254.0.0range

• Reboottheclienttoclearoutanyexistingleaseandattempttoobtainanewlease

Page 139: Network Troubleshooting and Tools

RogueDHCPServer• ARogueDHCPServerisaserveraddedtothenetworkbyunauthorizedpartyandisnotabletobeconfiguredbytheorganization’slegitimatenetworkadministrator• Usuallyhappenswhensomeoneaddsawirelessroutertothenetwork,leavingthedefaultDHCPservicerunningonthedevice• CancauseaclienttoreceivefalseIPaddressinformationtocreateman-in-the-middleanddenial-of-serviceattacks• Identifyandtakedowntheroguedevice

• LooktoseeiftheSSIDgiveshintsastothelocationorpersonwhoinstalledit• YoumayhavetouseseveralWi-Fimobiledevicesinacoordinatedefforttotriangulatethelocationoftherogue

Page 140: Network Troubleshooting and Tools

ExhaustedDHCPScope

• TheDHCPserverranoutofaddresses• TheexhaustionofaDHCPscopeindicatesthattheorganization’snetworkadministratorhasnotplannedforthegrowthofthenetwork• TheleasetimemightalsobetoolonginthecaseofamobileworkforcethatcomesinandoutoftheLAN• NeedtoincreasethenumberofIPaddressinformationinthepool,and/ordecreasetheleasetime

Page 141: Network Troubleshooting and Tools

Firewall/ACLIssues

Page 142: Network Troubleshooting and Tools

IncorrectHost-basedFirewallSettings

• Asstatedinthepreviousslide,someblockedsettingscouldhavebeenconfiguredonthefirewall• Examinetheuser’spersonalfirewallsettingstoseeiftheypermitthecorrecttrafficin/outofthedevice

Page 143: Network Troubleshooting and Tools

BlockedTCP/UDPPorts

• Thiscouldbetheresultoffirewallorrouterrulesandarecorrectlyblocked• Nochangemaybeneeded

• Couldbeamisconfigurationofrulesonthefirewallorrouter• Especiallylikelyonauser’slaptoporsoftwarefirewall

• Anexceptioncouldbeconfiguredforaspecificclientoruser

Page 144: Network Troubleshooting and Tools

IncorrectServer/ServiceACLSettings

• ACLsettingsarenotonlyforfirewallsandpacketfilteringrouters• AnAccessControlList(ACL)isusedtodefinewho/whatcanaccessthesystem• Ifcorrectlyset,willblockunwanteddata/packets• BlockshackershavingaspecificIPaddress• Agreatsecuritysolutiontounauthorizedaccessoftheorganization’snetwork

• AserverorprintermighthaveamisconfiguredACL• Causestheusertomistakenlythinkthereisanetworkproblemwhentheycannotconnect

Page 145: Network Troubleshooting and Tools

AdvancedNetworkIssues

Page 146: Network Troubleshooting and Tools

DNSServerIssues

• Verifynonetworkissuesorobstructivefirewallsettings• Testwithdigornslookup• CheckDNSconfiguration• Verifyrecordsinzone

• RestartDNSserverservice• ClearDNSresolvercache

Page 147: Network Troubleshooting and Tools

DuplicateMACAddresses

• MACaddressesareassignedtodevicesandareunique• TwodevicesusingthesameMACaddresswillcauseaswitchtoforwardthetraffictobothdevices• Ifduplicatesarefound,aroguedevicemaybepartofamalwareattack• Locateanddisableunauthorizeddevice/switchport

Page 148: Network Troubleshooting and Tools

IncorrectTime

• IfaclientorserverisnotbeingupdatedbyaNetworkTimeServerusingNetworkTimeProtocol(NTP)itisinsecureandneedstobeupdatedtouseNTP• Mayupdates,patches,andsecurityupdatesdependonthetimeontheclientusingthecorrecttime• MicrosoftActiveDirectoryloginsdependontimesynchronizedserversandclients• Thisisacriticalconfigurationthatneedstobekeptuptodate

Page 149: Network Troubleshooting and Tools

UnresponsiveService

Page 150: Network Troubleshooting and Tools

UnresponsiveService

• Aservicethatdoesnotrespondcouldbedueto• Anoverloadonaserverorservers• Aserverbeingdown• Incorrectconfiguration• Malwareattack

• Testing• Seeifsomeoneelsecanconnect• Telnetorportscantoseeifserviceisresponding• Checkserverconsole/logs

• Solutions• Restartservice• Addcapacity• Replaceorrepairtheserver• PatchtheOSorapplication• Reconfiguretheserverandservice

Page 151: Network Troubleshooting and Tools

HardwareFailure

Page 152: Network Troubleshooting and Tools

HardwareFailure

• Useastep-by-steplogicalapproachtotracedownahardwarefailureonthenetwork• Divide-and-conquertoeliminatewholenetworksegments

Page 153: Network Troubleshooting and Tools

Activity5.5– CaseStudy:TroubleshootinganUnusualNetworkIssue• Let’sexaminearealworldtroubleshootingcasestudy