4.1 Troubleshooting Basics (KL)

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

1 hour 39 minutes
Video Transcription
Hello and welcome to this Callie fundamentals lesson. I'm very excited to be here with you today, so we're going to be giving into and talking about troubleshooting. So you may be wondering, How do I troubleshoot Kelly? How do I go about solving problems? Things of that nature? Well, the good news is today, when you walk away from this lesson,
you're going tohave some high level troubleshooting steps that you can use
to ensure that you're able to successfully overcome problems and find solutions. The good news is, if you've had trouble shooting experience with Windows or networking equipment, things of that nature, it's not a lot different. We're just going to really touch on the basics again and make sure that we all have the same foundation moving forward. So
one of the first things that we always talked about is checking the physical,
and one of the things that I've run into early in my career was making sure that everything is plugged in and turned on. I can't tell you how many times I've looked at a system and discovered that it's off. I had some some funny stories back in,
you know, my college days where I was working on trying to get a council connection into a Cisco device.
I worked on it for about five minutes, had a buddy come over and he turned the power on. And then I felt really, really silly for the rest of the day. But that's not the lesson that you easily forget. So always check to make sure everything's plugged in and turn on. Does anything smell burnt? So if it's not your breakfast as we've got over here, if it's
if it smells like you've got some maybe electrical issues or something of that nature,
open your device up and see if there's anything going on and make sure that you don't have any charges or anything of that nature.
Is your artist making funny sounds? So you know this is maybe an exaggerated example here. But if you hear scratching, scraping things of that nature, suddenly your equipment's not working right. You may have some hard disk issues, so keep that in mind.
And, you know, I've run into before where I've had something like this happening where I've got some cable issues or the cable
is not connecting or it's not working try different physical cables. Try a few different things to just make sure that you're not having cable issues or something of that nature.
Also, did you follow the directions carefully? Did you do steps one through 10 according to the directions. If you skipped anything, go back and check it out.
And of course, you know, just make sure that you start from the basics every time that you start with the physical and then you work your way into the networking area here.
So after you've ensured that everything's connected, everything's running. Remember, some of you may be using ah guest or some type of virtual machine. Some of you may have loaded Callie directly onto the hardware, and you may not have some of these same issues with respect to what virtual machines are going to experience.
if you're having network issues or connective ity issues and the physical is obviously not the problem,
make sure that you check your network adapter settings in whatever you know, hyper visor that you're using. A lot of times, you know what I like to do is if I'm testing tools or something of that nature, I'll do a host on Lee Connection. But in that instance, I shouldn't be able to get out to the Internet or do anything of that nature. So make sure that if you need to
that you have your settings, you know said accordingly
and then do a couple checks Can you ping the Google D. N s server? Can you ping? You know, the I P addresses? That should be pink bubble on the internet like 8989898 Here can you ping Google by name? So those were some things that if you can ping the actual i p address but you can't paying the actual name of a system,
then you may have some D. N s issues if you can't pin your gateway address, which you know, we put up here. So when you do an I p configure, if convict on a system
and you get a gateway address, if you can't paying that, maybe there's a problem there. So remember, be systematic in the way that you're looking at network issues and connectivity issues. Take it one thing at a time and, you know, don't let it get on your nerves or cause any stress on your report there.
So once we check those areas, you know if it's specific to an application or service, there's a couple steps that we can take there. So if you want to look at a specific service like in this case, we look at Apache to you can use the service service name here and then status and that I'll give you the status of the system and the service. It will tell you whether or not it's running,
as you can see here. We did a start on that,
and then we ran service Apache to status again, and then we can see that it's active and working. So you know you can do that. If you want to check everything at once like we've got over here, then you can do a service, and then this two dashes their status all. And then I'll give you a running list of everything that's that's currently owner off. So the plus here means that it's on
minus means that it's not
so if you're trying to do something and it's got a service related to it and you come in and you see that minuses there you may want to try starting that
now. Sometimes what can happen is is that you may have service is that want to use the same port so you can use nets, stat. And then the switch here Dash N p lmt. And what that does is it will show you the service is in the running ports and everything like that. If you were running,
ah, patchy, too. And it's on Port 80. And then, for some reason you try to use a different,
um, you know, Web service or something of that nature and it needs doing on Port 80 and there's a conflict. You may need to change the listening port in the configuration file to make sure that that works together with Apache two or something like that. And remember, if you did make changes to the convict file and now you're having issues,
go back and check that. See if you made a mistake. Look for spelling errors, et cetera,
and if you can do so, always make a copy of the convict file to ensure that if you make a mistake or have an issue, you can change it back to a known good status
and, of course, with anything. When in doubt, google it out. So keyword searches, air message searches, things of that nature is going to be huge. As you get into working with any distribution insecurity in I t. In general, you're gonna have to learn to use Google. But if you're gonna continue to use Callie
and you're gonna want to work with and learn more about it, you're obviously going to run into issues from time to time.
The forms are a great place to go. There's a great community here that maybe had some of the same issues you've had, and they've spent the time and effort working on it. And maybe you can find a solution there and then, you know, try to use some keyword searches in, you know, your Google searches. So if you know, you know it's not a network issue, maybe you can,
you know, take away the word network when you're searching for
terms or something on that, like that, an advanced search. Or maybe if you're looking to find things that Onley include network, then maybe you ensure that it always has the word network or something of that nature. So Google is your best friend when it comes to trouble shooting or any search engine of choice, to be honest with you, but make sure that your patient,
if anything, starts to get on your nerves and you're starting to have a hard time.
Step away. Remember, you want to enjoy the things that you're doing. You want to enjoy working with these tools sets you want to enjoy learning and and things of that nature. So if you start to experience a high level of stress or you're getting angry at the situation, step back sometimes a breath of fresh air
and a fresh set of eyes. Once you, you know, you kind of clear your head and come back
is the best way to solve a problem.
So with those things in mind, let's do a quick check on learning. So if I can paying a website by its I P address, okay, so I can pay in the i p address of the website, but not its domain name. I likely have what kind of issue.
All right, so
as we're discussing here, it can't be a physical issue, because if I can ping the website so I can ping the website by the I P. But not its domain name. Then I can't have a physical issue because obviously I've got some kind of connective ity. It wouldn't be a D h cp issue because I have an I p address. I can ping
the website, so that's not an issue.
There's nothing application related here that we're talking about right now. And then that leaves us with D. N s issues or potential D. N s issues. Remember, D N S translates an i P address
into a name, and vice versa. So if I can ping the Web sites I p address but not paying the name of the website, then it's likely I have a D. N s issue. So I know that was very brief. I know it wasn't deep again. These were just some foundational things that you want to take into consideration is you troubleshoot systems and
we'll start working with these tools like Callie clinics.
So we touched on physical troubleshooting basics. We talked very high level network troubleshooting basics,
and we looked at a few things that you can do with respect to service import status checks and the reason we wanted to stay high level here today is because there are so many different things you can run into so many things that you could see it you're working with these tools sets that it's almost impossible to teach you how to troubleshoot all of those things. And so take these
fundamentals. Take these core
practices with you is you're working on these tools as you're learning the systems and make those kind of your starting points as you're doing your troubleshooting. So I want to thank you for your time today, and I will look forward to seeing you again soon.
Up Next