Can Ping Website But Not Browse (2026 Complete Guide)

If you can ping a website but cannot browse to it, you are experiencing one of the most common and frustrating network issues on Windows. This problem occurs when your computer has basic network connectivity (ICMP packets work) but cannot establish the higher-level connections needed for web browsing (TCP/UDP on ports 80 and 443). The good news is that this issue is almost always solvable through a series of troubleshooting steps that address DNS configuration, proxy settings, firewall rules, and browser-specific problems. In this comprehensive guide, we will explain exactly why this issue occurs, walk you through every possible fix step by step, and help you identify whether the problem lies with your DNS, proxy, firewall, browser, or ISP. Whether you are dealing with this issue on a single browser, across all browsers, or on a specific website, this guide has you covered.

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

Table of Contents

• Understanding the Problem: Ping vs Browse
• Fix 1: DNS Issues and Solutions
• Fix 2: Proxy Settings
• Fix 3: Firewall and Antivirus
• Fix 4: Browser-Specific Issues
• Fix 5: Flush DNS Cache
• Fix 6: Reset Winsock and TCP/IP
• Fix 7: MTU Settings
• Fix 8: Wired vs Wireless Issues
• Fix 9: ISP and Router Issues
• Fix 10: Advanced Troubleshooting
• Frequently Asked Questions

Understanding the Problem: Ping vs Browse

To fix the “can ping but cannot browse” issue, you first need to understand why these two functions behave differently. Ping uses ICMP (Internet Control Message Protocol) to test basic network connectivity. When you ping a website, your computer sends a small ICMP echo request packet to the target server and waits for an echo reply. This process does not involve DNS resolution (when using an IP address), does not use TCP or UDP ports, and does not go through your web browser.

Web browsing, on the other hand, uses a completely different set of protocols and processes. When you type a URL into your browser, the following steps occur:

Step 1: DNS Resolution – Your browser asks a DNS server to translate the domain name (like example.com) into an IP address. If DNS is not working, the browser cannot find the server.

Step 2: TCP Connection – Your browser establishes a TCP connection to the server on port 80 (HTTP) or port 443 (HTTPS). This connection may be blocked by firewalls or proxy settings.

Step 3: HTTP Request – Your browser sends an HTTP request to the server and waits for a response. This request includes headers that may be filtered or modified by proxies and firewalls.

Step 4: TLS/SSL Handshake – For HTTPS connections, a TLS handshake occurs to establish an encrypted connection. Certificate issues or TLS configuration problems can prevent this handshake from completing.

Because ping and browsing use different protocols, a working ping does not guarantee that browsing will work. The issue typically lies in one of the intermediate steps: DNS, TCP/UDP port blocking, proxy configuration, or browser settings.

Fix 1: DNS Issues and Solutions

DNS (Domain Name System) issues are the most common cause of being able to ping but not browse. If DNS resolution is failing, your browser cannot translate domain names into IP addresses, preventing web pages from loading. However, if you ping an IP address directly (like ping 8.8.8.8), ping will still work because it bypasses DNS entirely.

Test for DNS issues: Open Command Prompt and type nslookup example.com. If this command fails or returns an error, your DNS is not working correctly. You can also try browsing to a website using its IP address directly (like http://142.250.190.46 for Google) to confirm that DNS is the issue.

Solution 1: Change DNS Servers

Step 1: Press Windows + I to open Settings, then navigate to Network & Internet > Ethernet (or Wi-Fi).

Step 2: Click on your active connection and scroll down to DNS server assignment. Click Edit.

Step 3: Change the DNS settings from Automatic to Manual.

Step 4: Enter one of these reliable public DNS servers:

Step 5: Click Save and try browsing again.

Solution 2: Reset DNS via Command Prompt

Open Command Prompt as Administrator and run these commands:

ipconfig /flushdns
ipconfig /registerdns
netsh int ip set dns “Wi-Fi” static 8.8.8.8
netsh int ip add dns “Wi-Fi” 8.8.4.4 index=2

Replace “Wi-Fi” with “Ethernet” if you are using a wired connection.

Fix 2: Proxy Settings

Incorrect proxy settings are another very common cause of the can-ping-but-cannot-browse issue. A misconfigured proxy can intercept and block HTTP/HTTPS traffic while allowing ICMP (ping) traffic to pass through.

Step 1: Press Windows + I to open Settings, then navigate to Network & Internet > Proxy.

Step 2: Check if “Use a proxy server” is turned on. If you are not intentionally using a proxy, turn this off.

Step 3: If you need a proxy for your network, verify that the proxy address and port are correct. An incorrect proxy address will block all web traffic.

Step 4: Also check “Automatically detect settings” and make sure it is turned on.

Step 5: If you suspect proxy settings are corrupted, you can reset them via Command Prompt:

netsh winhttp reset proxy

Step 6: Restart your browser and try browsing again.

Proxy settings can be changed by VPN software, malware, or corporate network policies. If you recently installed or uninstalled a VPN, check that it did not leave behind proxy settings.

Fix 3: Firewall and Antivirus

Your firewall or antivirus software may be blocking HTTP and HTTPS traffic while allowing ICMP (ping) traffic. This is a common issue with third-party security software that implements aggressive web filtering.

Windows Defender Firewall:

Step 1: Press Windows + R, type wf.msc, and press Enter to open Windows Defender Firewall with Advanced Security.

Step 2: Click on Inbound Rules and look for rules that block HTTP (port 80) or HTTPS (port 443) traffic. If you find any, right-click them and select Disable Rule.

Step 3: Check Outbound Rules for similar blocking rules.

Step 4: As a quick test, you can temporarily disable Windows Defender Firewall by going to Control Panel > System and Security > Windows Defender Firewall > Turn Windows Defender Firewall on or off. Turn it off for all network types temporarily, test browsing, and then re-enable it.

Third-Party Antivirus:

If you use third-party antivirus software (Norton, McAfee, Kaspersky, Bitdefender, etc.), it may have its own firewall or web protection module that is blocking traffic. Open your antivirus software and look for firewall or web protection settings. Try temporarily disabling the web protection feature to see if browsing works without it.

VPN Software:

If you have a VPN installed, it may be interfering with your connection. Some VPNs modify network settings even when they are not actively connected. Try fully disconnecting or uninstalling the VPN to see if browsing is restored.

Fix 4: Browser-Specific Issues

Sometimes the issue is isolated to a specific browser rather than being a system-wide problem. Here are browser-specific fixes:

Google Chrome:

Step 1: Type chrome://settings/reset in the address bar and press Enter.

Step 2: Click “Restore settings to their original defaults” to reset Chrome to its default state. This clears extensions, cache, and settings that may be causing the issue.

Step 3: Type chrome://flags in the address bar and click “Reset all” to restore all experimental flags to their defaults.

Step 4: Try Chrome in Incognito mode (Ctrl + Shift + N) to see if an extension is causing the issue. If browsing works in Incognito, an extension is likely the culprit.

Mozilla Firefox:

Step 1: Type about:support in the address bar and click “Refresh Firefox” to reset Firefox to its default state.

Step 2: Check Firefox proxy settings: type about:preferences in the address bar, scroll to Network Settings, click Settings, and ensure “No proxy” is selected (or configure correctly).

Microsoft Edge:

Step 1: Go to Settings > Reset settings > Restore settings to their default values.

Step 2: Check Edge proxy settings through Settings > System and performance > Open your computer’s proxy settings.

If browsing works in one browser but not others, the issue is browser-specific. If browsing fails in all browsers, the issue is system-wide and requires the DNS, proxy, firewall, or network fixes described in this guide.

Fix 5: Flush DNS Cache

The DNS resolver cache stores recently resolved DNS entries, and a corrupted cache can cause browsing issues even when DNS servers are working correctly.

Step 1: Open Command Prompt as Administrator (right-click Start, select Command Prompt or PowerShell (Admin)).

Step 2: Run the following commands one at a time:

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

Step 3: Restart your computer after running all commands.

Step 4: Test browsing after the restart.

The flushdns command clears the DNS resolver cache, forcing your computer to resolve all domain names fresh. The release and renew commands obtain a new IP address from your DHCP server, which can resolve IP address conflicts. The winsock reset restores the Windows networking stack to its default state, fixing corruption that may have accumulated over time.

Fix 6: Reset Winsock and TCP/IP

Winsock is the Windows API that handles network input/output operations. When Winsock becomes corrupted, it can cause exactly the symptoms described in this article: ping works but browsing does not.

Step 1: Open Command Prompt as Administrator.

Step 2: Run the following commands:

netsh winsock reset
netsh int ip reset
netsh int ipv4 reset
netsh int ipv6 reset
netsh int tcp reset

Step 3: Restart your computer.

Step 4: After the restart, run ipconfig /flushdns to clear the DNS cache.

Step 5: Test browsing.

These commands reset the entire Windows networking stack to its default state. This is a comprehensive fix that addresses many networking issues at once. Note that you may need to reconfigure custom network settings (like static IP addresses or VPN connections) after running these commands.

Fix 7: MTU Settings

The Maximum Transmission Unit (MTU) determines the largest packet size that can be transmitted over your network. If the MTU is set too high, some websites may fail to load while ping (which uses small packets) continues to work.

Step 1: Open Command Prompt as Administrator.

Step 2: Check your current MTU setting: netsh interface ipv4 show subinterfaces

Step 3: Test the optimal MTU for your connection: ping example.com -f -l 1472. If you get “Packet needs to be fragmented but DF set,” reduce the number and try again. The optimal MTU is the largest number that does not cause fragmentation, plus 28 (for IP and ICMP headers).

Step 4: Set the optimal MTU: netsh interface ipv4 set subinterface “Wi-Fi” mtu=1492 store=persistent (replace 1492 with your optimal value and “Wi-Fi” with your connection name).

Common optimal MTU values are 1492 for PPPoE connections, 1500 for standard Ethernet, and 1400 for some VPN connections. If you use a VPN, the VPN may have its own MTU requirements.

Fix 8: Wired vs Wireless Issues

The issue may be specific to your connection type. Ethernet and wireless connections have different characteristics and potential problems:

If you are on Wi-Fi:

Try switching to a wired Ethernet connection if possible. Wi-Fi connections are more susceptible to interference, signal strength issues, and driver problems. If your Wi-Fi adapter is aging or malfunctioning, it may maintain basic ICMP connectivity while struggling with the sustained TCP connections needed for web browsing. For more information on Wi-Fi adapter issues, check out our article on do Wi-Fi adapters go bad.

If you are on Ethernet:

Try a different Ethernet cable and a different port on your router or switch. A damaged cable can sometimes maintain basic connectivity while dropping the higher-bandwidth connections needed for browsing. If you need to set up Ethernet in a different room, read our guide on how to get Ethernet in my room for practical solutions.

Network Adapter Reset:

Step 1: Press Windows + X and select Device Manager.

Step 2: Expand Network adapters and right-click your network adapter.

Step 3: Select Uninstall device and check “Delete the driver software for this device” if available.

Step 4: Restart your computer. Windows will automatically reinstall the driver.

Fix 9: ISP and Router Issues

If the issue is not with your computer, it may be with your ISP or router:

Router Restart: Unplug your router from power, wait 30 seconds, and plug it back in. Wait 2-3 minutes for it to fully restart, then test browsing.

DNS on Router: Log into your router’s admin interface and check its DNS settings. Try changing the router’s DNS to Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1).

ISP DNS Issues: Your ISP’s DNS servers may be experiencing problems. Changing your computer’s DNS servers to a public alternative (as described in Fix 1) can bypass ISP DNS issues.

ISP Firewall: Some ISPs implement transparent proxies or firewalls that can block web traffic. Contact your ISP if you suspect they are blocking traffic.

Router Firmware: Check if your router has a firmware update available. Outdated router firmware can cause various networking issues, including the one described in this article.

Fix 10: Advanced Troubleshooting

If none of the above fixes have resolved the issue, try these advanced troubleshooting steps:

Network Reset (Windows 10/11): Go to Settings > Network & Internet > Advanced network settings > Network reset. Click “Reset now” to perform a complete network reset. This removes and reinstalls all network adapters and resets all networking components to their defaults.

Check Hosts File: Open Notepad as Administrator and open the file C:\Windows\System32\drivers\etc\hosts. Check for any entries that block or redirect websites. If you see suspicious entries, remove them.

Malware Scan: Some malware modifies network settings to redirect traffic through malicious servers. Run a full system scan with Windows Defender and a second scan with Malwarebytes to rule out malware.

Check for Corrupted System Files: Run System File Checker to repair corrupted system files: sfc /scannow in an elevated Command Prompt. If SFC finds and repairs issues, restart and test browsing.

TCP/IP Diagnostics: Use the built-in Windows Network Diagnostics tool by right-clicking the network icon in the system tray and selecting “Troubleshoot problems.” While this tool does not fix everything, it can identify some issues automatically.

Frequently Asked Questions

The “can ping but cannot browse” issue is almost always solvable through systematic troubleshooting. Start with the most common causes (DNS and proxy settings), then move through firewall, browser, and network stack fixes. In most cases, one of the first three fixes (DNS change, proxy reset, or firewall adjustment) will resolve the issue. If you need to establish a more permanent wired connection to prevent future wireless-related issues, check out our guide on how to get Ethernet in my room.

Related posts:

How to Overclock Ryzen 7 3700X (2026 Complete Guide) Can Not Find Script File Startupcheck.Vbs How to Stop Onmicrosoft Spam (2026 Complete Guide) How to Setup StoreMI (2026 Complete Guide)