Network Troubleshooting using PING, TRACERT, IPCONFIG, NSLOOKUP COMMANDS

hello and welcome to sake tech so this video is about a series of network troubleshooting tools that you can use in command prompt to troubleshoot your network and get some information on your network so in this video we're going to go over four commands the IP config command the nslookup command the ping command and the trace RT the trace route command so let's start with IP config for now okay so the first command that I want to go over is the IP config command the IP config command is a very common and very useful tool it displays the current information about your network so it will give you basic information such as your IP address for the computer that you're stationed on it will give you the IP address of your router it will tell you where your DNS servers is where your DHCP servers are so let's type in the basic IP config command to start and usually your local area connection is called the Ethernet adapter local area connection so this is the connection where you plug in your network cable the rj45 network cable connects to the to the jack behind your computer and this is the information pertaining to that connection any way you can get your IP address on the screen which is 192.168.1 point 1 0 it's also called the ipv4 address you can get your subnet mask right here and you can get your default gateway address here the default gateway is your router so now I know the eye a dress for my router by looking at this screen as you can see you don't get much information about your local area connection here so what I'll do is I'll clear the screen type in CLS to clear the screen and type in ipconfig /all to get more in-depth information about your local area connection + enter and let's go back up to the Ethernet adapter local area connection this time as you can see there's much more information present the IP address is still here the subnet mask is still here the router address is still here but this time you can also see where is your DHCP server in my case as you can tell the IP address is the same as the router address that means that my DHCP server is currently residing on the router and then your DNS server my DNS server is also 192.168.1.1 it's the same as my router address that means my DNS server is also on my router so you can see how this tool is helpful in troubleshooting and information gathering information gathering is a part of troubleshooting so you know when it comes to networks DNS DHCP the default gateway the subnet mask these are all important keywords and you can get the information about these guys right here so if you're trying to troubleshoot the DNS server you can beforehand type in the IP config command and find where the DNS server is so in my case it's in the router so I would go to the router settings to tweak the DNS server okay so let's let's move on to the next command this is all I want you to know about the ipconfig command clear the screen and let's get on ok so one of the commands you'll be using a lot for network troubleshooting is the ping command ping command allows you to send a signal to another device and if that device is active it will send a response back to the sender now for those of you who are interested in the details of how this works the the ping command is a subset of the ICMP internet control message protocol and it uses what is called an echo request so when you ping a device you send out an echo request and if the device you pinged is active or online you get an echo response so already you can tell why this is a good command to troubleshoot so for example if your router is down and you try to ping it and you get no response then you know that the router is what is giving you problems so let's say let's run this command a couple times and see what kind of results we get so let us let us ping my router ping one 92168 dot one dot one press enter and let we will analyze the the printout here that we got so what happens is we send out four packets to the destination and the destination responds back with the same four packets so as you can see here 1 2 3 4 so this is a reply from 192 168 1 and 1 that is my router we sent out 32 bytes of data and we got back 32 bytes of data and we got it back in less than 1 milliseconds down here you get a summary so it says packets and 4 packets received 4 packets lost zero so that means this is a stable connection and then there's another some statistics here that is not important so this is how the ping command works it sends out an echo request using data packets of of miniscule size and then you get a response and you know that the other device is actually alive so let us paint on Google www.google.com and see what happens so we got a similar print up let me just bring this to the top and that as you can see this is the IP address of Google and that is where we got the response from as usual we sent out 32 bytes of data but as you can see because Google is far far far away and not in my basement it took twenty nine milliseconds to send r2 to get a response from Google and if you look down here again statistics our packets were sent for received for lost zero so the connection was stable finally let's ping a device that doesn't exist this is going to yield the same kind of results if a device wasn't actually working so if your daughter was down and you pinged your router but uh you are not going to get a response from it so let's say ping one nine two one six eight two 200 press Enter so we're opinion right now and the request was timed out because that device does not exist as you can see the ping command is retrying it's going to retry four times the first packet didn't go through second second packet didn't go through the third packet and the fourth packet did not go through and as you can see at the summary packets sent four received zero and lost four so it was a hundred percent lost the signal does not exist so if you ping the device you get no response and you lose all the packets that means the system you're trying to reach is not connect to the networks having network problems and this brings us to the end of the ping command let's clear the screen and move on to the next command so the next command is the trace our T command so what the trace our T command does is it lets you see step by step a route a packet takes to the destination that you specify so if you send a packet to Google calm before the packet actually reaches Google comm it goes through a couple of routers to reach the destination so it'll go to your router then it will go to Verizon or Comcast router and from there it's going to go to all kinds of different routers before it reaches Google servers so you can also use the term hops instead of routers so if it takes 10 routers to get to google.com you can instead say it took 10 hops so how do you do how to use this this command for troubleshooting let's actually run the command and see what kind of results we get so I'm going to run the trace or T command I'm going to trace google.com ok so as you can see we're getting a list of each of the routers that we're hitting as we are closing in on google.com and up here will tell you what you're tracing and it'll give you the IP address for a Google ok so the trace is complete let's see we have 1 2 3 4 5 6 7 8 9 10 11 we went through 11 hops 11 routers before we actually reached google.com now if you look up up top here the first router that we actually hit was my own router can tell by the IP address right here 192 168 1 . one and it's the wireless broadband router data home the next one because I have my service through Verizon was Verizon router so it clearly goes step by step through all the hops and then after 11 hops we were at google.com what what what is the significance of this let's say your home network was perfectly fine but there was a problem with the verizon routers you can run the trace RT command and if if there's any problems here it will actually tell you what the problem is it could say things like request timed out destinies destination unreachable or it could also say that in so 16 milliseconds it could be saying like 5,000 milliseconds just to give an example and I don't think you'll ever see that but so if the request times out that means the problem lies with one of the routers that has to do with Verizon and then you can call Verizon and you can tell them hey you guys are having a problem because I know that my router works because I ran the trace RT command so this is the idea behind the trace RT command as far as troubleshooting goes ok so that brings us to the end of this command let's clear the screen and move on to the final command ok so the final command I want to talk about is the NS lookup command this command will fetch the DNS records for a given domain name or an IP address remember the IP addresses and domain names are stored in DNS servers so the nslookup command lets you query the DNS records to gather information so let's say I wanted to know the IP address of google.com I could simply type in NS lookup and and type in google.com press ENTER and what let's analyze this printout so the the first two lines here show you which DNS server was used to get these results my DNS server happens to reside on my router as you can see 192 168 1.1 is my router so that is also my DNS server and the answer that we got was this all these IP addresses here are Google's IP addresses now Google is a huge website obviously it's not going to have one single IP address and obviously the IP addresses will change from time to time but if you type in any of these IP addresses in your browser it will take you to Google com so this is the basic idea behind the nslookup command ok so this brings us to the end of this video and if you guys like the video just click the like button and if you like my videos subscribe to my channel because I will be updating more and more videos of this sort and thank you for watching have a good day guys

Channel: sakitech

Views: 3,912,656

Keywords: nslookup, ping, tracert, ipconfig, network troubleshooting, command prompt

Id: AimCNTzDlVo

Length: 14min 33sec (873 seconds)

Published: Sat Nov 03 2012