Skip to main content

PING: Transmit failed. General Failure - Reasons and Solution

Yesterday I faced issues with connecting to Internet and while checking network connectivity, I received one error message. The error message I received was "PING: Transmit failed. General Failure" and all the packets sent from command prompt were lost. I received that error message while trying to ping loopback address from my Windows computer. I tried to ping a different loopback address, but the result was the same. I fixed the issue by following a set of steps and this tutorial is completely based on those troubleshooting steps. Since this issue is very common, I believe sharing the method I followed may help those who experience the same error message PING: Transmit failed. General Failure.

Before going to the details, I suggest you read the below tutorial if you are experiencing slower broadband speed on your PC.
Broadband Hack To Improve Speed

This is the output I received when I ping loopback address.


Pinging 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 
   Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) 

Reasons and fix for PING: Transmit failed. General Failure

Major possible reasons for the error message  PING: Transmit failed. General Failure are:
  1. Misconfigured Firewall
  2. Outdated Network drivers or firmware
  3. DNS and other socket issues
  4. Other software or hardware errors

The solution for Ping: Transmit failed. General Failure

We can resolve it by following the steps provided below.
  1. Power Cycle the entire network :
    To know more about this step go to the link below.
    How to perform power cycle

  2. Command Prompt troubleshooting :

    Use the following command prompt commands to solve the issue.

    • ipconfig/release

    • ipconfig/renew

    • ipconfig /flushdns

    • netsh int ip reset c:\tcp.txt

    • netsh winsock reset

    Type each command on the command prompt, and press the enter key. After completing all commands, reboot your computer.

  3. 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.

  4. Perform System Restore to last known good configuration

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

  6. 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. They are:
Error 718: Connection was terminated

Above error message says about a state where the entire connection is terminated. However, if the modem fails to get a connection with a remote host you will receive the following error message.
Error 777: Connection Attempt failed


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…
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
You will get this error message if you ping an up that simply doesn't exist.
Siju George said… to 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.

Siju George said…
Thanks for giving additional trick to resolve the issue.
Anonymous said…
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 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

Ping -w 9999 -i 255 -t -l

1 -n 25
GOTO Start
Paul Gallagher said…
Ping -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
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.