1 / 2100%
Ic alwaysc startc troubleshootingc usingc thesec simplec networkc troubleshootingc stepsc toc helpc
diagnosec andc refinec thec issue.c Becausec itc developsc ac successfulc scenarioc forc thec computer.
1. Checkc thec hardware.c Whenc you’rec beginningc thec troubleshootingc process,c checkc
allc yourc hardwarec toc makec surec it’sc connectedc properly,c turnedc on,c andc working.c Ifc ac
cordc hasc comec loosec orc somebodyc hasc switchedc offc anc importantc router,c thisc couldc
bec thec problemc behindc yourc networkingc issues.c There’sc noc pointc inc goingc throughc
thec processc ofc troubleshootingc networkc issuesc ifc allc youc needc toc doc isc plugc ac cordc in.c
Makec surec allc switchesc arec inc thec correctc positionsc andc haven’tc beenc bumpedc
accidentally.
2. Next,c turnc thec hardwarec offc andc backc onc again.c Thisc isc thec mainstayc ofc ITc
troubleshooting,c andc whilec itc mightc soundc simplistic,c oftenc itc reallyc doesc solvec thec
problem.c Powerc cyclingc yourc modem,c router,c andc PCc canc solvec simplec issues—justc
bec surec toc leavec eachc devicec offc forc atc leastc 60c secondsc beforec youc turnc itc backc on.
3. Usec ipconfig.c Openc thec commandc promptc andc typec “ipconfig”c (withoutc thec quotes)c
intoc thec terminal.c Thec Defaultc Gatewayc (listedc last)c isc yourc router’sc IP.c Yourc
computer’sc IPc addressc isc thec numberc nextc toc “IPc Address.”c Ifc yourc computer’sc IPc
addressc startsc withc 169,c thec computerc isc notc receivingc ac validc IPc address.c Ifc itc startsc
withc anythingc otherc thanc 169,c yourc computerc isc beingc allocatedc ac validc IPc addressc
fromc yourc router.
4. Tryc typingc inc “ipconfigc /release”c followedc byc “ipconfigc /renew”c toc getc ridc ofc yourc
currentc IPc addressc andc requestc ac newc one.c Thisc willc inc somec casesc solvec thec
problem.c Ifc youc stillc can’tc getc ac validc IPc fromc yourc router,c tryc pluggingc yourc
computerc straightc intoc thec modemc usingc anc ethernetc cable.c Ifc itc works,c thec problemc
liesc withc thec router.
5. Usec pingc andc tracert.c Ifc yourc routerc isc workingc fine,c andc youc havec anc IPc addressc
startingc withc somethingc otherc thanc 169,c thec problem’sc mostc likelyc locatedc betweenc
yourc routerc andc thec internet.c Atc thisc point,c it’sc timec toc usec thec pingc tool.c Tryc sendingc
ac pingc toc ac well-known,c largec server,c suchc asc Google,c toc seec ifc itc canc connectc withc
yourc router.c Youc canc pingc Googlec DNSc serversc byc openingc thec commandc promptc
andc typingc “pingc 8.8.8.8”;c youc canc alsoc addc “-t”c toc thec endc (pingc 8.8.8.8c -t)c toc getc itc
toc keepc pingingc thec serversc whilec youc troubleshoot.c Ifc thec pingsc failc toc send,c thec
commandc promptc willc returnc basicc informationc aboutc thec issue.
6. Youc canc usec thec tracertc commandc toc doc thec samec thing,c byc typingc “tracertc 8.8.8.8”;c
thisc willc showc youc eachc step,c orc “hop,”c betweenc yourc routerc andc thec Googlec DNSc
servers.c Youc canc seec wherec alongc thec pathwayc thec errorc isc arising.c Ifc thec errorc comesc
upc earlyc alongc thec pathway,c thec issuec isc morec likelyc somewherec inc yourc localc
network.
7. Performc ac DNSc check.c Usec thec commandc “nslookup”c toc determinec whetherc there’sc
ac problemc withc thec serverc you’rec tryingc toc connectc to.c Ifc youc performc ac DNSc checkc
on,c forc example,c google.comc andc receivec resultsc suchc asc “Timedc Out,”c “Serverc
Failure,”c “Refused,”c “Noc Responsec fromc Server,”c orc “Networkc Isc Unreachable,”c itc
mayc indicatec thec problemc originatesc inc thec DNSc serverc forc yourc destination.c (Youc
canc alsoc usec nslookupc toc checkc yourc ownc DNSc server.)
Students also viewed