Getting Reply From Loopback Address But Can't Ping Other IP Address

Published by: Alex George on April 07, 2009
Loopback address also called localhost is a reserved IP address. If we send packets to this IP address it will be rerouted to the computer itself. So loopback address is used to troubleshoot TCP/IP related issues on a PC. This article explains a rare situation where you cannot ping any IP address including the DNS server but can successfully ping loopback address. Before explaining this issue, I would like to explain the concept of loopback. The IP address in the range 127.0.0.1 - 127.255.255.255 are private and can be used as loopback but we normally use 127.0.0.1 as the loopback or localhost. Now let us check the scenario where you can successfully ping 127.0.0.1 but not any other external IP.


Explanation

Here I ping 4.2.2.2 from the command prompt but it failed to get a valid reply from it. However, when I ping 127.0.0.1, I am getting valid replies. Possible reasons from no valid reply from DSS server though I get replies from loopback address are:
  1. The TCP suit on your computer might be corrupted

  2. Connection Issues in the network

  3. There is no internet connection from your service provider.

If you are getting a reply from the loopback address it shows the TCP/IP suite is working on your computer. However, it is important to verify it by sending ping packets to 127.0.0.1 and analyze the reply.
  1. Click on start

  2. Click on run and type cmd on it then click OK(On Vista type command on search and press enter)

  3. Ping Loopback

    On the command prompt type, the following command ping 127.0.0.1 and press enter key. If you are getting replies, then the TCP/IP suite is fine. If not, you must reset the TCP/IP suit on your computer. To learn how to do it, I recommend you to visit the link below.
    There is No Reply From Loopback

After verifying the status of the TCP/IP suite, we must check the network connection. Here we must make sure there is no loose connection or faulty cable. Verify the Ethernet cable connected properly between your LAN port and Modem/router. Also, verify the quality of Ethernet cable. To get more inputs about this issue, I suggest you visit the link below.
How to check my Local Network Connection issues

If you are getting valid replies from localhost, next you must ping any DNS address. You may go through the instructions provided in the link below to learn more about it.
I Am Getting Replies From DNS Server

No:Recent Tutorials
Can Ping Global DNS Server IP Address But Unable To Open URL
How to Test Local Network For Connectivity Issues
3 How to Configure Idea 3G on Android Phone
PING: Transmit failed. General Failure
A solution for Destination Net Unreachable - Error
Destination host unreachable
How to Enable Disabled Adapter
Resolve Windows Automatic IP Address
Asianet Dataline Cable Broadband Modem WiFi Connectivity
How to Solve TTL Expired in Transit
Ping Request Could not Find Host
Steps to Reset Winsock On Your Computer
Important Network Commands

2 comments:

  1. Hi

    I use succesfully wired connection to my wrg54 on port 192.168.1.3 now I want to connect wirelessly so far I only see outgoing packets no incoming there is no firewall on the system so can any help plse

    Thanks

    ReplyDelete
  2. Can you explain your network structure ? It will help us to analyze and fix the issue.

    ReplyDelete

Newer Post Older Post Home