In this section, we're going to cover two topics, ping, and path pain. So what exactly is ping? Or ping is a very basic networking command that you can use within Windows that will test and see the connectivity between your system and another system on the same network. Now, how can this be useful? Well, let's just say you have a user calling to complain that they're intermittently having issues connecting to the internet, or they're not receiving emails, or the outlook isn't logging in just various areas that needs consistent network connectivity. Well, let's simulate a very basic troubleshooting steps when it comes to ping in path pain.

So the system on the left is going to be our computer. And the system on the right is going to simulate the user's computer. Both systems are connected to the network. Let's go ahead and verify that. I'm going to type IP config, and hit enter. See, I have an IP address 1921680 154.

And now we're going to type the same command on the user computer and hit Enter. And I verified the user also has an IP address 192 168 0101. So what we want to do, we want to see if we can successfully basically test a very basic networking connection from our ERP system to the remote system. So I'm going to type ping and then I'm going to type the IP address of the remote system 1921680 dot 101 and hidden. And as we notice, we are not we got four replies back from the remote system. So we know that we can successfully at least to the network, connect to the system or verify its connectivity to the network.

But now let's simulate a system that's having intermittent connection issues. So on the remote system, I'm going to hit start, and I'm going to type firewall. I'm gonna go select Windows Firewall. I'm going to click inbound rules, scroll all the way down to file and print sharing echo request IP ICMP v4. So I'm going to right click on that section and hit properties. Now under the action section of the General tab, I'm going to click block the connection And hit Apply.

Now these echo requests are basically was being made on the left system by our system when we ping a remote PC. So basically what we told the system is to block these connections when they come in. So we're going to go into our system on the left, and type Ping. And we're going to type the same IP address as we did before 1921680101 and hit enter. Now this time around, we're getting different results, request timeout. So now we know that for some strange reason, we can't connect to the remote system so we can verify that the user is having connectivity issues.

So I'm going to go back to our system and we're going to come Another switch using ping called, well the switch dash T. Actually, let's go back. And let's do a forward slash question mark to see what are all the switches that we can use. With Ping. We see we have a dash t, which is paying the specified hosts until stopped. Dash a resolve the address to host names. We can scroll down we have using routing headers, and we can force us to ipv4 or ipv6 IP address.

So let's go ahead and do the dash T, for a continuous pain to the system to basically verify its connectivity. I'm going to go back to our system and hit OK. And on our system, I'm going to hit enter let the penguin for a second. So now we know that for some reason we can't successfully connect to the system on our right, we're getting request timeouts, we know the issue is that we know that the user is having connectivity issues. So let's just say we tell the user to go ahead and unplug the ethernet cable and plug the ethernet cable back into the system and wait a second. So the user unplug the ethernet cable and plug the ethernet cable back in. And now, we see that we are getting replies back from the remote system.

So in this case, in a very simple way, we know that it was probably the ethernet cable wasn't properly seated. And that's how a very effective way that we can use something as simple as paying to troubleshoot networking issues. I'm going to stop the ping on the left. I'm going Hit OK on the system on the right. Make sure we're going to allow the connection exit out of that. Now we want to cover a topic called path pain.

What exactly is path pain? Well, path ping combines the technology of a command called trace route with the technology of Ping. trace route basically tracks the amount of hops it takes to get from one destination to another via networking. So let's take a look at trace route really fast. I want to clear the system on the left and clear the system on the right. We're going to do trace route to let's just say yahoo.com.

Sorry, I believe I spelled it wrong. yahoo.com leave I'm still spelling it wrong. Oh, sorry. Actually. It's called tracer. There we go to yahoo.com.

So basically what the system is doing now, it's tracing the amount of hops or routes that are routers that it hits in order to get to that specific yahoo.com account. So right now we know we hit nine routers, 10, routers, 11, routers, things like that. Going to let trace route run. The reason why I'm saying trace route because that was the old way that we refer to trace route. This command instead of tree cert. We'll see the maximum amount of hops is 30.

And now the trace has been complete. So this is basically the route that this PC takes to get from my computer, all the way to Yahoo. com. Pretty, a pretty handy tool, how trace route can come in handy. Is because let's just say you're having issues reaching yahoo.com. And you don't know exactly where you're having the issue, whether it's your company, the remote company, somewhere in the line, you want to see where the issue is.

So we see that we successfully connected to yahoo.com with no issues. So we have a new problems here. Now path ping, as stated before combines this technology of trace route with the technology of pain. So I'm going to type path ping, and type yahoo.com. In hidden now we see we have the same statistics as before, is tracing the route. We went from my lab PC in my domain, we cross the few other networks and it finished up but the difference that it takes between Ping and trace route pain will now tell us the amount of packets that failed from one destination router to another.

So we can actually go into the system. And see, let's just say if there's a bad router somewhere in the network. And once these packets hit that router, we see maybe 1% 2%, or 3% loss. So it helps us to identify issues that we're having in the network. I want to pause the video for a second and wait for this to finish and we'll be right back. Okay, we are back.

And we now have our results from our path ping command. It's kind of important to notice here the different sections, we have the source to particular website, we have the loss in percentage and the address of the website that we were trying to access or the access point. So as we see from just like trace route, we started with our local network and we gradually went out and pinged every single router that we ran across. But the more information that we get about path pain can help us with troubleshooting. So as we look as our loss percent category here, we have a few, a little bit after a few of the routers, we have a 2% loss 3% on our particular gateway, we may need to look at that. And as we go down, we look at different gateways, we have 1% 1% 1%.

So we see the entire middle connection of our attempt to get to yahoo.com is fine, while the beginning and the end tend to have lost about a 3% loss. So we see that our network router, our default gateway, may need to be looked at, as well as we know that the route is on the endpoint also averaged about a 3% loss. So it kind of helps us to see where we are exactly having issues when connecting from one system to website. one system to another system so we can pinpoint more exactly where those issues are. I hope you guys enjoyed this course. I will see you again in the next one.