Windows 10: General Failure on ping 127.0.0.1 or dedicated IP

Discus and support General Failure on ping 127.0.0.1 or dedicated IP in Windows 10 Network and Sharing to solve the problem; Hello! I have a big problem with reaching one of computers within home LAN. I am not sure if it is because of last 20H2 update, but there are no... Discussion in 'Windows 10 Network and Sharing' started by BoskoVoda, Nov 16, 2020.

  1. BOSKOVODA
    BoskoVoda Win User

    General Failure on ping 127.0.0.1 or dedicated IP


    Hello!


    I have a big problem with reaching one of computers within home LAN.

    I am not sure if it is because of last 20H2 update, but there are no problems on my Server WS 2016 or other PC stations, so I assume it is also not group policy.


    Problem:

    C:\WINDOWS\system32>ping 127.0.0.1

    Pinging 127.0.0.1 with 32 bytes of data:
    General failure.
    General failure.
    General failure.
    General failure.

    or:


    Pinging 192.168.1.8 with 32 bytes of data:

    General failure.

    General failure.

    General failure.

    General failure.


    If I ping just a string "localhost", then:

    Pinging BoskoNoviM2.vodnik.lan [::1] with 32 bytes of data:

    Reply from ::1: time<1ms

    Reply from ::1: time<1ms

    Reply from ::1: time<1ms

    Reply from ::1: time<1ms


    This PC can ping anything except its own ip address.


    I tried everything from CMD Commands flushdns, release, renew... and sfc /scannow, disabling and uninstalling NIC driver, disabling firewall and windows security and reseting host file. I tried to login with local admin account and repeated most of previously mentioned tasks and still nothing.


    Is there any solution to this except factory reset or reinstall?

    :)
     
    BoskoVoda, Nov 16, 2020
    #1
  2. JACKIN
    jackin Win User

    What causes PING General Failure

    C:\windows\system32>ping 192.168.11.175

    Pinging 192.168.11.175 with 32 bytes of data:
    General failure.
    General failure.
    General failure.
    General failure.

    Ping statistics for 192.168.11.175:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    After I restart Windows I didn't get it again, but I'm curious to know what causes GENERAL FAILURE error to begin with.
     
    jackin, Nov 16, 2020
    #2
  3. SCYLIPT
    Scylipt Win User
    Tracert or ping not working, general failure

    Hi Delchina,

    I get the same results no matter where I ping, I run Cmd as admin and the only vpn i have is Hola free Vpn which is a chrome extension which is turned off.

    C:\Windows\system32>ping amazon.com

    Pinging amazon.com [176.32.103.205] with 32 bytes of data:
    Request timed out.
    General failure.
    General failure.
    General failure.

    Ping statistics for 176.32.103.205:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:\Windows\system32>ping tori.fi

    Pinging tori.fi [54.194.118.22] with 32 bytes of data:
    Request timed out.
    General failure.
    General failure.
    General failure.

    Ping statistics for 54.194.118.22:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:\Windows\system32>tracert tori.fi

    Tracing route to tori.fi [54.194.118.22]
    over a maximum of 30 hops:

    1 * General failure.

    Trace complete.

    I have also tried an online tracert, Online Visual Traceroute Tool - Monitis, with similar results

    Source
    Europe
    1ip-10-0-0-0.eu-west-1.compu0 ms0 ms0 ms
    2ip-10-0-0-0.eu-west-1.compu0 ms0 ms0 ms
    3
    no response
    4
    no response
    5
    no response
    6
    no response
    7
    no response
    8
    no response
    9
    no response
    10
    no response
    11
    no response
    12
    no response
    13
    no response
    14
    no response
    15
    no response
    16
    no response
    17
    no response
    18
    no response
    19
    no response
    20
    no response
    21
    no response
    22
    no response
    23
    no response
    24
    no response
    25
    no response
    26
    no response
    27
    no response
    28
    no response
    29
    no response
    30
    no response
    Destination
    Osta ja myy helposti. Ilmoita ilmaiseksi Torissa.
     
    Scylipt, Nov 16, 2020
    #3
  4. SCYLIPT
    Scylipt Win User

    General Failure on ping 127.0.0.1 or dedicated IP

    Tracert or ping not working, general failure

    Hello,

    I tried a tracert today and it failed. I tried it a few different ways and the results are below.

    C:\Windows\System32>tracert bbc.co.uk

    Tracing route to bbc.co.uk [151.101.192.81]
    over a maximum of 30 hops:

    1 * General failure.

    Trace complete.

    C:\Windows\System32>tracert BBC - Home

    Tracing route to gtmlivelive-eu-c-1nlbwwwcouk-17e0f31403454351.elb.eu-central-1.amazonaws.com [3.120.156.170]
    over a maximum of 30 hops:

    1 * General failure.

    Trace complete.

    C:\Windows\System32>tracert -4 BBC - Home

    Tracing route to gtmlivelive-eu-c-1nlbwwwcouk-17e0f31403454351.elb.eu-central-1.amazonaws.com [35.156.134.252]
    over a maximum of 30 hops:

    1 * General failure.

    Trace complete.

    I also tried it with ping with similar results.

    C:\Windows\System32>ping BBC - Homepage

    Pinging gtmlivelive-eu-c-1nlbwwwcom-8168f86a0c0d146f.elb.eu-central-1.amazonaws.com [18.195.39.25] with 32 bytes of data:
    Request timed out.
    General failure.
    General failure.
    General failure.

    Ping statistics for 18.195.39.25:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    Can anyone help figuring out why this is happening?

    Regards, Henry

    Edit....

    I also tried with the firewall off with the same results.
     
    Scylipt, Nov 16, 2020
    #4
Thema:

General Failure on ping 127.0.0.1 or dedicated IP

Loading...

  1. General Failure on ping 127.0.0.1 or dedicated IP - Similar Threads - General Failure ping

  2. Disk 0 Disk 1

    in Windows 10 Software and Apps
    Disk 0 Disk 1: My C and D drive had a partition where my C was Full and D was empty. I though erasing my D drive was going to eliminate that partition and add the space to C. But nop., D drive turned into Disk "0" and C drive into disk 1. Can I fix this ? and how to can Add more space from...

  3. Ping "General failure" ~50% of the time

    in Windows 10 Network and Sharing
    Ping "General failure" ~50% of the time: Around 50% of the time when running a ping, its returning "General Failure" for an unknown reason. This is leading to very dodgy internet. It works absolutely fine on Linuxping 8.8.8.8 -tReply from 8.8.8.8: bytes=32 time=20ms TTL=114Reply from 8.8.8.8: bytes=32 time=18ms...

  4. Ping 192.168.0.* returns 'General Failure'

    in Windows 10 Ask Insider
    Ping 192.168.0.* returns 'General Failure': submitted by /u/Maelstrive [link] [comments] https://www.reddit.com/r/Windows10/comments/ji1wo3/ping_1921680_returns_general_failure/

  5. Ping - General Failure

    in Windows 10 Network and Sharing
    Ping - General Failure: I have a laptop .193 that connects to my home network through a wireless access point .162. I can access the internet and I can ping out google.com and 8.8.8.8. I cannot ping anything in my network, including the gateway. Everything, including the laptop is static IP. I...

  6. General Ping Failure help

    in Windows 10 Ask Insider
    General Ping Failure help: [ATTACH] So, for some reason I can't ping my default gateway... I have tried these cmd commands: netsh int ip reset netsh winsock reset netsh int ip reset Tried to turn off all firewalls, and when I type the default gateway in a webbrowser I just get "Your Internet...

  7. Ping 192.168.1.1 General Failure

    in Windows 10 Network and Sharing
    Ping 192.168.1.1 General Failure: Hi. I have a problem in one of my computers. It successfully gets IP address from my router and successfully connects to the Internet. However, it can't detect my network WD drive, and while testing I discovered that it fails even to ping it's own IP address and even my...

  8. Ping 168.192.1.1 General Failure

    in Windows 10 Network and Sharing
    Ping 168.192.1.1 General Failure: Hi. I have a problem in one of my computers. It successfully gets IP address from my router and successfully connects to the Internet. However, it can't detect my network WD drive, and while testing I discovered that it fails even to ping it's own IP address and even my...

  9. Tracert or ping not working, general failure

    in Windows 10 Network and Sharing
    Tracert or ping not working, general failure: Hello, I tried a tracert today and it failed. I tried it a few different ways and the results are below. C:\Windows\System32>tracert bbc.co.uk Tracing route to bbc.co.uk [151.101.192.81] over a maximum of 30 hops: 1 * General failure. Trace complete....

  10. PING: transmit failed. General failure.

    in Windows 10 BSOD Crashes and Debugging
    PING: transmit failed. General failure.: No Microsoft. You are wrong. "General failure" is always the the wrong answer. Tell me something useful that I can debug. "General failure" tells me nothing. "ping" is an age old diagnostic tool. You have neutered it....

Users found this page by searching for:

  1. cannot ping 127.0 0.1 general failure after route flush