5 hours 33 minutes

Video Description

Troubleshooting Wireless and Wired Connections Part 5 In our final lesson on Wireless and Wired Connectivity Issues we examine digital tools and how they help us diagnose connectivity issues. One such tool is PING, it confirm connection between two network end points using the Host name or IP address. PING can also provide information about the communication ability of the path that is traveled between those two networks end points. For example we examine how echoing works, how to test connectivity to a specific known device on the network such as a switch for a given server, or a router and what that information indicates about internal and external connectivity on its failure. Another is Trace route where we demonstrate how it work and examine what network information it reveals. Or another tool such as wireless locating software and what you can learn about signal or communication strength of your wireless network.

Video Transcription

Now we've talked about our physical tools. Let's go ahead and move on to our digital tools. Now, our digital tools are going to be the different applications. And the different commands that we're gonna be using on our computer to troubleshoot are wired and wireless connective ITI. Our first tool is going to be paying now. Paying is a tool that will use in command, prompt
and paying. Allows us to check and see if we can make a connection
from point A to point B. We can paying using a host name or weaken paying using an I P address and paying simply tells us Hey, we're knocking on the door of this device. Can we see it? Can we talk to it now? Some devices may have Ping Ping may not work on these devices because they have what are called ICMP.
Echo requests, disabled
paying sins and ICMP echo request to a device. And if it successfully the device successfully receives the pain and it is set to respond to them, it'll respond back and say, Hey, yeah, I see you
so pings were useful when we're trying to determine at what point in our network there an issue? Maybe.
I say we have our computer here inside of our network, followed by a manage switch that we have an I p address on
followed by a,
server here are so sorry. Followed by our router here,
followed by the internet. So I have a router here and then off of this manage switch. May we may have a couple servers.
So our computers plugged into this switch was flood, which is plugged into this router, which is which is connected to the internet. And our computer says we don't have connective ity. Well, how much? Where is our connectivity? Lacking where? Where does our connectivity stop?
So we can if we know that i p address of our manage switch here or we know an I p address of one of the servers
are we know an I p. Address of this router. And we known I p address out on the internet somewhere. So we send a paying request, we try to paying the switch, or we try to paying one of these servers that are connected to the switch. If we can successfully get to if we can, successfully paying one of these servers,
our recon successfully paying this switch. That means we can connect where successfully connected to through our cable to the server are sorry to the server and threw the switch. So we know that because we can paying
so far, we're good. At least up to here. Now, there are some settings on this switch which we may need to configure. But we do know with the pain that we can at least get to this point.
So let's say okay, I can paying to the switch. I complain to the server. Let me see if I've been paying the next location. So I'm gonna try and send a paying request to the router
Cinda pain to the router andan except in its successfully response. So that means I can connect out to this far everywhere inside my local network is now letting me connect.
So then I send a final paying request to a server out on the Internet and it tries to go out, and I don't get any response back on. And I paint an IP address. So to try toe, eliminate it being possible the NS issues. But I tried to paying this. I p address out on the Internet and I can't connect.
So what this is done for us is we now know
that are connective iti. We have a SZ physical or have a wireless connection, at least between our computer and the router. There's something there is some sort of setting either on the router itself, going outbound or some sort, or some problem between the router and the Internet
that is existing. So we've trouble. She we are Ping Command has helped this trouble shoot down.
So what part of our network the issue lies on And then we can use that in order to make better informed decisions and then go through and continue to troubleshoot.
Our next command is going to be, Iike, Peak and fig. I peek and fig is going to let us know our current I P configuration is going to give us information such as our I P address, such as 1 92.1 68 1 dot whatever will say three for the situation
gives our I P address. It will give us our default gateway
and our Mac address. If we use an I p config all we could see our physical addresses. Well, we can see what our D N s servers are. We can see if, if it is applicable, weaken. See even
the other network interface cards in our computer. Not just our wired connective ity, but maybe a wireless wireless car that we have in our computer. I p config is gonna give us a lot of those different i p configuration information.
Now, if we run an I peek and fig
and we noticed that we're getting a an address that starts with 1 69 dot
the rest of our I p address. Then we're more than we're getting tonight. Pippa address that a pip address means that for some reason, we're not getting an i p address from D H cp. Maybe our were set to Maybe we are are rather set to not issued the HCP. Maybe we have a server here which issues D a C p,
which is off line. Or maybe it has stopped issuing requests because it thinks that it's out of I p addresses.
Whatever the case, for some reason, we're not getting an I p address. So we're getting in a pip address. I peek and fake. And also we can also release and renew an I P address. So say we connect to a print one particular switch and then that switch goes down or we connect to a different network
on We need to release our I p address and renew a new one
if we've connected to a different network. Or maybe we want to try to get a new I p address. Now, if we're using the HCP or if we have that is giving us an I P address, it may give us the same i p address, but it still may be worth our while to release and renew. If we're using a static I P configuration on our computer
release and renew isn't going to do anything for us. We'll get an error that says that
this adapter is not in the correct state toe. To form this action, which means release and renew our actions related with D h C P I p config release and means that I'm releasing this I p address that D H CP gave me
and then I p config renew means that I'm gonna try to get a new I P address. I'm gonna try to renew an I P address
from D H Cp to see if it's gonna give me a different one. So if those settings air static or not, if our I p address settings on our computer are static, we're not pulling a d h c p I p address. We're using static settings, so release and renew won't be able to do anything. Thus, the air message will get
next. We have trace route now. Trace route is a bit different from paying. Trace route actually tells us every step between us and where we're trying to us and the other address that we enter. So if we run a trace route command and enter an I P address, say,
between us and somewhere out on the Internet,
trace route is essentially going to give us all the information about all the hops between us and that location.
So we have our computer, and then we're connected out to our router, which connects out to our Internet service provider server, which connects out to eventually another server that we're trying to get to with the couple's different steps. In between, we run a trace route command because we're having trouble getting to that final location.
A trace route will let us know if there's any bottlenecks
that are stopping our connection because it's going to tell us information like how long our connection is at a certain location. So we run a trace route command and we can get
to a router. Were good. You get to the next point, you can get to our I S P, but then it stops
sauce for a long time,
and then it times out. We know that our connection is good all the way up to this point, but then passed that point. Something's going on that's not letting us go on any further or either. It's throttling us down for some reason. So trace route is whereas a ping request will
you will just tell us yes or no. It'll say I got a response or I did not get a response.
Trace route will essentially go through every single one of the points between us and another location and say, Hey, how long are you? Are you? Am I sitting here? How long is my data sitting here on? Can I can I get a response from you. Can you let me know your I P address? Can I resolve here I p address to a name
so that trace route, maybe a bit
more intensive? It may be a bit more in depth in depth steps in order to see if we can figure out what's going on and why we can't connect to a certain location or where a bottleneck is in our connection to a particular location. Next we have Nets. Stat.
Net stat is going to give us information as faras. What type of what connections we have to our computer,
what connections there are over two certain ports. What connections? We have two different servers, not only on our network but the Internet. Sonett stat is a good command to be able to use in order to determine what type of connections we have going on with our computer. If we want to see if there's any unnecessary connections may be going on,
maybe we're tryingto dive down into some deep analysis of maybe some remote connections that are trying to connect to us.
We may be able to use this net stat and get some, and we can't even get some statistics on these connections and see how much information we've sent out. How much we've received and where we've sent this information to
nbt stat is net biostatistics. Nbt stat Will gives information about bios, names that we've resolved net bios, connections that Net bios, information that we've received by sending out requests over Net bios. BIOS is essentially a predecessor to
eyes, a predecessor to D. N s its windows de ns for his Windows D. N s.
It's not uses it extensively. It's not used is widely because we use D. N s now domain name service. But Net bios is still out there. It's still used in networks on it still is a part of how our computer resolves names so that by NBT stat will give us information on our bios on our net bios connections.
Now we have our net command now. Arnett, Command, we can't just use by itself. We're not command prompt and we type in net. It's not gonna do anything for us. We'll need to type in one of the fault one of the following or even more qualifiers for net. We have net used that uses going to give us information on our current network connections.
Not like Net Stat does like
nets. That gives us information on our current data. Where we're sending it to who were sending information from net use is more of our network shares. So current folders that were connected to on the network current network drives that were Matt to information like that
Net view is going to give us information on the current servers and shares that are available on our network
nets. Statistics will give a statistics as faras data and packets that we've sent and received, but we also need to qualify as server or workstation.
And then finally, we have our wireless local wireless locator. A wireless locator eyes a tool that is typically software that we will install on our computer in order to use in conjunction with determining our wireless network strength. We could install this software on our computer
and then use it and navigate around our house or navigate around our business
and see and map locations where our wireless connection is weaker or a whiles connection. Maybe, maybe really strong or we're receiving a lot of interference. Using our wireless locator, we can see where interference may be coming in from other wireless access points.
We may be able to see what frequencies or what channels would be better to switch to with all wireless access point.
So it'll show us a lot of information as far as how our wireless network is performing and what maybe what we may be able to do in order to improve our wireless connectivity and our improved the strength of our radio frequencies for the wireless access points on our network.
So thank you for joining us here today on cyber dot i. T. Today we talked about troubleshooting different wired and wireless networks with their appropriate tools. We talked about everything from a low radio frequency strength on our wireless to intermittent connective ity on Wired networks. We talked about physical tools such as cable strippers and punch down tools
to vigil tools such as paying
and our wireless, our wireless programs that can help us to determine our wireless, strengthen our network so hopefully you'll be able to use this information and you'll be able to troubleshoot your wireless networks or you're wired networks. You will be able to improve your connective ity and you'll be able to see us here next time on cyber readout. I t

Up Next

Troubleshoot Critical Systems

Diagnosing system malfunctions and finding a solution is an important skill for help desk professionals to develop. Expand your knowledge of the troubleshooting theory in less than an hour.

Instructed By

Instructor Profile Image
Anthony Harris
Senior Systems Engineer at ZenPoint Solutions