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.
Agree, asking this question narrows it down. If it is only a single person that is experiencing this issue, then it is easy to solve. If it affects multiple users or a department, then it will require more digging information. Ask them if they tried restarting their laptop before testing the cable and port at their cube/office.
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!
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?
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.
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
for real
hello keith great to see u back
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.
Agree, asking this question narrows it down. If it is only a single person that is experiencing this issue, then it is easy to solve. If it affects multiple users or a department, then it will require more digging information. Ask them if they tried restarting their laptop before testing the cable and port at their cube/office.
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?
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
I don’t knows Keith but he’s a networking Jedi and yes he know much more
why it always fails when pinging a public/tunnel IP on my laptop?
Damn the myth, the legend.
How to use script to run commands?
Awesome
He may as well be speaking mandarin!!
lol agreed. That's why experience is the most important thing.
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.
why it always fails when pinging a public/tunnel IP?