Skip to main content

PING: Transmit failed. General Failure - Reasons and Solution

Yesterday I faced Internet connectivity issues on my computer, and the troubleshooting ended up with an error message PING: Transmit failed. General Failure. I received this error when I ping the loopback address. I tried to ping a different loopback address, but that too faced the same fate. However, I fixed the PING: Transmit failed General Failure error on my computer by following a set of troubleshooting methods. This tutorial explains the reasons to receive PING: Transmit failed General Failure error and how to solve it.


Let you show you the screenshot I took from my Windows PC, before explaining the meaning of PING: Transmit failed General Failure message.

PING: transmit failed. General failure means I lost all the ping packets I sent to the loopback address.

C:\Users\sijugk>ping 127.0.0.21 

Pinging 127.0.0.21 with 32 bytes of data: 
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 

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

Reasons for Getting PING: transmit failed. General failure
One of the major reasons to receive PING transmit failed General failure error is the wrong TCP/IP and DNS settings. Firewall misconfiguration and Network adapter driver issues can also be a reason.

  1. Corrupted TCP/IP suite

  2. Misconfigured Firewall

  3. Outdated Network drivers or firmware

  4. DNS and other socket issues

  5. Other software or hardware errors


The solution for Ping: Transmit failed. General Failure
To fix the PING transmit failed General failure error, follow the instructions provided below.


  1. Reset the TCP/IP suite and Flush the DNS Cache on your computer
    The first step to troubleshoot the PING transmit failed General failure error on a Windows computer is to perform flush DNS cache and reset TCP/IP suite.


    • Type netsh int ip reset c:\tcp.txt on command prompt and press enter key.

    • Type ipconfig /flushdns on the command prompt and press enter key

    • Reboot your computer.

    • Check for the issue. If you still receive the same error, proceed to the next steps.



  2. Disable Firewall (and other security programs ) and check for the issue: Sometimes you may get this message "PING: Transmit failed. General Failure" when firewall stops packets.

  3. Perform a System Restore to the last known good configuration

  4. Power Cycle the entire network:
    To know more about this step, go to the link below.
    How to perform the power cycle

  5. Update the Network Adapter driver:
    To perform this step follow the instructions provided in the link below.
    How to Update Adapter Driver from Device Manager

  6. Perform a Windows Socket Reset
    Execute the following commands on command prompt to renew IP address and reset Windows Socket on your laptop.

    • ipconfig/release

    • ipconfig/renew

    • netsh winsock reset

  7. Update the modem and router (if any) firmware


Just like this guide for "Ping: Transmit failed. General Failure" error message, we have a troubleshooting guide for some other important Internet connectivity error messages.

Some of them with the connection error codes are Error 718: Connection was terminated, and Error 777: Connection Attempt failed.

When I optimized the Windows 10 settings on my laptop, I faced some similar ICMP error codes. Destination Net Unreachable and Destination Host Unreachable were the commonly occurred error messages.

Comments

Thief_ said…
For those visiting, looking for an answer, I had the same issue in a VMware machine which i was moving from one domain to another. The fix was to remove the existing VM NIC then install a new NIC. Interestingly Windows 7 told me that the IP I assigned to the new NIC was already assigned to the old NIC, eventhough the old NIC was no longer available and that I may have issues when the old NIC was made available (which it would not as I had deleted it from the VMware config for that server).

Once I entered the same IP information against the new NIC it worked like a charm!
Anonymous said…
hi,
this problem has only occured for me when I resumed the PC from hibernation. A normal reboot always solved it, but I'd still like to know WHY does it happen.
Siju George said…
Thanks for adding the way you resolved the similar issue.
Arnold Giovanni said…
Just when i our old router was changed, non of window 7 machines was able to access the network.
PING:transmit failed. general failure
Siju George said…
Hi Arnold,

Is the issue persists ?
Anonymous said…
Loopback I.p. Is 127.0.0.1
You will get this error message if you ping an up that simply doesn't exist.
Siju George said…
127.0.0.0 to 127.255.255.255 is mapped to loop back address and you should get valid reply if you ping an IP address in this range from your computer.
Anonymous said…
I don't know if that will be helpful or not, but if the problem arises in wireless connection it could be because of "WAP Pre-Shared Key", someone might have changed it and may have forgot to update you that he has done it, so, just updating the Pre-Shared Key would do the trick.

Thanks
Siju George said…
Thanks for giving additional trick to resolve the issue.
Anonymous said…
THANKS!!!!
Marty said…
I just shut down the Firewall. Great no more error.
Anonymous said…
Thanx it worked
Hamza Farooq said…
I tried installing jetico firewall 2, totally hang my windows 7 , system restore saved the OS but DNS issue for browsing disconnected me from internet world, Plus pin to 127.0.0.1 was not working, New wireless device didnt help either, still looking for a solution.
Siju George said…
May be your adapter driver is corrupted. I suggest you to uninstall and reinstall adapter driver.
Anonymous said…
Thanks Brother. Nice work
Nathan said…
Honestly I was looking for what is this transmit failed !!!!

I believed it was related to transmission or something. Anyway good work hurraay.....
Lucky said…
I get this transmit failed error message when I ping from my wireless adapter. But there is no problem with Ethernet adapter.. So strange !!
Anonymous said…
If you receive this error run the following command:
netsh int ipv4 show ipaddresses level=verbose
Look at the bottom for "Skip as Source : true"
If it says "true" this is the cause of your issue. It should say "false"
that means that windows will skip using this as the source when trying to hit external address / register in dns
Siju George said…
Thanks for providing additional solution.
Anonymous said…
Here is an interesting twist. I have set up a BAT file that uses PING to prevent connection from being shut down because it was not active. (An idea posted by someone else having trouble with keeping T-Mobile broadband connected.) At any rate, the response can go from general failure to timeout or reply from ... without me changing anything. Does not seem like it would have anything to do with my system other than the flakiness of my USB Broadband device. Oh, and I still have internet access when it is returning General failure.
Paul Gallagher said…
My current BAT file loops after 25 ping echos as follos

:Start
Ping google.com -w 9999 -i 255 -t -l

1 -n 25
GOTO Start
Paul Gallagher said…
:Start
Ping google.com -w 9999 -i 255 -t -l

1 -n 25
GOTO Start

The above BAT file sets up a loop so every 25 pings it goes back and restarts. Of not General error does not mean I cannot access internet and I get reply for ... and general error returns with no changes on the system
My connection is flakey USB Broadband.
Alex George said…
Very interesting observation Paul.
kywriter said…
I know this may seem obvious but it was not obvious to me (at first) while seeking a laptop connection to a LAN.
Something disabled the adapter.
I enabled it and used advanced settings it to wake up from shutdown.
Instant access and no need to reenable on startup.
kywriter said…
It was not obvious to me that the WAN adapter was disabled, probably by setting up a new antivus program.
So I enabled it and VOILA! instant access.
I also checked the adapter settings and saw that the "wake after restart" was set to No. changed that to Yes and now I'm online more quickly in the morning.
Thanks,it help me to solve that error occur when i try to ping
Anonymous said…
Thanks. These commands solved the problem. Good job!
Anonymous said…
An outstanding share! I have just forwarded this onto a colleague who
was conducting a little homework on this. And he actually bought me breakfast due to the fact that I discovered it for
him... lol. So let me reword this.... Thanks for the meal!!
But yeah, thanks for spending the time to discuss this issue here on your blog.
David Den said…
Nice Blog...TFS
https://fixingblog.com/how-to-setup-belkin-wireless-router-in-easy-steps/
Unknown said…
Thank you so much resolved myn. I just uninstalled the antivirus and immediately it connected before it finished uninstalling
TJ said…
You didn't ping the loopback. You even tried to tell someone that you did and posted the loopback addresses...and still didn't go back and look at what you did wrong. 172 is not a loopback address.
sharmarajat said…
I performed a Window Socket Reset. Do not know much about these things so just followed the instructions and ran the 3 commands mentioned in the Command prompt. Broooo. It worked like a charm. I was facing this issue for a month now. My ISP couldn't solve it but was very sure that the internet connection is 100% strong. I was about to change my ISP when I found this.
Really thanks to the person who posted this. Solved a huge problem for me.
Alex George said…
@ Sharma Rajat

I am happy to hear this tutorial helped you to solve the issue.