Fixing Ping General Failure: Step by Step Ways to Fix Ping Failure Easily

Fixing Ping General Failure: Step by Step Ways to Fix Ping Failure Easily.

Fixing Ping General Failure: Ping is a valuable tool for troubleshooting network or internet issues of any kind. A ping command sends information packets to computers on a network or over the Internet to decide if they are eligible for communication.

In Windows 8, if the device does not have the proper Internet protocol selected, the error message “Ping, Transmit Failed, General Failure” appears: It’s not beyond fixing. In your computer’s control panel, you can pick TCP / IPv4 or TCP / IPv6.

Fixing Ping General Failure

Ping Commands

You can only send ping requests from the command prompt of your operating system. In Windows 8, open the Search box, type “cmd” in the Search field, then select “Command Prompt” from the list of search results. At the prompt, type “ping,” a space and then the IP address or domain name of the target. For example, type “ping xxx.xxx.xxx.xxx” or “ping www.mynetwork.com;” then press Enter. Your computer will send four packets of information at one-second intervals.

Ping Responses

A ping response shows results for each returned packet on four separate lines showing the round-trip time in milliseconds. It also gives a summary of the packets lost, along with the fastest, slowest and average times. If the target doesn’t respond, each line shows “Request Timed Out.” If the computer has the wrong TCP/IP setting, in Windows 7 and Windows 8, the message reads, “PING: Transmit Failed. General Failure.” In Vista, it reads, “PING: transmit failed, error code 1231.” It indicates that you have the wrong TCP/IP setting. In earlier Windows versions, it reads, “Destination Host Unreachable.”

Set TCP/IP Version

Click “Start,” and select “Control Panel.” Type “Adapter” in the “Search Control Panel” box in the upper right corner and click “View Network Connections” under the Network and Sharing Center tab. Right-click on the network you’re using; then click “Properties.” Ensure the proper TCP/IP protocol version is checked in the list of optional boxes. At the time of publication, most networks use TCP/IPv4. Don’t change any other boxes because they don’t affect the ability to ping. Click “Properties,” then under the “General” tab, click “Obtain an IP Address Automatically” and “Obtain DNS Server Address Automatically.” Then click “OK.”

TCP/IPv4 vs. TCP/IPv6

TCP/IPv4 vs. TCP/IPv6

Internet Protocol Version 4 has about 4 billion addresses available, which are rapidly being used up. Version 6 allows 79 octillion times more address space to provide for worldwide Internet expansion, along with several other advantages over version 4. However the Internet Engineering Task Force has been working to design a smooth transition that allows both to exist at the same time until all networks can be upgraded. In the meantime, network designers must choose between the two and can’t use both simultaneously. You must make the setting in your computer conform with the network.

Fixing Ping General Failure: When Running Ping Commands

The Command Prompt doesn’t provide any additional information as to exactly what failed or why the computer failed to run the ping command. That being the case, there are a ton of different possible causes for this problem. On the bright side, however, there’s basically just as many possible solutions to this problem as there are possible causes for it. The following are some of the most effective solutions that users affected by this problem can use to try and resolve it:

Solution 1: Uninstall any applications that block HTTP traffic in any way

First and foremost, if you have any applications on your computer that are, in one way or another, capable of blocking HTTP traffic to or from your computer, you need to get rid of them right away. Such applications include (but are certainly not limited to) PeerblockCharlesWireshark and the AnyConnect mobility client. A program capable of blocking HTTP traffic to or from your computer might be blocking your computer’s attempts to ping the website or IP address you are trying to get in touch with, which is why uninstalling any and all such applications is an excellent place to start in this case.

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

Not many Windows users know that simply un-checking the IPv6 internet protocol in the Network adapter settings of their computer does not completely disable the IPv6 protocol. There are prefix policies built into the Windows Operating System that are programmed to prefer using IPv6 over IPv4, and that can lead to your attempts at running ping commands resulting in General failure error messages. To configure Windows to prefer IPv4 over IPv6 in prefix policies, you need to:

  1. Go here and click on Download under Prefer IPv4 over IPv6 in prefix policies to download Microsoft Easy Fix 21066.
  2. Once Microsoft Easy Fix 21066 has been downloaded, navigate to where you downloaded it to and double-click on it to run it.
  3. Follow the onscreen instructions so that the utility may fix this problem for you.
  4. Once the utility is done working its magic, close it and check to see if you can now successfully run ping commands.

Solution 3: Disable any and all IPv6-IPv4 transition technologies

If you have any kind of IPv6 transition or tunneling technology enabled and on your computer, that might be the cause of all your problems. Thankfully, though, simply disabling any and all IPv6-IPv4 transition technology should fix the issue.

  1. Open the Start Menu.
  2. Search for “cmd“.
  3. Right-click on the search result titled cmd and click on Run as administrator.
  4. One by one, type each of the following commands into the elevated Command Prompt, pressing Enter after typing in each one:

netsh int ipv6 isatap set state disabled
netsh int ipv6 6to4 set state disabled
netsh interface teredo set state disable

  1. Close the elevated Command Prompt.
  2. Restart your computer.
  3. Check to see whether or not the problem still persists when the computer boots up.

Solution 4: Reset your computer’s TCP/IP and Winsock catalog

  1. Open the Start Menu.
  2. Search for “cmd“.
  3. Right-click on the search result titled cmd and click on Run as administrator.
  4. One by one, type each of the following commands into the elevated Command Prompt, pressing Enter after typing in each one:

netsh i i r r
netsh winsock reset

PRO TIP: If the issue is with your computer or a laptop/notebook you should try using Reimage Plus which can scan the repositories and replace corrupt and missing files. This works in most cases, where the issue is originated due to a system corruption.

  1. Close the elevated Command Prompt.
  2. Restart your computer and check to see if this solution got the job done when it boots up.

Solution 5: Flush your computer’s DNS

Solution 5: Flush your computer’s DNS

A solution that tons of users affected by this problem have found immensely effective in getting rid of it and restoring their computers’ ability to successfully run ping commands is flushing their computers’ DNS. Flushing your computer’s DNS is not only a pretty safe bet when it comes to fixing this problem but is also, in general, good for the health of your computer. To flush your computer’s DNS, you need to:

  1. Open the Start Menu.
  2. Search for “powershell“.
  3. Right-click on the search result titled Windows PowerShell and click on Run as administrator.
  4. One by one, type each of the following commands into the elevated instance of Windows PowerShell, pressing Enter after typing in each one:

ipconfig/release
ipconfig/renew
ipconfig /flushdns
netsh int ip reset c:\tcp.txt
netsh winsock reset 

  1. Close Windows PowerShell and restart your computer.

When the computer boots up, check to see whether or not the problem has been resolved.

Read Also:

Solution 6: Reset your computer’s Hosts file

  1. Open a fresh instance of Notepad.
  2. Paste the following into the fresh 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

# entry should be kept on an individual line. The IP address should

# be placed in the first column followed by the corresponding host name.

# The IP address and the host name should be separated by at least one

# space.

#

# Additionally, comments (such as these) may be inserted on individual

# lines or following the machine name denoted by a ‘#’ symbol.

#

# For example:

#

#      102.54.94.97     rhino.acme.com          # source server

#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handle within DNS itself.

#       127.0.0.1       localhost

#       ::1             localhost

  1. Press Ctrl to save the Notepad document.
  2. Name the Notepad document “hosts” (including the quotation marks), navigate to the directory you want the file to be saved in and click on OK.
  3. Press the Windows Logo key + R to open a Run dialog.
  4. Type the following into the Run dialog and press Enter:

%WinDir%\System32\Drivers\Etc

  1. Locate the hosts file, right-click on it, click on Rename, rename the file to old and press Enter.
  2. Move over the new “Hosts” file from wherever you saved it to, to %WinDir%\System32\Drivers\Etc.
  3. If you are asked to confirm the action while moving the file, do so.

Once the file has been moved, restart your computer and check to see if the problem has been resolved once it boots up.

Solution 7: Enable all of the ICMPv4-In rules in your computer’s Firewall settings

  1. Open the Start Menu.
  2. Search for “firewall“.
  3. Click on the search result titled Windows Firewall with Advanced Security.
  4. In the left pane of the window, click on Inbound Rules.
  5. In the right pane, locate every single Inbound Rule titled File and Printer Sharing (Echo Request – ICMPv4-In), right-click on it and click on Enable Rule.
  6. Once done, restart your computer.
  7. When the computer boots up, check to see if the issue has been fixed.

Conclusion

Conclusion

The nature of this error makes it difficult to pinpoint what exactly went wrong. One of the fixes in this article: Fixing Ping General Failure, will likely get you back on track. If you’re running traffic filters or blockers, you’ll probably know what they are so you could disable those first. However, the most common cause seems to be version complications; asking Windows to prefer the older protocol version may help you there.

SHARE THIS ARTICLE

There is never a time that isn’t right to help. If this information was useful to you, do well to share it with friends and loved ones. It’s your turn to help other people. You can share this article on your favorite social media handle.

Add a Comment

Your email address will not be published. Required fields are marked *