Error of “general failure” when executing ping commands

At an elevated or not elevated command prompt on a Windows operating system computer, the ping command can be used to contact another web portal or IP address on the same network and see what response is received, along with specific statistics of the solution being received . The ping command is one of the simplest commands available to Windows users., but that doesn't mean nothing will fail when pinging. One of the most common problems Windows users have had when trying to ping a command prompt is a roadblock where the ping command fails and the entire command prompt says General Failure.

The command prompt does not provide additional information on what exactly failed or why the computer did not ping. This being the case, there are a lot of different possible causes for this problem. Despite this, on the bright side, there are simply as many possible solutions to this problem as there are possible causes. The following are some of the most effective solutions that users affected by this problem can use to try to resolve it:

Solution 1: uninstall any application that blocks HTTP traffic in any way

First, if you have an application on your computer that, one way or another, is able to block HTTP traffic to or from your computer, you must get rid of it immediately. Such applications include (but they are not limited to) Peerblock, Charles, Wireshark and the AnyConnect mobility client. A program capable of blocking HTTP traffic to or from your computer could be blocking your computer's attempts to ping the web portal or the IP address it is trying to contact., so uninstalling each and every one of these applications is an excellent starting point in this circumstance.

Solution 2: configure Windows to prefer IPv4 over IPv6 in prefix policies

Not many Windows users are aware that simply unchecking the IPv6 Internet Protocol in your computer's network adapter settings does not absolutely disable the IPv6 protocol.. There are prefix policies built into the Windows operating system that are programmed to prefer the use of IPv6 over IPv4, and that can cause your attempts to ping to result in general failure error messages. To configure Windows to prefer IPv4 over IPv6 in prefix policies, should:

1. Go here and click Download under Prefer IPv4 over IPv6 in prefix policies to download Microsoft Easy Fix 21066.

2. Once Microsoft Easy Fix has been downloaded 21066, navigate to the place where you downloaded it and double click it to run it.

3. Follow the instructions on the screen so that the utility can fix this problem for you..

4. Once the utility has finished working its magic, close it and see if you can now successfully ping the commands.

Solution 3: Disable each and every IPv6-IPv4 transition technology

If you have any kind of IPv6 tunneling or transition technology enabled and on your computer, that could be the cause of all your troubles. Despite this, Fortunately, simply disabling each and every IPv6-IPv4 transition technologies should fix the problem.

1. Open the start menu.

2. Busque »cmd«.

3. Right click on the search result titled cmd and click Run as administrator.

4. One by one, type each of the following commands at the elevated command prompt, pressing Enter after each write:

netsh int ipv6 isatap determine disabled status

netsh int ipv6 6to4 determine disabled status

netsh teredo interface determine state disable

1. Close the elevated command prompt.

2. Restart your computer.

3. Check whether the problem persists or not when the computer is on.

Solution 4: Reset the TCP catalog / IP and Winsock of your computer

1. Open the start menu.

2. Busque »cmd«.

3. Right click on the search result titled cmd and click Run as administrator.

4. One by one, type each of the following commands at the elevated command prompt, pressing Enter after each write:

netsh iirrr

reinicio de netsh winsock

1. Close the elevated command prompt.

2. Restart your computer and check if this solution has done the job when it boots.

Solution 5: Clean your computer's DNS

One solution that many users affected by this problem have found immensely effective in getting rid of it and restoring their computers ability to successfully execute ping commands is to remove DNS from their computers.. Cleaning your computer's DNS is not only a pretty safe bet when it comes to fixing this problem, it is also generally good for the health of your computer. To clean your computer's DNS, should:

1. Open the start menu.

2. Busque »powershell«.

3. Right-click the search result titled Windows PowerShell and click Run as administrator.

4. One by one, type each of the following commands in the elevated instance of Windows PowerShell, pressing Enter after typing each one:

ipconfig / release

ipconfig / renovate

ipconfig / flushdns

netsh int ip reset c: tcp.txt

reinicio de netsh winsock

1. Close Windows PowerShell and restart your computer.

When the computer starts, check whether the problem has been solved or not.

Solution 6: restart your computer's Hosts file

1. Open a new instance of Notepad.

2. Paste the following into the new instance of Notepad:

# Copyright (c) 1993-2006 Microsoft Corp.

#

# This is a sample HOSTS file used by Microsoft TCP / IP for Windows.

#

# This file contains the mappings of IP addresses to host names. Each

The entrance # should be kept on one line. The IP address must

# will be placed in the first column followed by the name of the respective host.

# The IP address and the hostname must be separated by at least one

# space.

#

# At the same time, the comments (like these) can be inserted into the individual

# lines or after the machine name indicated by a symbol $ 0027 # $ 0027.

#

# As an example:

#

# 102.54.94.97 rhino.acme

# 38.25.63.10 x.acme.com # x host client

# Localhost name resolution is handled within DNS itself.

# 127.0.0.1 localhost

# :: 1 localhost

1. Presione Ctrl + S to save the Notepad document.

2. Name the document from Notepad “hosts” (including quotes), navigate to the directory where you want to save the file and click OK.

3. Press the Windows logo key + R to open a Run dialog.

4. Type the following in the Run dialog box and press Enter:

% WinDir% N-Sistema32N-ConductoresN-Etc

1. Find the hosts file, right click on it, click Rename, rename the file to old and press Enter.

2. Move the new file “Hosts” from where you saved it, a% WinDir% System32DriversEtc.

3. If you are asked to confirm the action while moving the file, do it.

Once the file has been moved, restart your computer and check if the problem is resolved once it starts.

Solution 7: enable all ICMPv4-In rules in your computer's firewall settings

1. Open the start menu.

2. Busque »firewall«.

3. Click on the search result titled Windows Firewall with Advanced Security.

4. In the left pane of the window, click Inbound Rules.

5. In the right panel, locate each of the inbound rules titled File and Printer Sharing (Echo request – ICMPv4-In), right click on them and click Enable rule.

6. Once this is done, restart your computer.

7. When the computer starts, check if the problem has been fixed.