Cannot Ping 127.0.0.1 and No Reply From Local Host

Published by: Alex George on April 07, 2009
When we send ping packets to localhost or loopback address (127.0.0.1 to 127.255.255.254), they will be rerouted to the PC. Even if your Ethernet adapter is not connected to any modem or router, you will get a valid reply when you ping loopback IP. However, in some cases, you may not get replies from 127.0.0.1 and this article explains the reasons for it.


Reasons For No Replies From 127.0.0.1

There are two reasons which prevent your computer from getting replies from 127.0.0.1. They are provided below.
  1. TCP/IP suit installed on your laptop is corrupted

  2. Ethernet adapter is not working

Fix

Now let us troubleshoot each case.
Important Network Commands

  1. Reset TCP/IP

    To fix the issue with the TCP/IP suite on your computer, use the following commands. You can type them on Command Prompt one by one and then check for the issue.

    • ipconfig /flushdns

    • netsh int ip reset c:\tcp.txt

    • netsh winsock reset

    After resetting the windows socket and TCP/IP suite, we need to restart the PC. After restarting the computer we need to check whether the issue persists or not. If still, we cannot ping the loopback address the only possible chance is corrupted Ethernet Adapter.

  2. Test Adapter

    Since the TCP/IP suite is installed properly, the only reason that may prevent the local host from communicating properly is the faulty Ethernet adapter. We can test the status of an adapter in the device manager. To learn it properly, I recommend you to follow the instructions provided in the link below.
    Test an Adapter in Device Manager
Ping Global DNS Connectivity Issues Configure Idea 3G
PING: Transmit failed Destination Net Unreachable Destination host unreachable
Enable Disabled Adapter Windows Automatic IP Asianet Dataline
TTL Expired Couldn't Find Host Reset Winsock

No comments:

Post a Comment

Newer Post Older Post Home