Can Ping But Cannot Browse (2026 Complete Guide)

Last updated: July 19, 2026 | Estimated reading time: 13 minutes

One of the most frustrating network issues you can encounter on a Windows PC is being able to ping websites and IP addresses successfully, but being unable to browse the web in any browser. This strange situation — where the command prompt tells you that your internet connection is working, but Chrome, Firefox, or Edge refuses to load any pages — can be incredibly confusing. You run a ping test, see successful replies, and assume your connection is fine, only to find that every website times out or returns an error in your browser. This issue is more common than you might think, and it usually points to a problem with DNS resolution, proxy settings, firewall rules, or browser-specific configurations rather than a fundamental connectivity issue. In this comprehensive guide, we will explain why you can ping but cannot browse, walk through every possible cause, and provide step-by-step solutions to get your web browsing working again.

Table of Contents

• Understanding the Ping vs Browse Problem
• DNS Resolution Problems
• Proxy Server Configuration Issues
• Firewall Blocking Browsers
• Winsock and TCP/IP Stack Issues
• Browser-Specific Issues
• Antivirus and Security Software
• Hosts File Modifications
• Step-by-Step Troubleshooting Guide
• Preventing the Issue in the Future
• Frequently Asked Questions

Understanding the Ping vs Browse Problem

To understand why you can ping but cannot browse, you need to understand the difference between how ping works and how web browsing works. These two activities use different network protocols and different ports, which is why one can work while the other fails.

Ping uses ICMP (Internet Control Message Protocol) to test basic connectivity between your computer and a remote server. When you ping google.com, your computer sends an ICMP echo request to Google’s servers and waits for an ICMP echo reply. This test only requires that your computer can reach the server at the IP level — it does not involve DNS resolution for domain names (ping resolves the name first, then pings the IP), does not use web ports, and does not involve any application-layer protocols.

Web browsing, on the other hand, uses HTTP (port 80) or HTTPS (port 443) over TCP to communicate with web servers. Before your browser can connect to a website, it must first resolve the domain name to an IP address using DNS (Domain Name System). Then it establishes a TCP connection to the server on port 80 or 443 and sends HTTP requests. This process involves multiple layers of networking — DNS resolution, TCP handshaking, and HTTP communication — any of which can fail independently.

This difference explains why ping can succeed while browsing fails. If your basic internet connectivity is working (ICMP works), but DNS resolution fails, or if a firewall blocks ports 80 and 443, or if a proxy configuration is misconfigured, your browser will be unable to reach websites even though ping shows that you have a working connection.

DNS Resolution Problems

DNS issues are the most common cause of being able to ping but not browse. When DNS resolution fails, your browser cannot translate domain names like google.com into IP addresses, so it cannot connect to websites. However, if you ping by IP address (like ping 8.8.8.8), the ping succeeds because it bypasses DNS entirely.

Symptoms of DNS issues: You can ping IP addresses like 8.8.8.8 but cannot ping domain names like google.com. Browsers show errors like “DNS_PROBE_FINISHED_NXDOMAIN” or “Server not found.” Some websites load while others do not, suggesting intermittent DNS failures.

Fixing DNS issues: The quickest fix is to change your DNS server to a public, reliable DNS provider. Google’s DNS (8.8.8.8 and 8.8.4.4) and Cloudflare’s DNS (1.1.1.1 and 1.0.0.1) are popular choices. You can change DNS settings in Windows by going to Network Settings, selecting your connection, clicking Properties, selecting Internet Protocol Version 4 (TCP/IPv4), and entering the new DNS server addresses.

You can also flush your DNS cache by opening Command Prompt as administrator and running the command ipconfig /flushdns. This clears any stale or corrupted DNS entries that may be causing resolution failures. After flushing the DNS cache, try browsing again to see if the issue is resolved.

Additionally, you can reset the DNS client service by running net stop dnscache and then net start dnscache in an elevated Command Prompt. This restarts the DNS caching service, which can resolve issues where the DNS cache has become corrupted.

Proxy Server Configuration Issues

Incorrect proxy settings are another common cause of the ping-but-no-browse problem. If your system is configured to use a proxy server that is not running or not reachable, your browser will attempt to route all traffic through the non-functional proxy, causing browsing to fail while ping (which does not use the proxy) continues to work.

Proxy settings can be changed accidentally by software installations, malware, VPN clients, or manual configuration. Even if you do not remember setting up a proxy, it is worth checking your proxy settings to rule this out as a cause.

To check proxy settings in Windows: Go to Settings > Network & Internet > Proxy. Check both “Automatically detect settings” and “Use a proxy server” sections. If “Use a proxy server” is enabled and you do not need a proxy, disable it. Also check the “Manual proxy setup” section to see if a proxy address is configured. If you are not using a proxy, clear any addresses listed there.

You can also check proxy settings in Internet Explorer (which still affects system-wide proxy settings in Windows) by going to Internet Options > Connections > LAN Settings. Make sure “Automatically detect settings” is checked and that no proxy server is configured unless you specifically need one.

Some VPN applications and corporate network software configure proxy settings automatically. If you recently installed or uninstalled a VPN, check that it did not leave behind proxy settings that are now causing problems. For guidance on setting up network connections in different scenarios, see our guide on how to get Ethernet in my room.

Firewall Blocking Browsers

Your Windows Firewall or third-party firewall may have rules that block web browser traffic while allowing ICMP (ping) traffic. This can happen after a software installation, a firewall configuration change, or a malware infection that modifies firewall rules.

To check Windows Firewall settings: Open Windows Security, go to Firewall & network protection, and click “Allow an app through firewall.” Check the list of allowed apps and make sure your web browser (Chrome, Firefox, Edge) is listed and allowed on both Private and Public networks. If it is not listed, click “Change settings” and then “Allow another app” to add your browser.

You can also temporarily disable Windows Firewall to test whether it is causing the issue. Go to Firewall & network protection, click on the active network profile, and toggle the firewall off. Try browsing again — if browsing works with the firewall disabled, the firewall rules need to be adjusted. Remember to re-enable the firewall immediately after testing.

Third-party firewalls like Norton, McAfee, Kaspersky, or ZoneAlarm can also block browser traffic. Check the settings of any third-party security software to ensure your browsers are allowed to access the internet. Some security suites have “application control” features that block specific programs from accessing the network, and these may need to be adjusted.

Winsock and TCP/IP Stack Issues

The Windows Sockets (Winsock) API and TCP/IP stack can sometimes become corrupted, leading to strange network behavior where some protocols work but others do not. This corruption can occur after malware infection, improper network configuration changes, or software conflicts.

To reset Winsock: Open Command Prompt as administrator and run the command netsh winsock reset. This resets the Winsock catalog to its default state, removing any corrupted entries. You will need to restart your computer after running this command for the changes to take effect.

To reset the TCP/IP stack: In the same elevated Command Prompt, run netsh int ip reset. This resets the TCP/IP stack to its default configuration, fixing any corruption in the IP configuration.

To renew your IP address: Run ipconfig /release followed by ipconfig /renew to release your current IP address and obtain a new one from your DHCP server (usually your router). This can fix issues where the IP configuration has become corrupted or conflicted.

These commands are safe to run and are commonly recommended for fixing various network issues. However, they will reset any custom network configurations you have set up, so be prepared to reconfigure custom settings afterward.

Browser-Specific Issues

Sometimes the problem is isolated to a specific browser rather than affecting all browsers on the system. If you can browse in one browser but not another, the issue is with the browser’s configuration rather than the system’s network settings.

Clear browser data: Corrupted cookies, cache, or browsing data can cause loading issues. Clear your browser’s cache, cookies, and browsing history, then restart the browser and try again.

Disable browser extensions: Some browser extensions, particularly ad blockers, VPN extensions, and privacy tools, can interfere with web browsing. Disable all extensions and try browsing again. If it works, re-enable extensions one by one to identify the culprit.

Reset browser settings: Most browsers have a “Reset to default settings” option that clears all custom configurations, extensions, and data. This is a more drastic step but can resolve issues caused by deeply corrupted settings.

Check browser proxy settings: Browsers can have their own proxy settings separate from the system proxy. Check the browser’s network settings to ensure it is not configured to use a proxy that does not exist.

If browsing works in one browser but not others, compare the settings between the working and non-working browsers to identify the difference. Common culprits include proxy settings, DNS settings, and extension configurations. For tips on troubleshooting WiFi connectivity issues, see our article on do WiFi adapters go bad.

Antivirus and Security Software

Antivirus and internet security suites sometimes interfere with web browsing by scanning web traffic and blocking suspicious connections. This can cause browsing to fail while ping continues to work, since antivirus software typically does not intercept ICMP traffic.

To test for antivirus interference: Temporarily disable your antivirus software’s real-time protection and web scanning features, then try browsing again. If browsing works, the antivirus was the cause. Re-enable the antivirus and add your browser to its whitelist or exception list.

Some antivirus programs have a “web shield” or “web protection” feature that scans HTTP and HTTPS traffic. If this feature becomes corrupted or overly aggressive, it can block all web traffic. Check your antivirus settings for web protection options and try disabling and re-enabling the feature.

Windows Defender (now called Microsoft Defender) is generally less likely to cause this issue than third-party antivirus software, but it is still worth checking its settings if you cannot find another cause. Go to Windows Security > Virus & threat protection > Manage settings and review the available options.

Hosts File Modifications

The Windows hosts file is a local file that maps hostnames to IP addresses. It is sometimes modified by malware, ad-blocking software, or network configuration tools to redirect or block specific websites. If the hosts file has been modified to block major websites or redirect them to incorrect addresses, browsing will fail while ping may still work for IP addresses.

To check the hosts file: Open Notepad as administrator, then open the file at C:\Windows\System32\drivers\etc\hosts. The file should contain only comments (lines starting with #) and localhost entries. If you see any other entries, they may be causing the browsing issue.

Legitimate entries in the hosts file might include a localhost mapping (127.0.0.1 localhost) and possibly IPv6 localhost (::1 localhost). Any other entries, especially those mapping well-known websites to unusual IP addresses, should be investigated and removed if they are not intentional.

Some ad-blocking tools and privacy software modify the hosts file to block tracking domains. If you recently installed such software, check whether it modified the hosts file in a way that is blocking more than intended. You can safely remove non-essential entries from the hosts file to restore normal browsing.

Step-by-Step Troubleshooting Guide

Follow this systematic troubleshooting process to identify and fix the cause of your ping-but-no-browse issue.

Step 1: Determine the scope of the problem. Try browsing in multiple browsers (Chrome, Firefox, Edge). Try pinging both IP addresses and domain names. Try accessing websites by IP address in your browser (type the IP directly in the address bar). This helps you narrow down whether the issue is DNS-related, browser-specific, or system-wide.

Step 2: Flush DNS and change DNS servers. Run ipconfig /flushdns in an elevated Command Prompt. Then change your DNS servers to Google (8.8.8.8, 8.8.4.4) or Cloudflare (1.1.1.1, 1.0.0.1). Try browsing again.

Step 3: Check proxy settings. Go to Settings > Network & Internet > Proxy and disable any proxy configuration. Also check Internet Options > Connections > LAN Settings for proxy settings.

Step 4: Check firewall settings. Ensure your browsers are allowed through Windows Firewall. Temporarily disable the firewall to test. Check third-party firewall and antivirus settings.

Step 5: Reset network stack. Run these commands in an elevated Command Prompt:

• netsh winsock reset
• netsh int ip reset
• ipconfig /release
• ipconfig /renew
• ipconfig /flushdns

Restart your computer after running these commands.

Step 6: Check the hosts file. Open the hosts file with administrator privileges and look for suspicious or unexpected entries. Remove any non-standard entries.

Step 7: Test with a different network. If possible, connect to a different network (mobile hotspot, different WiFi) to determine if the issue is specific to your network or persists across networks.

Step 8: Check for malware. Run a full system scan with your antivirus software and consider running a scan with Malwarebytes or another anti-malware tool to check for infections that may be modifying network settings.

For more comprehensive network troubleshooting, our article on can ping website but not browse provides additional solutions and context for this specific issue.

Preventing the Issue in the Future

Once you have resolved the ping-but-no-browse issue, take steps to prevent it from recurring.

Be careful with VPN software. VPN applications can modify proxy and DNS settings. Always properly uninstall VPN software rather than just deleting the files, and check your network settings after uninstalling.

Use reputable antivirus software. Choose an antivirus program that does not aggressively modify network settings. Windows Defender is sufficient for most users and is less likely to cause network issues than some third-party solutions.

Be cautious with network optimization tools. Some software claims to optimize your network performance but actually modifies network settings in ways that can cause problems. Avoid these tools unless you fully understand what they do.

Regularly check your network settings. Periodically verify that your DNS settings, proxy settings, and firewall rules have not been changed by software installations or updates. Catching these changes early prevents browsing issues from developing.

For WiFi-related issues that might contribute to network problems, see our guide on do WiFi adapters go bad, which explains how to identify and replace failing wireless hardware.

Frequently Asked Questions

Why can I ping but not browse websites?

The most common causes are DNS resolution failures, incorrect proxy settings, firewall rules blocking browser ports, or corrupted Winsock/TCP/IP stack. Ping uses ICMP protocol which works independently of DNS and HTTP, so basic connectivity can work while web browsing fails due to issues at higher network layers.

How do I fix DNS issues that prevent browsing?

Run ipconfig /flushdns in an elevated Command Prompt to clear the DNS cache. Then change your DNS servers to Google (8.8.8.8) or Cloudflare (1.1.1.1) in your network adapter settings. If the issue persists, restart the DNS client service with net stop dnscache and net start dnscache.

Could my proxy settings be causing the browsing issue?

Yes, incorrect proxy settings are one of the most common causes. Check Settings > Network & Internet > Proxy and disable any proxy configuration you do not need. Also check Internet Options > Connections > LAN Settings. VPN software and some corporate tools can modify proxy settings without your knowledge.

Will resetting Winsock fix the browsing issue?

Resetting Winsock can fix the issue if the Winsock catalog has been corrupted by malware, software conflicts, or improper network configuration changes. Run netsh winsock reset in an elevated Command Prompt and restart your computer. This is a safe operation that resets network programming interfaces to their default state.

Can my firewall block browsing but allow ping?

Yes, Windows Firewall or third-party firewalls can have rules that allow ICMP (ping) traffic while blocking HTTP/HTTPS ports (80 and 443) used by web browsers. Check that your browsers are listed as allowed apps in the firewall settings. You can also temporarily disable the firewall to test whether it is the cause.

Why does only one browser have the problem?

If only one browser is affected, the issue is with that browser’s specific configuration, extensions, or cached data. Clear the browser’s cache and cookies, disable all extensions, and try resetting the browser to its default settings. Check the browser’s own proxy and network settings separately from the system settings.

Can malware cause the ping-but-no-browse issue?

Yes, some malware modifies DNS settings, proxy settings, the hosts file, or firewall rules to redirect or block web traffic. Run a full system scan with your antivirus and consider scanning with Malwarebytes. Check the hosts file at C:\Windows\System32\drivers\etc\hosts for suspicious entries.

Do I need to restart my computer after fixing network settings?

In many cases, yes. After running network reset commands like netsh winsock reset or changing DNS settings, a restart ensures all changes take effect properly. Some changes apply immediately, but a restart resolves any lingering cached settings that might still cause issues.

Could my WiFi adapter be causing this issue?

A failing WiFi adapter typically causes broader connectivity issues, not just browsing failures while ping works. However, a WiFi adapter with driver issues could potentially cause protocol-specific problems. Update or reinstall your WiFi adapter drivers if you suspect it is involved. See our article on do WiFi adapters go bad for more information.