Ping and Arp both commands are use to determine network problems. If you get any problem in your network regarding your computer connectivity through remotely or locally then you can use this Ping and Arp command to determine actual problem in your network.

How to use Ping and Arp command for network connection troubleshooting ?

Ping and PathPing commands

Ping is a tool that helps to verify IP-level connectivity and PathPing is a tool that detects packet lose over multiple-hop trips. Ping command basically use to verify that a host computer can send IP packets to a destination computer.

How to use ping command?

To use ping command in your computer to check network connectivity problem follow this below steps.

* Login to your Windows Computer with admin account.

* Then Click on start and go to run.

* Now type CMD and press Enter. See below picture

* A command prompt window will open like below picture

Now you can use the following ping commands to troubleshoot network connectivity.

---

Command 1 : Type  Ping  <IP Address> in command windows. In IP Address use your own target IP address like 192.168.1.224. See below picture

Remarks : If you get fail results in “ping IP Address” command, it could be reason for TCP Drivers are corrupted, the network adaptor might not be working or another service might be interfacing with IP. So try to check this first to troubleshoot network connection problem.

---

Command 2 : Ping  IP address of the local host computer to verify that an address has been added correctly. To perform this step, enter ping <IP address of local host> at a command prompt.

Remarks : If you get successful replay message from the ping command its mean that your computer IP setup is working fine. If not then check your TCP/IP properties to configure your local IP address properly.

---

Command 3 : Ping the IP address of the default gateway. This step verifies that the default gateway is reachable and that the local host can communicate with another host on the network. to perform this steps, enter ping <IP address of default gateway> at a command prompt.

---

Command 4 : Ping the IP address of a remote host located beyond the default gateway. This step verifies that you can communicate with hosts outside your local network segment. To perform this step, enter ping <IP address of remote host> at command prompt.

---

Command 5 : Ping the host name of a remote host computer to verify that you can resolve remote host names. To perform this step, enter ping < host name of remote computer> at a command prompt.

---

Command 6: Run a PathPing analysis to a remote host to determine which (if any) routers on the way to the destination are malfunctioning. To perform this step, enter pathping <IP address of remote host computer> at a command prompt.

---

Extra tips : Ping uses host name resolution to resolve a computer name to an IP address, so if pinging succeeds by address, but fails by name, the problem lies in host name resolution(WINS), not network connectivity.

Please check this below option in your computer network properties to solve this problem

* The local computer’s  IP address and subnet mask are correctly configured.

* A default gateway is configured and the link between the host and the default gateway is operational. for troubleshooting, make sure only one default gateway is configured.

---

Troubleshooting network problem with ARP

Network traffic sometime fails because a router’s proxy ARP returns the wrong address. If you can ping both the loopback address and your won IP address, but you cannot ping a computer on the local subnet, the next step is to check the ARP cache for errors.

The ARP command is useful for viewing the ARP cache. If two hosts on the same subnet cannot ping each other successfully, try running the ARP command with -a switch on each computer to see whether the computers have the correct MAC address listed for each other. Use arp -a in your computer command prompt windows to get your Local Area Network (LAN) MAC Address. See below picture

If you cannot ping a command on a local subnet by IP address, and the ARP -a command reveals no errors in hardware address mapping, you should investigate for errors in the physical media, such as LAN cards, hubs, and cables.