Time
57 minutes
Difficulty
Beginner
CEU/CPE
1

Video Transcription

00:01
Welcome back. Here we are in our first lesson on testing network connectivity.
00:07
Our objectives for this lesson include taking a look at some command line utilities like I P Config,
00:13
Ping Trace Route and Telnet.
00:18
First, let's take a look at I p. Config. This stands for Internet protocol configuration.
00:23
This is going to display our network configuration on our local system.
00:27
We can also use it to release in renewed DHC P addresses.
00:32
G eight CP dresses are assigned by a central server or networking device to nodes or systems that are connected on the same network.
00:41
Running I p config by itself will display the I P address, submit mask and the default Gateway.
00:47
And if you add slash all afterwards, it's gonna display more information such as the physical or Mac address, and the D. H C P server is connecting to.
00:56
We'll see some more options when we take a look at this inside of our demo.
01:03
Next up is the Ping utility. This tests and activity to another computer network device or even a website. It uses thebe TCP slash ip protocol and also uses Internet control message protocol, or ICMP packets,
01:18
and it sends these packets to the network device or host and waits to get a response back.
01:23
It also calculates if any packet loss has occurred and the average round trip time to determine Layton Z to the host.
01:33
Next step. We have trace route,
01:34
whereas Ping will just go to the final host or destination and wait for a response.
01:41
Trace Route checks every network device or router along the route to the destination and displays it.
01:48
It also uses ICMP packets, and we'll test the destination with three tests or probes.
01:53
It also calculates the time to live or t TL or the round trip time to that network hop.
02:01
And finally, we have telnet. This is a protocol that we use to interact with Roe computers, and we can use it to test and create a TCP connection to the host on a specific port.
02:13
Once the session is established, you can use it to interact with the remote system.
02:16
For example, you can tell net to an email server and actually create and sending email using telnet commands,
02:23
and you can see on our screen shot where I've tell mated to this I P address over port 25.
02:29
If you look at this inside of a window system, the Telnet client isn't there by default and typically requires installing it as it's an additional feature of Windows that does it for the basics of our commands that we're gonna learn in this lesson. Let's jump over to our workstation and test them out.
02:45
Here we are on our Windows 10 workstation named W S 01 In first, we need to open the command prompt.
02:52
If you've never opened it before, you can click on start search for command problem
02:55
and open it from the list of applications that finds
03:00
now. I already have a session opened, so let's go ahead and switch over to it
03:04
first. Let's take a look at our local I p configuration using the I P config command running. Just I Pekan fake will get back our I P address, Submit mask and default Gateway.
03:14
You can see here r I p addresses 169 dot to 54.40 at 201
03:20
Now the 169 dot to 54 address is an EpiPen address which stands for automatic private I P address.
03:28
This is the I p address you get if you do not get one from a d h c p server.
03:32
So if you see this, that means your system is either not on the network. Or maybe the D H c P server is having an issue, and you are unable to get an address from it.
03:44
If you think the network issue has been resolved or the D H. C P server is back online, you can run i p config slash renew
03:51
an attempt to get a new I P address.
03:53
Now, in my environment, I don't have a d h c p server to get an I P address from, so I'm not going to run this as it's just going to time out.
04:00
But just know if you're on the network and you're not getting an I P address from your d. C. P server, you can't attempt to get a new one by running slash renew with the I P Config command.
04:10
Instead, I'm going to open the network connection control panel and go sign a static I p address. I get there quickly from the command prompt by running in CPI a dot CPL
04:20
and here I have my Ethernet network adapter
04:24
minute to right, click on it
04:26
and choose properties
04:28
going to go to Internet Protocol, Version four, option here and select properties
04:33
and you can see it's already set to obtain an I P address automatically, which is what you would do if you want to get an I P address from the D. H C P server.
04:43
Instead, I'm going to check this radio button here to use the falling I P address
04:48
and I'm going to set a static I p address for the system.
04:54
Let's go ahead and click on OK,
04:56
close.
04:57
Let's go back to our command. Prompt.
05:00
I'm going to up arrow inside the command prompt to get back to my previous command. Let's run i p config again and I've got my new statically assigned I P address.
05:10
Now, if you want to see more information about your network card or network information you received, you can run I p config slash All
05:16
here. You can see we get a description of the network device, the physical or Mac address of it if we have d HCP enabled
05:24
as well as our DNS servers.
05:26
So just by running all you can get a little bit more information, including R. I. P V six address.
05:31
Let's go ahead and clear this screen
05:33
now there were on the network. Let's test connectivity to some other devices
05:39
for this. We're going to use the ping utility
05:41
now. One thing you can do with the Ping Command is test and verify that your own TCP I p. Stack is working by pinging your local address of 1 27.0 dot 0.1.
05:53
If you get replies back, this manger local coal network configuration is up and running correctly.
05:59
I personally have never seen this failed, but it's always a good thing to test if you're running into some weird network configuration issues.
06:04
Now we just configured our static I P address with our default gateways. Let's see if we can ping get and have connectivity to it,
06:14
and that looks good as well. We got four replies back from our gateway and is relatively nearby, with a round trip time of less than one millisecond. Now, in addition to testing network connectivity to network devices, you can also test things like host names or websites. Let's go ahead and try a website here.
06:30
We're going to paying google dot com and we get a reply back. We see the round trip time is a little bit bigger, but again, we were sent four packets and we got back. So we're not losing any packets along this network path, so it's really good to see
06:46
one thing to note is not all host or network devices allow. Replying back to ICMP packets,
06:51
for example, the default Windows firewall actually blocks them. So if you ever try to ping a Windows host that she knows on the network and don't get a response back, But you know the servers up and running. One thing to definitely check is the local firewall.
07:05
For example, we just pained google dot com. Let's try another website
07:10
and we'd see we got an I P address.
07:13
But our request are starting to time out.
07:15
This means that being dot com is not going to respond to our ping requests, but I do know the website is up and running. Could easily open a rep browser and go visit it and you can see down. Here are it's statist. Exchange it a little bit as well we sent four packets, but we didn't receive any back, so we had 100% packet loss.
07:31
The default Ping Command will just send four packets. You can't increase this if you want, but one thing I typically do is add the Dashti parameter.
07:42
This is going to continue pinging the remote host and getting back
07:46
responses until you break the command using control. See,
07:50
this is really good. If you're may be waiting for a device to reboot and you want to see when it comes back up, or you just want to get statistics over a period of time to see if there is intermittent network connectivity issues going on.
08:05
For example, let's jump back over to the network connections.
08:09
I'm going to disable my network card
08:11
and we start getting failures.
08:16
If we enable it again
08:20
and go back to our window,
08:22
we'll start getting responses back
08:24
so you can see this is again really good, too.
08:28
Test connectivity to remote host and see if you have consistent connectivity to it
08:33
in a press control, See to break the command
08:35
and you can see we actually had 20% packet loss when we disabled the network card.
08:41
It's good and clear this screen again
08:43
now. So far we've verified our local I. P configuration is up and running and we're on the network, and we tested connectivity to a single remote host.
08:52
But what if you're having intermittent issues connecting to a remote host and you want to see everything in the path to that host
08:58
as you suspect, something else is causing an issue there.
09:01
For that, we can use the trace route command.
09:03
Let's go ahead and run a trace route out to our WiFi router that we saw in the last lesson. That's our last top. Before we go out to the Internet,
09:13
we're gonna start seeing results from the three probes that we're sending out.
09:18
1 72.16 dot three of that one is our default gateway, which makes sense. It's the next top in our network path,
09:24
and here we see a couple Asterix or stars. That just means the router did not return our expired. Time to live value,
09:31
and you'll see that occasionally not everything is going to give a response back in the path,
09:35
but it's going to continue and we'll get responses later down the network connection.
09:41
And finally, our third hop. There is our WiFi router.
09:43
Let's run trace route back for our website so we could get a little bit more information
09:50
again. We're gonna hit the default gateway and
09:52
follow the path outside my local network.
09:56
And now these tin 0.9 and 100.1 26 are going out through my local Internet service for Ryder
10:03
and you can see occasionally the trace route Command will also perform name resolution against I P addresses and give us actual host names. Here, you can see host names of some routers and you can see my I S P is Cox Communications.
10:18
Finally, once it gets out to the public Internet, we're going to finish up here and get our final response back from the Google Server
10:26
and you can see in this trace route results. We had two times where we had requests timed out, but again, not to worry. It's just gonna continue along the path and give us a much information as they can
10:37
Now, I mentioned trace route here is performing some I p address name resolution to give us actual host names. But if you didn't care about that and wanted just I p addresses. You can add the dash d parameter
10:50
and have it not performed DNS lookups
10:52
and a quick correction there. The Dash D needs to come before the host name
10:58
You can see this time we just got back I p addresses. We did not get the names of some of those devices back if it was able to perform the name resolution.
11:07
Let's go ahead and clear the screen again.
11:09
Finally, let's take a look at Tel. Net. We're going to use this to create a connection to a remote system over TCP
11:16
to a specific host name or I P address and pork combination.
11:22
Remember, we do have our server, 01 system inside this demo network. Let's go ahead and try to tell Mitt to it over Port 25 which is used for email services.
11:33
And once we make thes successful connection, we have a prompt here where we can actually interact with that remote system.
11:39
Like I mentioned in the slides, you can actually use Telnet to create email messages and send them to and from a server.
11:48
Now this session would eventually time out, but If you need to break out of it, you can do control, plus a right bracket.
11:56
And when you get to this interactive, prompt type, quit.
12:00
I'm going to use the up arrow to bring back our previous command.
12:03
Also have a Web server running on this remote server, So let's go ahead and try poor 80.
12:09
You see, we also made a successful connection, but there's no system for us to really interact with, so we just get a blank line here with the cursor. That's OK. That means we still made a successful connection to that remote server over poor 80.
12:22
So we verified we can make a remote TCP connection to that server over that specific port.
12:28
Let's go ahead and break out of this telnet session as well.
12:31
Let's try a different port that I know we're not gonna be able to connect to, so you can see what a failure looks like. It's going to attempt to make the connection,
12:39
and it's gonna come back and say it couldn't open a connection to the host on that specific port. So if you know something is up for running that can respond back to a TCP connection. You can use the Telenet Command to verify if you can connect to it and make that TCP connection.
12:54
If I knew these server was up and running and Port 80 was available, that's hosting our website. But my connection failed. That would point me to something between the two system is causing an issue could be a host level firewall or a network firewall that's blocking the connection. At that point, you can then use the trace Route Command to find everything between the two
13:13
and start investigating each of those systems
13:16
that does it for a demo. Let's jump back to the slides and wrap this up.
13:22
Coming back for our demo. I've got a quick quiz question for you. What command is used to get a new D HCP address
13:30
and the answer is I p config slash renew
13:37
That does it for this lesson. In this video, we discussed
13:41
how we couldn't verify our network configuration
13:43
how we can test connectivity with the ping utility.
13:46
We verify our network path using the trace route command
13:50
and finally, how we can test host and poor connections using Tell net
13:56
coming up next, we're gonna take a look at a very important subject of how we contest domain name resolution.
14:01
See you in the next episode.

Up Next

Network Troubleshooting and Tools

In this course, we will learn basic network troubleshooting using command line tools in a Windows environment. We will learn to verify local network configuration and test connectivity from our local system to other network resources.

Instructed By

Instructor Profile Image
Jeff Brown
Instructor