WEBVTT - This file was automatically generated by VIMEO 0 00:00:00.300 --> 00:00:03.800 Hello and welcome to this. Cali fundamentals lesson. 1 00:00:03.800 --> 00:00:06.800 I'm very excited to be here with you today. So 2 00:00:06.800 --> 00:00:09.200 we're going to be getting into and talking 3 00:00:09.200 --> 00:00:13.000 about troubleshooting. So you may be wondering how do I troubleshoot Cali? 4 00:00:12.400 --> 00:00:15.600 How do I go about solving problems things of 5 00:00:15.600 --> 00:00:18.100 that nature? Well, the good news is today when you 6 00:00:18.100 --> 00:00:21.500 walk away from this lesson, you are going to have some high level 7 00:00:21.500 --> 00:00:24.500 troubleshooting steps that you can use to ensure 8 00:00:24.500 --> 00:00:27.600 that you're able to successfully overcome problems and 9 00:00:27.600 --> 00:00:30.300 find Solutions. The good news is if you've had trouble shooting 10 00:00:30.300 --> 00:00:33.500 experience with Windows or networking equipment things of 11 00:00:33.500 --> 00:00:36.100 that nature. It's not a lot different. We're just going to 12 00:00:36.100 --> 00:00:39.300 really touch on the basics again and make sure that we all have the 13 00:00:39.300 --> 00:00:42.000 same Foundation moving forward. So one of 14 00:00:42.200 --> 00:00:45.500 the first things that we always talk about is checking the physical and one 15 00:00:45.500 --> 00:00:48.900 of the things that I've run into early in my career was making 16 00:00:48.900 --> 00:00:51.300 sure that everything is plugged in and turned on I can't 17 00:00:51.300 --> 00:00:54.300 tell you how many times I've looked at a system 18 00:00:54.300 --> 00:00:57.600 and discovered that it's all I had some 19 00:00:57.600 --> 00:00:59.400 some funny stories back in. 20 00:01:00.200 --> 00:01:03.700 You know my college days where I was working on trying to get a 21 00:01:03.700 --> 00:01:06.300 console connection into a Cisco device. I worked 22 00:01:06.300 --> 00:01:09.300 on it for about five minutes had a buddy come over and he turned the power on 23 00:01:09.300 --> 00:01:12.400 and then I felt really really silly for the rest of the day, but 24 00:01:12.400 --> 00:01:15.300 that's not a lesson that you easily forget. So always check 25 00:01:15.300 --> 00:01:18.600 to make sure everything's plugged in and turned on does anything smell 26 00:01:18.600 --> 00:01:21.400 burnt. So if it's not your breakfast as we've 27 00:01:21.400 --> 00:01:24.300 got over here if it's if it smells like you've got some 28 00:01:24.300 --> 00:01:27.300 maybe electrical issues or something of that 29 00:01:27.300 --> 00:01:27.600 nature. 30 00:01:28.500 --> 00:01:31.500 Open your device up and see if there's anything going on and make 31 00:01:31.500 --> 00:01:35.300 sure that you don't have any charring or anything of that nature is your 32 00:01:35.300 --> 00:01:38.500 hard disk making funny sounds so, you know, this is maybe an 33 00:01:38.500 --> 00:01:41.700 exaggerated example here, but if you hear scratching scraping 34 00:01:41.700 --> 00:01:44.200 things of that nature suddenly your equipment's not 35 00:01:44.200 --> 00:01:47.200 working, right you may have some hard disk issues. So keep 36 00:01:47.200 --> 00:01:50.400 that in mind and you know, I've run into before where 37 00:01:50.400 --> 00:01:53.500 I've had something like this happening where I've got some cable issues 38 00:01:53.500 --> 00:01:56.200 or the cable is not connecting or it's 39 00:01:56.200 --> 00:01:59.400 not working. Try different physical cables. Try 40 00:01:59.400 --> 00:02:02.700 a few different things to just make sure that you're not having cable issues 41 00:02:02.700 --> 00:02:05.700 or something of that nature. Also. Did 42 00:02:05.700 --> 00:02:08.500 you follow the directions carefully? Did you do steps one 43 00:02:08.500 --> 00:02:11.200 through 10 according to the directions if 44 00:02:11.200 --> 00:02:14.300 you skipped anything go back and check it out. And of 45 00:02:14.300 --> 00:02:17.500 course, you know, just make sure that you start 46 00:02:17.500 --> 00:02:20.200 from the basics every time that you start with the 47 00:02:20.200 --> 00:02:23.300 physical and then you work your way into the networking area 48 00:02:23.300 --> 00:02:23.600 here. 49 00:02:24.500 --> 00:02:27.300 So after you've ensured that everything's connected 50 00:02:27.300 --> 00:02:31.000 everything's running remember some of you may be using a guest 51 00:02:30.100 --> 00:02:33.000 or some type of virtual machine. Some of you 52 00:02:33.300 --> 00:02:36.300 may have loaded Cali directly on to the hardware and you may 53 00:02:36.300 --> 00:02:39.300 not have some of these same issues with respect to what virtual machines 54 00:02:39.300 --> 00:02:41.000 are going to experience but 55 00:02:42.200 --> 00:02:45.700 If you're having network issues or connectivity issues in the physical is 56 00:02:45.700 --> 00:02:47.000 obviously not the problem. 57 00:02:47.800 --> 00:02:50.400 Make sure that you check your network adapter settings 58 00:02:50.400 --> 00:02:53.700 in whatever, you know hypervisor that 59 00:02:53.700 --> 00:02:56.200 you're using a lot of times. You know, what I like to do 60 00:02:56.200 --> 00:02:59.200 is if I'm testing tools or something of that nature, I'll do a host 61 00:02:59.200 --> 00:03:02.200 only connection. But in that instance I shouldn't be able 62 00:03:02.200 --> 00:03:05.300 to get out to the internet or do anything of that nature. So make 63 00:03:05.300 --> 00:03:08.200 sure that if you need to that you have your settings, 64 00:03:08.200 --> 00:03:11.500 you know set accordingly and then do a couple checks. 65 00:03:11.500 --> 00:03:14.200 Can you ping the Google DNS server? Can 66 00:03:14.200 --> 00:03:17.300 you ping you know the IP addresses that should 67 00:03:17.300 --> 00:03:20.200 be pingable on the internet like eight down eight not eight down 68 00:03:20.200 --> 00:03:23.400 eight here. Can you ping Google by name? So those are 69 00:03:23.400 --> 00:03:26.700 some things that if you can ping the actual IP address, but you 70 00:03:26.700 --> 00:03:29.600 can't ping the actual name of a system then 71 00:03:29.600 --> 00:03:32.700 you may have some DNS issues. If you can't ping your 72 00:03:32.700 --> 00:03:35.400 gateway address which you know, we put up here. So when you do an 73 00:03:35.400 --> 00:03:38.200 IP config and if config on a system and you 74 00:03:38.200 --> 00:03:41.600 get a gateway address, if you can't ping that maybe there's 75 00:03:41.600 --> 00:03:44.500 a problem there. So remember be systematic in 76 00:03:44.500 --> 00:03:47.700 the way that you're looking at network issues and connectivity issues take 77 00:03:47.800 --> 00:03:50.200 One thing at a time and you know, don't let 78 00:03:50.200 --> 00:03:52.800 it get on your nerves or cause any stress on your part there. 79 00:03:53.600 --> 00:03:56.300 So once we check those areas, you know, if it's 80 00:03:56.300 --> 00:03:59.500 specific to an application or service there's a couple steps that 81 00:03:59.500 --> 00:04:02.300 we can take there. So if you want to look at a specific service, like 82 00:04:02.300 --> 00:04:05.500 in this case, we look at Apache too. You can use the service 83 00:04:05.500 --> 00:04:08.600 service name here and then status and that'll give 84 00:04:08.600 --> 00:04:11.200 you the the status of the system. It'll or the 85 00:04:11.200 --> 00:04:14.200 service it'll tell you whether or not it's running as you can see here. We 86 00:04:14.200 --> 00:04:17.600 did a start on that and then we ran service Apache 87 00:04:17.600 --> 00:04:20.200 2 status again and then we can see that it's active and working. 88 00:04:20.200 --> 00:04:23.300 So, you know, you can do that if you want to check everything at once 89 00:04:23.300 --> 00:04:26.500 like we've got over here then you can do a service and 90 00:04:26.500 --> 00:04:29.600 then this two dashes their status all and 91 00:04:29.600 --> 00:04:32.400 then I'll give you a running list of everything that's that's currently on 92 00:04:32.400 --> 00:04:35.600 or off. So the plus here means that it's on minus means 93 00:04:35.600 --> 00:04:38.600 that it's not so if you're trying to do something 94 00:04:38.600 --> 00:04:41.200 and it's got a service related to it and 95 00:04:41.200 --> 00:04:44.300 you come in and you see that minus is there you may want to try starting that. 96 00:04:45.100 --> 00:04:49.100 Now sometimes what can happen is is that you may have services that 97 00:04:48.100 --> 00:04:51.400 want to use the same port so you can use 98 00:04:51.400 --> 00:04:55.000 netstat and then the switch here Dash NP 99 00:04:54.300 --> 00:04:57.700 lnt and what that does is it'll 100 00:04:57.700 --> 00:05:01.000 show you the services and the running ports and everything like that. If 101 00:05:00.100 --> 00:05:03.300 you were running Apache 2 102 00:05:03.300 --> 00:05:06.500 and it's on Port 80 and then for some reason you try to use a different, 103 00:05:06.500 --> 00:05:09.100 you know web service or something of that 104 00:05:09.100 --> 00:05:12.400 nature and it needs drawn on Port 80 and there's a conflict you may 105 00:05:12.400 --> 00:05:15.900 need to change the listening port in the configuration file 106 00:05:15.900 --> 00:05:18.200 to make sure that that works 107 00:05:18.200 --> 00:05:21.400 together with Apache to you or something like that. And remember if 108 00:05:21.400 --> 00:05:24.500 you did make changes to the config file, and now you're having issues. 109 00:05:25.300 --> 00:05:28.400 Go back and check that see if you made a mistake look for spelling errors 110 00:05:28.600 --> 00:05:31.500 Etc. And if you can do so always make 111 00:05:31.500 --> 00:05:34.400 a copy of the config file to ensure that if you make a mistake 112 00:05:34.400 --> 00:05:37.100 or have an issue, you can change it back to a known good 113 00:05:37.100 --> 00:05:37.400 status. 114 00:05:38.100 --> 00:05:41.300 And of course with anything when in doubt Google it out, 115 00:05:41.300 --> 00:05:44.500 so keyword searches error message searches things 116 00:05:44.500 --> 00:05:47.300 of that nature are going to be huge as you get into working with 117 00:05:47.300 --> 00:05:50.400 any distribution insecurity in it 118 00:05:50.400 --> 00:05:53.200 in general. You're gonna have to learn to use Google but if you're 119 00:05:53.200 --> 00:05:56.200 going to continue to use Cali and you're gonna want to work with it 120 00:05:56.200 --> 00:05:59.400 and learn more about it, you're obviously going to run into issues from time to 121 00:05:59.400 --> 00:06:02.500 time the forms are a great place to go. There's a great Community 122 00:06:02.500 --> 00:06:05.400 here that maybe had some of the same issues 123 00:06:05.400 --> 00:06:08.100 you've had and and they've spent the time and effort working on 124 00:06:08.100 --> 00:06:11.300 it and maybe you can find a solution there and then, you know try to 125 00:06:11.300 --> 00:06:14.400 use some keyword searches in you know, your 126 00:06:14.400 --> 00:06:17.300 Google searches. So, you know, you know, it's not a network issue. 127 00:06:17.300 --> 00:06:20.900 Maybe you can you know, take away the word network when 128 00:06:20.900 --> 00:06:23.400 you're searching for terms or 129 00:06:23.400 --> 00:06:26.100 something like that like that in advance search or maybe if 130 00:06:26.100 --> 00:06:29.900 you're looking to find things that only include Network then 131 00:06:29.900 --> 00:06:32.400 maybe you insure that it always has the word network or 132 00:06:32.400 --> 00:06:35.200 something of that nature. So Google's your best friend when 133 00:06:35.200 --> 00:06:38.000 it comes to troubleshooting or any search engine of 134 00:06:38.100 --> 00:06:41.800 To be honest with you, but make sure that your patient if anything 135 00:06:41.800 --> 00:06:44.100 starts to get on your nerves and you're starting to have a 136 00:06:44.100 --> 00:06:47.300 hard time step away. Remember you want to enjoy the 137 00:06:47.300 --> 00:06:50.400 things that you're doing. You want to enjoy working with these toolsets. You 138 00:06:50.400 --> 00:06:53.600 want to enjoy learning and and things of 139 00:06:53.600 --> 00:06:56.100 that nature. So if you start to experience a high level of 140 00:06:56.100 --> 00:06:59.500 stress or you're getting angry at the situation step back, 141 00:06:59.500 --> 00:07:02.300 sometimes the breath of fresh air and a fresh 142 00:07:02.300 --> 00:07:05.400 set of eyes, once you you know, you kind of clear your head and come back is 143 00:07:05.400 --> 00:07:07.000 the best way to solve a problem. 144 00:07:07.700 --> 00:07:10.300 So with those things in mind, let's do a quick check on 145 00:07:10.300 --> 00:07:13.500 learning. So if I can ping a website by its IP 146 00:07:13.500 --> 00:07:16.200 address, okay, so I can ping the IP address of the 147 00:07:16.200 --> 00:07:19.300 website, but now it's domain name. I likely 148 00:07:19.300 --> 00:07:20.400 have what kind of issue? 149 00:07:22.600 --> 00:07:23.300 all right, so 150 00:07:24.200 --> 00:07:27.200 As we're discussing here, it can't be a physical 151 00:07:27.200 --> 00:07:30.200 issue because if I can ping the website so I 152 00:07:30.200 --> 00:07:33.300 can ping the website by the IP but not its domain 153 00:07:33.300 --> 00:07:36.600 name. Then. I can't have a physical issue because obviously I've 154 00:07:36.600 --> 00:07:39.600 got some kind of connectivity. It wouldn't be be 155 00:07:39.600 --> 00:07:42.300 a DHCP issue because I have an IP address I 156 00:07:42.300 --> 00:07:46.600 can ping the website. So that's not an issue. There's nothing 157 00:07:46.600 --> 00:07:49.400 application related here that we're talking about right now. 158 00:07:49.400 --> 00:07:52.700 And then that leaves us with DNS issues 159 00:07:52.700 --> 00:07:56.400 or potential DNS issues. Remember DNS translates 160 00:07:55.400 --> 00:07:58.400 an IP address into a 161 00:07:58.400 --> 00:08:01.700 name and vice versa. So if I can ping 162 00:08:01.700 --> 00:08:04.400 the website's IP address but not paying the 163 00:08:04.400 --> 00:08:07.700 name of the the website then it's likely I have a DNS 164 00:08:07.700 --> 00:08:10.200 issue. So I know it was very brief. I know 165 00:08:10.200 --> 00:08:13.500 it wasn't deep again. These are just some foundational things 166 00:08:13.500 --> 00:08:16.500 that you want to take into consideration as you troubleshoot systems 167 00:08:16.500 --> 00:08:19.400 and start working with these tools like Kelly 168 00:08:19.400 --> 00:08:22.500 Linux. So we touched on physical troubleshooting Basics. 169 00:08:22.500 --> 00:08:24.000 We talked very high level. 170 00:08:24.200 --> 00:08:25.700 Network troubleshooting basics 171 00:08:26.200 --> 00:08:29.400 and we looked at a few things that you can do with respect to service 172 00:08:29.400 --> 00:08:32.200 and Port status checks. And the reason we wanted to stay 173 00:08:32.200 --> 00:08:35.200 high level here today is because there are so many different things. You can run 174 00:08:35.200 --> 00:08:38.200 into so many things that you could see as you're working 175 00:08:38.200 --> 00:08:41.900 with these toolsets that it's almost impossible to teach 176 00:08:41.900 --> 00:08:44.700 you how to troubleshoot all of those things and 177 00:08:44.700 --> 00:08:48.300 so take these fundamentals take these core practices 178 00:08:47.300 --> 00:08:50.300 with you as you're working on these tools 179 00:08:50.300 --> 00:08:53.300 as you're learning these systems and make those 180 00:08:53.300 --> 00:08:57.000 kind of your starting points as you're doing your troubleshooting, so 181 00:08:56.100 --> 00:08:59.300 I want to thank you for your time today and I 182 00:08:59.300 --> 00:09:01.700 will look forward to seeing you again soon.