Packet Tracer Lab 17.7.7 Tutorial (Cisco ITN)

hello everyone in this video i'm going to go over the packet tracer 17.7.7 lab for the cisco intro to networking course and this lab is called troubleshoot connectivity issues and we're going to use some of the show commands that we learned in the last lab important things to notice here are the addressing table we're going to refer to this quite a bit throughout this lab our objective is you will troubleshoot and resolve connectivity issues if possible otherwise the issues should be clearly documented so they can be escalated so moved up the command chain to somebody else that can handle it our background users are reporting that they cannot access the web server after a recent upgrade that included adding a second dns server you must determine the cause and attempt to resolve the issues for the users clearly document the issues and any solutions you do not have access to the devices in the cloud or the server escalate the problem if necessary and they give us a few things here we've got a username and a password that we're going to use and we'll need that as we move along okay so first of all we are told in the instructions here on pc1 open the command prompt so i will click on pc1 here and i want to go to desktop command prompt and there i am enter the command ip config to verify what ip address and default gateway have been assigned to pc1 correct is necessary according to the addressing table so i'm going to look at the addressing table for pc1 here here's what the addresses should be and let's take a look at what they actually are on pc1 so here's my ip address 172 168 1 3 and that's wrong right the second number should be a 16 not a 168 the subnet mask that looks okay the default gateway 172 16 1 1 that looks okay but we need to fix that ip address so we are going to x out of the command prompt here and remember on pcs here in packet tracer we want to go into the ip configuration and we're going to change that 168 and change it to a 16. now i want you to notice the completion percentage here on the lab is at zero and once i click out of that particular box i'm at 33 percent so i fixed a big problem here and then you just click out into the white area of your lab to move on to the next question after verifying and correcting the ip addressing issues on pc1 issue pings to the default gateway web server in other pcs were they successful and then we're given room on our lab if you look here i'm sorry but i just read some of the things right here and we're told um to ping some specific things um the addresses are not listed here but they are right up there in our addressing table so let's try all of this and see what happens so i want to go into pc1 and i want to go back to the command prompt and i want to try some pings here we are first asked to ping the default gateway and we're given the address so let's try it see what happens ping is the command 172 16 1 1. let's see what happens when we do that and then we want to record what happens did it work sure it worked zero percent loss it's all good all right let's try pinging the web server we're just doing some detective work here to see what might be wrong with this network since people were complaining so ping 209 165 2012 let's see what happens when we ping that one all right i have a 25 loss i'm gonna hit the up arrow and ping it again and that's going to turn into a zero percent loss whenever you have like a partial loss it has more to do with tables that are being built through the network and if you try it again typically you'll get no loss all right so that one's good mark that down as being good that one worked put a yes there now we're going to ping pc2 to get pc2's address it is right here in my addressing table ping 172 16 1 4. let's see what happens when we ping pc2 zero percent loss that one worked so put a yes there that one worked no problem let's try pca pca's address is right here so we will ping 172 16 2 3 and see how that goes oh i've got some different messages here 100 loss so that one did not work and you need to write on no next to that one that's a problem area we're going to have to be detectives and figure out why that didn't work let's see how it goes to pcb by the way let's take a second here and look at what's going on we are on pc1 and we're trying to ping we were able to get to the default gateway which is the router we were able to get to the web server we were able to get to pc2 but now we tried pca and we cannot get there so let's try pcb and see what happens so i'm going to click on pc1 again and continue on i need the address for pcb and i'm going to ping that and see what happens ooh looks like we're having trouble reaching that sub network over there okay so that didn't work either all right we'll try to troubleshoot that in a while but let's move on to part c now and see how this works use the web browser to access the web server on pc1 and we're given some direction so let's x out of this on pc1 out of the command prompt and we're going to go to the web browser and it says first enter the url http colon backslash backslash www and we're going to see what happens i'm going to click go and see if i'm able to get there yeah i had to click go again i don't know why that happened but yes i am at the cisco packet tracer page that worked okay but then they want us to try using the ip address instead so i'm going to x out of this and i'm going to go back into the web browser because i wouldn't be able to tell if it worked since the screen was already up so i'm going to type in 209 165 201.2 and i'm going to see is it going to work with the url and the ip address let's see if we can get there and it was successful okay so those both worked and let's move on to part d so we've got a yes here and a yes for the second question document the issues and provide the solutions correct the issues if possible so we already fixed the ip address on pc1 and we understand that we have some problems in connectivity and we've recorded those so let's move on to step two now determine connectivity issues from pc2 on pc2 open the command prompt and we're going to do some of the same things we did on pc1 so here's pc2 i go to desktop command prompt and i want to type in ipconfig to verify the addresses and the default gateway so now we're on pc2 you can tell it's up here in the left of the screen and i want to go up here and make sure that pc2 is correctly configured these are the addresses we should have and here's what we've got on the screen 172 1614 is my ip address the subnet mask looks good how about the default gateway oh look at that the default gateway is supposed to end in dot 1 not 11. so we have a problem here so we are going to x out of here and go into the configuration for pc2 which is ipconfiguration and see the default gateway has the wrong address i'm going to get rid of one of the ones so it matches my addressing table and when i click out of that bar it automatically saves it and now i'm at 66 percent all right now we're going to continue following the directions here we are in step 2 on pc2 okay so you know where we're at and now it says we did the part a after verifying and correcting the ip address issues issue pings to the default gateway to these same things well some of them are the same that we did in on pc one so we're going to try these pings so here i am in pc2 i'm going to x out of the ip configuration and go back to the command prompt and i'm going to try these pings and record what happens you know where are my connectivity issues paying 172 16 1 1. let's see how that works out zero percent loss it worked all right so write a yes next to that one because it worked let's try ping 209 165 201.2 looks like that one's working too zero percent loss everything worked out we got our replies back sent four packets received four packets lost zero okay that's what we're looking for now we'll ping pc1 so i need to get pc1's address and here it is in the addressing table being 172 16 1.3 see how that goes looks good zero percent loss everything worked out let's look at our next step that was pc one let's go to pc a so i'm gonna start typing ping and let's go to the table and find out the address for pca 172 16 2 3. i'll try pinging that oh looks like we have trouble when we try to reach pca right so this is a no and that's good to know let's try pcb pcb is 172 16 2 4. so i'm going to hit the up arrow and change the three to a four to save myself some time it looks like that one's going to be unreachable also so record that that one also didn't work so now let's try navigating on the web again okay let's see how that works out navigate to the cisco.pka and let's see what happens so x out of here and go into the web browser just as we did for pc one and we're going to try typing in www.cisco.pk hit go and see what happens and it works now i'm not going to type in the number right here i didn't quite show you this last time if i type in the number and hit go it's this the number will make it look the ip address will bring me to the same place so i won't be able to tell if it actually worked so i'm going to axe out and go back into the web browser and this time i'm going to type in the address which was let's see um the address i guess i'll go back to the first step to get that here it is two zero nine one six five two oh one two i will hit go and see how that yeah that worked okay so that worked and this one worked document the issues and provide the solutions correct if possible so we're going to keep moving on and see if we can correct our issues as we continue so next it says determine connectivity issues from pca on pca open the command prompt so i'm just going to click out here pc pca now i want to go to desktop command prompt and i want to enter that same ipconfig command and let's make sure the addressing is correct it's a good thing to check as we get going so pca should be 172.16.2.3 and it is the subnet mask looks good and our default gateway also is good so for pca we are good with this everything looks fine after correcting the ip addressing issues on pca which there were none of by the way it says we're going to check these pings again so we're going to ping the web server and see what happens let's see if we can get to the web server oh looks like there's some trouble here let's see what happens okay we had a hundred percent loss to the server so make a note here this did not work keeping this documentation is really important because if somebody else is going to help you solve issues with a network you need to show them what you have figured out you're like a detective with your notes all right let's try the next one ping the default gateway we're trying to figure out where is our problem what is the problem going on so we're pinging the default gateway and let's see how that one goes looks like we're having trouble again so just so you understand what's going on here this is going to be a 100 percent loss let's look at our topology right now we are dealing with pca and we cannot ping the default gateway router one and we cannot ping the server okay so that's what's going on right now there it is 100 loss let's try pinging pcb so can i go from pca to pcb is that going to work so um pcb i need the address for pcb so i'm going to look at my table here ping 172 16 2 4. all right that was all good zero percent loss i'm good to go on that one all right let's take a look at pc one is next so pc1 am i able to get to this other network over here from from this side can i get up to here um this is important information to figure out so back to pca and i want pc1 so ping 172 16 1 3. let's see if pc1 works i suspect we're not going to be able to because it seems like we're having trouble getting to that other network and it's timing out you can see this is not going to work so that's going to be a no and then let's try i'm letting that work its way through all right 100 loss let's go ahead and try pinging pc too so i need the address for pc2 it's right here so ping 172 16 2 oops which one am i doing pc201 172 16 1.4 and let's see how this one goes looks like we're going to have trouble there okay so right now we're just doing the detective work we're just trying to figure out where the problems are and seeing what's going on with that all right so that one did not work either so you can see that pca can only get to its own network it's not able to ping outside to the other network let's try the rest of this and still do some detective work and let's do the um the part where we try getting to the web so we're going to go to the web browser and we're going to type in www.cisco.pka and see if we're able to get to that website clicking go again see if i can make something happen all right this is not working so let's go ahead and try getting there with the web address let's see where that is again it is right here two 209 165 201.2 let's see if we can get there with the web address it's timed out this is not working okay neither one of those worked so we need to see if we can try to correct this so let's go ahead and it seems as if there's trouble at the router so here's our router so let's look at the router using ssh from one so remember ssh is a secure way to access that router so on pc1 i want to go to i'm going to x out of this and i want to go to um telnet ssh which is down here in the menu and i don't believe we have gone there in packet tracer until right now it's right here telnet ssh client so i'm going to click in there and at this part we want to type in the ip address which is 172.1611. that is the router's ip address and our username remember at the beginning of this lab we were told a username and a password and here they are so we want to type in capital a dmin 0 1 and we want to try to connect using ssh and it's asking for our password which is right here at the beginning of our lab we were told to get to router 1 using ssh here's our username and password so cisco one two three four five as usual when you type passwords in in packet tracer labs or in on actual routers they don't look like you're doing anything trust that it's happening i get my message of the day and here i am in router 1. so we're trying this what we want to do now is um i want to look at the interfaces so i want to try looking and making sure that the interfaces are correctly configured so i'm going to type in the command show interfaces and take a look at how this is set up now um looking at g00 i want to check the address for g00 so here's gigabit ethernet g00 and the address is 172 16 1 1. let's make sure that that's okay so here's the router and i have gigabit ethernet g00 is that the right ip address and it is and my subnet mask is backslash 24 which matches this remember 8 times 3 and i have 24 as my subnet mask okay that looks good i'm going to hit the space bar here in this window so i can see more let's make sure g01 is all good because i'm having trouble leaving my little network over there so here's where the information about gigabit ethernet 01 starts and the address internet address is right here let's make sure that that one is right 172 16 3 1 is what it's configured as but look here in my addressing table it should be 2.1 not 3.1 i need to fix that so here i am in the command prompt i want to just hit the spacebar a few times to get done with all that information because i found a problem here i want to fix so i want to go to configuration mode so down here i'm going to type configure terminal and i need to change that ip address on gigabit ethernet 0 1. so now i'm going to type interface g 0 1 and you can see that my prompt changed and i'm now in config mode for interface g01 and i want to type in the correct ip address so id address 172 16 2.1 255.255.255 i'm going to double check that that's right before i hit enter and i want you to take a look at the score because i think we're going to get 100 right now and there it is so i have fixed another problem okay so um let's see let's go ahead now and let's look at um some pinging let's see how things go now so i fixed some things um let's x let's just click on the white area here and let's see now um let's try pcb this time if we fixed everything pcb will be able to get around here in the network let's see what happens i'm in pcb desktop command prompt and for part four here i want to enter the ipconfig command to see if my address is correct for pcb well i'm going to tell you i already checked it and it's good okay so let's move on to pinging let's try the web server and see what happens ping 209.165.201.2 and this is working this time zero percent loss let's try the default gateway that router wasn't working before from this part of the network let's see if it works now and it does work all right we couldn't get to pca from this network before let's see if we can get there now so i'm going to ping pca's address which is hold on let me highlight this so we don't lose our place pca is 172.16.2.3. see if that works it does work all right let's try pc1 is next ping 172.16.1.3 let's see how that works pc1 that one's good let's try pc2 i'm going to hit the up arrow and change that 3 to a 4 and let's see if we can get to pc2 also works and now we are asked to so things have been fixed we did a good job the next thing step c is we want to navigate to the web browser and see if this is going to work so let's x out of this and go to the web browser to the internet and let's try going to that website the cisco.pka website see if we can get there hostname is unresolved we cannot do this all right let's try the um ip address instead so that ip address i have to keep hunting for where is that address okay so i'm going to try type oh let me x out of this so i know if this worked or not i'm going to type in 209.165.201.2 let's see if this works all right that one worked so i can get there with the address but i cannot get there with www.cisco.pka all right that's interesting um so we need to document some solutions or some problems and we can only get to from from pcb we can only get to the cisco packet tracer website using the um the ip address and not using the domain name okay so we're having trouble getting there so we're going to just document that there's a problem though we don't have access to be able to fix that so that's the kind of problem that would be sent back up to somebody who has more power in this network to make changes so we could not resolve everything in here because we don't have the administrative power to do that okay now if you go back and you verify that the pcs can access the web server and you take a look at other connectivity you're going to see that a lot of your a lot of your problems have been fixed but you'll need to send some things off to somebody who has more administrative powers okay that is it for this lab

Channel: Packet Tracer Tutor

Views: 302

Keywords:

Id: BpUGtWsIS1g

Length: 31min 4sec (1864 seconds)

Published: Sun Feb 21 2021