User Tools

Site Tools


networking:ping_transmit_failed_general_failure

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
networking:ping_transmit_failed_general_failure [2024/09/01 15:33] apereznetworking:ping_transmit_failed_general_failure [2024/09/01 16:02] (current) aperez
Line 81: Line 81:
 When the system loads, check if you can ping successfully. When the system loads, check if you can ping successfully.
  
-**Fix 3: Remove any applications that block HTTP traffic**+====== Fix 3: Remove any applications that block HTTP traffic ====== 
  
 If you’ve installed any applications on your Windows machine that could, in one way or another, be capable of blocking HTTP traffic coming to or from your PC, you must uninstall them. If you’ve installed any applications on your Windows machine that could, in one way or another, be capable of blocking HTTP traffic coming to or from your PC, you must uninstall them.
Line 92: Line 93:
  
   * Open the Control Panel, and go to Programs > Uninstall a program.   * Open the Control Panel, and go to Programs > Uninstall a program.
 +
 +{{ :networking:control-panel-uninstall-program-ezgif.com-webp-to-jpg-converter.jpg?600 |}}
 +
 +Right-click the suspect program and select Uninstall.
 +
 +{{ :networking:uninstall-a-program-1.png?600 |}}
 +
 +Additionally, if you’re using VPN software, disable it when testing to check if it’s causing the error.
 +
 +====== Fix 4: Flush your DNS cache ======
 +
 +Flushing your computer’s DNS is an effective solution to the “**Ping: Transmit failed. General failure**” error on Windows 10/11.
 +
 +When you **clear the DNS cache**, the old IP records are deleted, allowing your system to get fresh ones when you access the server. In fact, flushing your computer’s DNS cache from time to time is considered healthy.
 +
 +Clearing your DNS cache will also reset your Winsock catalog, and this might help to fix the problem. To flush the DNS cache, follow the instructions below:
 +
 +Launch Windows PowerShell. To do that, press the **Win + X** Use the keyboard shortcut and **select Windows PowerShell (Admin)**. Alternatively, use the **Win + S** combination to bring up the Windows search box, **type PowerShell**, and hit the Enter key.
 +
 +{{ :networking:open-powershell-1.png?300 |}}
 +
 +Click Yes when prompted by the system.
 +
 +{{ :networking:ipconfigrelease-ezgif.com-webp-to-jpg-converter.jpg?600 |}}
 +
 +In the Windows PowerShell window, type or paste the commands below one by one and press Enter after each one:
 +
 +**ipconfig /release**
 +
 +**ipconfig /renew**
 +
 +**ipconfig /flushdns**
 +
 +**netsh int ip reset c:\tcp.txt**
 +
 +**netsh winsock reset**
 +
 +After all the commands have been executed successfully, reboot Windows and check if your ping issue has been resolved.
 +
 +===== Fix 5: Remove All Ipv6 and IPv4 Transition Technologies =====
 +
 +Transition technologies have been developed to simplify the task of migrating to IPv6 from IPv4. However, they may cause problems when pinging.
 +
 +If you’re using any kind of protocol transition technology on your computer, try disabling it to check if this has fixed the issue.
 +
 +Here are the steps:
 +
 +You’ll need to run Windows PowerShell as an admin. To do that, press the Windows logo and X keys simultaneously and select Windows PowerShell (Admin)”. You can also run the Command Prompt with admin rights. Simply press the Win + R keyboard shortcut, type CMD into the text box, and hit the Ctrl + Shift + Enter combination.
 +
 +{{ :networking:open-windows-powershell-1.png?300 |}}
 +
 +In the elevated PowerShell or Command Prompt window, type or paste the commands below one after the other and press Enter after each one:
 +
 +**netsh int ipv6 isatap set state disabled**
 +
 +**netsh int ipv6 6to4 set state disabled**
 +
 +**netsh interface teredo set state disabled**
 +
 +Exit the Command Prompt or Windows PowerShell and restart your computer.
 +Now check if the ping problem still exists.
 +
 +===== Fix 6: Reset your PC’s TCP/IP =====
 +
 +If you’re still struggling to resolve the ping general failure error, try resetting your PC’s TCP/IP to check if it works this time.
 +
 +Here’s how:
 +
 +Run the Command Prompt or Windows PowerShell with admin rights.
 +
 +{{ :networking:run-powershell-1.png?300 |}}
 +
 +Click Yes when prompted by the system to grant administrator access.
 +
 +{{ :networking:grant-admin-access-1.png?400 |}}
 +
 +Type or paste the command **netsh i i r r** and press Enter.
 +
 +Next, type or paste the command **netsh winsock reset** and hit Enter.
 +
 +Exit the Command Prompt or Windows PowerShell and restart your computer. This solution should fix the ping failure error.
 +
 +==== Fix 7: Reset your PC’s hosts file ====
 +
 +If nothing seems to work in your case, you may want to try resetting your computer’s host file.
 +
 +Note: What is a Computer's Hosts File?: A computer’s hosts file is a local text file that maps IP addresses to hostnames. When a user tries to access a website, the operating system first checks this file before querying DNS servers, allowing for custom or overridden mappings for specific domains.
 +
 +Here is the step-by-step guide to reset your computer’s host file:
 +
 +  * Go to Start and launch Notepad.
 +  * Paste the following script into a new Notepad page:
 +
 +  # 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 handled within DNS itself.
 +  # 127.0.0.1 localhost
 +  # ::1 localhost
 +
 +{{ :networking:enter-script-into-notepad-1.png?600 |}}
 +
 +Go to File > Save As.
 +
 +{{ :networking:select-save-as-1.png?600 |}}
 +
 +Assign the file an appropriate title (like hosts1), and click on OK to save it to your preferred location.
 +
 +{{ :networking:save-hosts-1-1.png?600 |}}
 +
 +  * Next, open the “Run” command using the Win + R shortcut.
 +  * Type %WinDir%\System32\Drivers\Etc into the text box and press Enter.
 +
 +{{ :networking:type-windir-system-drivers-etc-1.png?400 |}}
 +
 +Search for the original hosts file here.
 +
 +{{ :networking:search-for-hosts-file-ezgif.com-webp-to-jpg-converter.jpg?600 |}}
 +
 +Right-click on it and select Rename.
 +
 +{{ :networking:proceso1.jpg?600 |}}
 +
 +Rename it to something like hostsOLD and hit Enter.
 +
 +{{ :networking:old.jpg?600 |}}
 +
 +Now, move the newly created hosts1 file from where you previously saved it to the %WinDir%\System32\Drivers\Etc directory.
 +
 +{{ :networking:old1.jpg?700 |}}
 +
 +If you’re prompted to confirm your action, select “Yes”.
 +
 +{{ :networking:confirm-your-action-1.png?400 |}}
 +
 +Now restart your PC and try running the ping command again.
 +
 +----
 +----
 +==== Overview command: ====
 +  
 +Open win + r:  for Net setting, write:** Ncpa.cpl**
 +
 +  ipconfig /flushdns
 +  netsh winsock reset
 +  netsh int ip reset
 +  netsh int ipv6 isatap set state disabled
 +  netsh int ipv6 6to4 set state disabled
 +  netsh interface teredo set state disable
 +  Netsh winsock reset reset.txt
 +
 +----
 +----
  
  
networking/ping_transmit_failed_general_failure.1725222827.txt.gz · Last modified: 2024/09/01 15:33 by aperez

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki