Steps for Network Troubleshooting
Вставка
- Опубліковано 8 лис 2023
- Whether it's our own network that we really know well or it's a new network that we were just introduced to, if we have a certain process or methodology for troubleshooting, we can apply that methodology across the board.
Watch the entire CompTIA Network+ (N10-008) course: training.cbt.gg/slo
Check out our blog article How to Troubleshoot General Networking Issues for more info: blog.cbt.gg/cs4r
Not a CBT Nuggets subscriber? Start your free week: www.cbtnuggets.com/signup
-----------------
Connect with CBT Nuggets for the latest in IT training:
• Twitter - / cbtnuggets
• Facebook - / cbtnuggets
• Instagram - / cbtnuggets
• LinkedIn - / cbt-nuggets
#networktroubleshooting #networking #comptia #systemadministrator #networkadmin #itcertifications #itprofessional #ittraining #cbtnuggets
This man is a legend in the network community.
Yep he is truly is.
He may need to lay off the meth before making a video since he was talking like Don Trump Jr after he did a few bumps off of Kims ass
hello keith great to see u back
Hi Keith! Your excitement and enthusiasm to teach is contagious!! do you teach the entire Network+ course or do you and other team members swap throughout lessons?
For the N10-008, Keith teaches the entire course. Check it out: training.cbt.gg/slo
Damn the myth, the legend.
Which video are you referring? Also make a TCP/OSI LAYER Troubleshoot! for every layer how to?! That is the video I looking for!
To view the entire course content of Network+ (N10-008), you can go here: training.cbt.gg/slo
If you're not a current subscriber, you can sign up for a free trial to view the content: training.cbt.gg/sbp
Thanks!
@@cbtnuggets Does this course: Network+ (N10-008), also make a TCP/OSI LAYER Troubleshoot?
From years in TAC trenches I’d rather use a KT method before establishing a theory, to get a situation awareness and start problem isolation (Usual questions to customer: when did you start experiencing the issue, are you the only one affected -assess business impact for severity- and check for any changes around that time issue started. All this even before starting the tech analysis. That will avoid jumping to early conclusions from a prebuilt theory that may take more time to root cause if we start troubleshooting from wrong end.
Or, in some cases customers aren't paying attention, guess at your questions to give an answer even if it's wrong, give you bad information, and you still start at the wrong place. It goes both ways pretty much evenly.
Ok big words.
He may as well be speaking mandarin!!
Mandarin Chinese
This was horrible, cause you spoke like you were on speed and then you were all over the place trying to squeeze out as much as you could within a short time period.
It's nobody else's fault that you hear slowly. His talking speed is fine.
If you struggle with following along, I recommend using the drop down and changing the speed to match your cognitive tempo.