Gfrktyl

In my situation, I found peerblock caused this.

Some applications block http traffic, peerblock for example.
These cause pings to fail via the "General Failure" error message.

The way I found the application causing this was to kill processes one by one and checking the pings. Eventually I killed peerblock in my case and my ping started working.

If your pings are failing only for a few sites it most likely Firewall, Antivirus or some other HTTP interception/blocking application like Peerblock, Charles, Wireshark... etc.

I had a similar issue. I had to uninstall the AnyConnect mobility client.

I had a constant ping running and was getting the "general failure." to 8.8.8.8; as soon as the uninstall was halfway done I was back to being able to ping.

I would get this error after:

1. Accessing a site.


2. Connecting to my corporate VPN.


3. Accessing the same site.

It didn't happen for all sites, just sites that we (the company) published. To fix it, I ran

ipconfig /flushdns

It appears your computer has 6to4, an IPv6 transition/tunneling technology, enabled. Unfortunately 6to4 is very unreliable in practice and for many people it is completely broken.

It's a good idea to disable all of the transition technologies if you aren't actually using them, since they can all cause various problems such as this.

You can do so from an Administrator Command Prompt with the following:

netsh int ipv6 isatap set state disabled

netsh int ipv6 6to4 set state disabled

netsh interface teredo set state disable

In my case, this actually propagated all the way down to the Cisco VPN client. It said that there was a network subsystem failure. It turns out that my wireless nic was getting an IP address and all, but when I tried to ping my router, it was giving me a General Failure.

I took a look at device manager, and there were a bunch of new Bluetooth items that did not have their drivers installed. That was odd, because I hadn't installed anything new. In fact, this is a laptop with built-in Bluetooth hardware.

I know that Bluetooth allows you to do PAN (personal area network), so I wondered if this was somehow taking precedence over my WiFi NIC. I disabled all of these items in device manager, and although no new drivers were installed for this 'presumably new hardware', this allowed me to begin pinging my router. I'm now using my laptop successfully to both get on the we and VPN.

I also ran into a similar issue. Namely, I was unable to ping or tracert www.google.com on a Windows 7 operating system and it threw a General Failure.

I did the following to trouble-shoot and resolve issue:

1. Issue command ping -4 www.google.com. This explicitly pings using IPV4. Did not resolve issue.
   



2. Issued same command from #1, but ping -6 . Explicitly ping with IPV6. Error stated that it could not find host www.google.com




3. Issued same command with different target (within my network) without issue.




4. Temporarily stopped firewall (AVAST) and was successfully able to ping/tracert to www.google.com.




5. Opened Avast Internet Security, clicked firewall settings on left pane, clicked Settings button.




6. Clicked System rules and then enable ICMP (Internet Control Message Protocol ) to allow outgoing ping and trace request. Resolved Issue

Concerned: I issued the above commands on same workstation a few weeks ago without issue. I'm not sure how that setting was changed.

Fixed one of these on win 8.1 by resetting TCP/IP and Winsock. For anyone who needs info on how, open ADMIN command prompt and run:

Windows Vista, 7, 8

netsh i i r r

netsh winsock reset

Then reboot.

Windows XP

netsh i i r r

netsh w r

Then reboot. Good luck!

In my case this happened because my Internet connection had both IPv4 and IPv6 enabled, but I then connected to a VPN that supported only IPv4. So I guess Windows was still trying to connect to that host over IPv6 over the VPN, which failed.

The fix was to disable IPv6 in the network adapter properties for my Internet connection.

You may need to reconnect to your VPN.

I ran into a similar issue, and tried flushing the dns cache (ipconfig /flushdns) to no avail, I ended up needing to disconnect and reconnect to my VPN to get resolution to start working once again.

Until I did that ping and tracert both failed (but I was able to lookup the host name via nslookup).

the 'cybersec' feature of the nordvpn client also causes this for other (local) subnet ranges to not be reachable, even when vpn is OFF - $deity knows why - turn off the 'cybersec' option and all of a sudden your other lan subnets work again.

A helpful article with some good instructions and useful commands to fix this annoying windows issue is written here: https://appuals.com/fix-general-failure-error-running-ping-commands/.