NetworkingAdvanced

Ping Works but Internet Does Not Work – Complete Windows Network Troubleshooting Guide

One of the more confusing Windows networking problems occurs when Ping works successfully, but websites, applications, or other Internet services do not work...

Bison Technical Team Enterprise IT specialists

Updated 18 Aug 2026 17 min read 3 total views

One of the more confusing Windows networking problems occurs when Ping works successfully, but websites, applications, or other Internet services do not work.

For example, you may run:

ping 8.8.8.8

and receive:

Reply from 8.8.8.8: bytes=32 time=25ms TTL=117
Reply from 8.8.8.8: bytes=32 time=24ms TTL=117
Reply from 8.8.8.8: bytes=32 time=26ms TTL=117

Yet when you open Chrome, Microsoft Edge, Firefox, Outlook, or another Internet-dependent application, it may display errors such as:

This site can't be reached
DNS_PROBE_FINISHED_NXDOMAIN
DNS server not responding
ERR_CONNECTION_TIMED_OUT
ERR_PROXY_CONNECTION_FAILED
No Internet
Unable to connect
Server not found

This situation is possible because successful Ping does not prove that every part of the Internet connection is working.

Ping primarily tests ICMP connectivity. Web browsing depends on several additional components, including DNS, TCP, TLS/SSL, ports 80 and 443, proxy configuration, firewall rules, browser configuration, and the Windows networking stack.

1. What Does a Successful Ping Actually Prove?

The Windows ping command normally sends ICMP Echo Request packets to a destination and waits for Echo Replies.

For example:

ping 8.8.8.8

A successful response generally proves that:

Your network adapter is functioning at least sufficiently to send and receive the test traffic.
Your computer has an IP route to the destination.
The default gateway and upstream routing are working sufficiently for ICMP.
The remote destination is responding to ICMP.
Basic IP connectivity exists between your computer and that destination.

However, it does not necessarily prove that:

DNS is working.
TCP connections are working.
HTTPS is working.
Port 443 is accessible.
Port 80 is accessible.
Your proxy configuration is correct.
Your browser is correctly configured.
TLS certificate validation is working.
Your firewall permits browser traffic.
Your antivirus or endpoint security software permits web traffic.
Your VPN is correctly routing traffic.

This distinction is the key to troubleshooting the problem.

2. First Test: Ping an IP Address

Open Command Prompt and run:

ping 8.8.8.8

You can also test another public IP:

ping 1.1.1.1

If these IP addresses respond, basic Internet routing is probably available.

Now test a hostname:

ping google.com

The difference between these tests is extremely important.

3. Scenario A: 8.8.8.8 Works but google.com Does Not

Suppose:

ping 8.8.8.8

works, but:

ping google.com

returns:

Ping request could not find host google.com.

This strongly indicates a DNS resolution problem.

Your computer can reach the Internet using IP addresses, but it cannot translate domain names such as:

google.com
microsoft.com
bison.co.in

into their corresponding IP addresses.

Since normal users access websites by domain name rather than IP address, the Internet can appear completely unavailable.

4. Check the Current DNS Configuration

Run:

ipconfig /all

Look for the active Ethernet or Wi-Fi adapter.

Check:

IPv4 Address
Subnet Mask
Default Gateway
DNS Servers
DHCP Enabled

For example:

IPv4 Address: 192.168.1.25
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DNS Servers: 192.168.1.1

Pay particular attention to DNS Servers.

An incorrect, unavailable, blocked, or compromised DNS server can cause the exact symptom where Ping to an IP works but Internet browsing does not.

5. Test DNS Using NSLOOKUP

Run:

nslookup google.com

A working DNS configuration should return one or more IP addresses.

If you receive messages such as:

DNS request timed out

or:

Server: Unknown

combined with failed lookups, investigate the configured DNS server.

You can also bypass the currently configured DNS server for a test:

nslookup google.com 8.8.8.8

and:

nslookup google.com 1.1.1.1

If your normal DNS lookup fails but the lookup through a known public resolver succeeds, your configured DNS service is a likely cause.

6. Flush the Windows DNS Cache

Windows caches DNS responses.

A corrupted or outdated DNS cache can sometimes create browsing problems.

Open Command Prompt as Administrator and run:

ipconfig /flushdns

You should receive:

Successfully flushed the DNS Resolver Cache.

Then test:

nslookup google.com

and try the browser again.

7. Change the DNS Server Temporarily

For troubleshooting, you can temporarily configure a known DNS resolver.

Examples include:

Google Public DNS

Preferred DNS: 8.8.8.8
Alternate DNS: 8.8.4.4

Cloudflare DNS

Preferred DNS: 1.1.1.1
Alternate DNS: 1.0.0.1

After changing DNS, run:

ipconfig /flushdns

Then:

nslookup google.com

If websites immediately begin working, investigate the previous DNS server, router DNS forwarding, DHCP configuration, or ISP DNS service.

8. Scenario B: Both IP and Domain Ping Work, but Browser Does Not

This is a different problem.

Suppose both commands work:

ping 8.8.8.8
ping google.com

If google.com resolves to an IP and replies, DNS is probably functioning.

The next investigation should therefore move to:

Proxy settings
TCP connectivity
HTTPS/port 443
Firewall
Antivirus/web protection
VPN
Browser configuration
TLS
Windows networking stack

9. Test HTTPS Port 443

Ping uses ICMP, whereas most modern websites use HTTPS over TCP port 443.

Therefore:

Ping working ≠ HTTPS working

PowerShell provides a useful test:

Test-NetConnection google.com -Port 443

Look for:

TcpTestSucceeded : True

If it returns:

TcpTestSucceeded : False

you have discovered an important clue.

Something may be preventing TCP/443 connectivity.

Possible causes include:

Firewall rules
Security software
Router filtering
VPN configuration
ISP filtering
Network security appliance
Routing problems

You can similarly test HTTP:

Test-NetConnection example.com -Port 80

10. Check Windows Proxy Settings

An incorrect proxy configuration is a common reason browsers cannot access the Internet while Ping continues to work.

Go to:

Settings → Network & Internet → Proxy

If your organization does not intentionally use a proxy, check for unexpected settings such as:

Use a proxy server
Setup script
Unknown proxy IP
Unknown proxy port

Do not disable an intentionally configured corporate proxy without checking with the network administrator.

11. Check WinHTTP Proxy Configuration

Windows also maintains WinHTTP proxy configuration.

Run:

netsh winhttp show proxy

A direct configuration normally displays:

Direct access (no proxy server).

If an unwanted proxy appears, and you are certain your environment does not require it, an administrator can reset it with:

netsh winhttp reset proxy

This can be particularly useful when system applications fail while basic network connectivity remains available.

12. Why Malware Can Cause This Problem

Some malware, potentially unwanted applications, adware, and malicious browser extensions modify:

Proxy configuration
DNS servers
Hosts file
Browser policies
Root certificates
Firewall rules
Network adapters

After malware is removed, the altered networking configuration may remain.

Therefore, if the problem appeared after a malware infection or cleanup, inspect proxy, DNS, hosts file, browser extensions, certificates, and firewall configuration carefully.

13. Reset Winsock

Winsock provides interfaces used by Windows networking applications.

If the Winsock catalog becomes corrupted, applications may experience connectivity problems even when some lower-level tests still work.

Open Command Prompt as Administrator and run:

netsh winsock reset

Restart Windows afterward.

14. Reset the TCP/IP Stack

If Winsock reset does not resolve the problem, reset TCP/IP:

netsh int ip reset

Restart the computer after the command completes.

You can combine common repair commands:

ipconfig /flushdns
netsh winsock reset
netsh int ip reset

Then reboot Windows.

Be aware that network resets can affect manually configured networking settings, so document important static IP, DNS, gateway, VPN, or specialized adapter settings first.

15. Renew the DHCP Configuration

For computers receiving their configuration through DHCP, you can renew the lease:

ipconfig /release
ipconfig /renew

Then check:

ipconfig /all

Verify that the computer received appropriate:

IP address
Subnet mask
Default gateway
DNS servers

Do not use this procedure casually on remotely administered systems if losing network connectivity could lock you out.

16. Check the Default Gateway

Run:

ipconfig

Identify the default gateway, for example:

192.168.1.1

Then:

ping 192.168.1.1

If the gateway does not respond, investigate the local LAN, Wi-Fi, VLAN, adapter, switch, router, or firewall before concentrating on Internet services.

Note that some gateways intentionally ignore ICMP, so a failed gateway Ping alone is not conclusive.

17. Trace the Route

Run:

tracert 8.8.8.8

and:

tracert google.com

This can help identify where traffic stops.

However, some routers intentionally do not respond to traceroute probes. Therefore, * * * at an intermediate hop does not automatically mean that router is faulty.

The final destination and overall pattern matter more.

18. Check the Windows Hosts File

Windows can override DNS resolution using:

C:\Windows\System32\drivers\etc\hosts

A typical hosts file contains mostly comments and possibly:

127.0.0.1 localhost
::1 localhost

Unexpected entries mapping common websites to incorrect IP addresses may indicate manual configuration, unwanted software, or malware activity.

Do not delete legitimate corporate or application-specific hosts entries without understanding their purpose.

19. Check Date and Time

Incorrect system time can cause HTTPS websites to fail because TLS certificate validation depends on accurate time.

Check:

Date
Time
Time zone
Windows time synchronization

You can inspect Windows time status with:

w32tm /query /status

If the clock is significantly incorrect, correct the time synchronization problem before investigating browser certificates.

20. Temporarily Test Security Software

Antivirus and endpoint security products may include features such as:

Web Protection
HTTPS Scanning
SSL Inspection
Network Protection
Web Filtering
Firewall
Intrusion Prevention

A corrupted security module or incorrect rule can block browsing while Ping remains successful.

If organizational policy permits, temporarily disable only the relevant web/network protection component for a controlled test.

If Internet access immediately returns, update, repair, reconfigure, or reinstall the security product as appropriate.

Do not leave security protection disabled as the permanent solution.

21. Check Windows Defender Firewall

Open:

Windows Defender Firewall with Advanced Security

Review outbound rules for:

Chrome
Edge
Firefox
System services
Port 80
Port 443

For diagnosis, administrators can compare the system against standard firewall policies or test within an approved maintenance window.

Avoid permanently disabling Windows Firewall merely to make the Internet work.

22. Check VPN Software

VPN clients install virtual network adapters and modify routing.

Disconnect the VPN and test again.

Then run:

route print

Look for unusual default routes or persistent routes.

Also inspect:

ipconfig /all

Old VPN software may leave behind:

Virtual adapters
DNS settings
Routes
Proxy configuration
Network filters

If the issue started after installing or uninstalling a VPN, its network filter driver deserves particular attention.

23. Test Another Browser

If Chrome does not work, try Edge or Firefox.

Interpret the results carefully.

Only one browser fails

Likely causes include:

Browser extension
Browser proxy configuration
Secure DNS configuration
Corrupted browser profile
Browser policy
Browser cache/configuration

Every browser fails

Investigate system-wide components:

DNS
Proxy
Firewall
TLS
Winsock
TCP/IP
Antivirus
VPN
Router/network

This simple comparison can save considerable troubleshooting time.

24. Check Secure DNS / DNS over HTTPS

Modern browsers can use DNS over HTTPS (DoH).

This means the browser's DNS behavior may differ from standard Windows DNS resolution.

If:

nslookup google.com

works but the browser behaves abnormally, temporarily review the browser's Secure DNS settings.

A misconfigured secure DNS provider, filtering service, enterprise browser policy, or network restriction can create unusual symptoms.

25. Disable and Re-enable the Network Adapter

A simple adapter restart can clear temporary problems.

Open:

Control Panel
→ Network and Internet
→ Network Connections

Right-click the active Ethernet or Wi-Fi adapter:

Disable

Wait several seconds and select:

Enable

Then test the connection again.

26. Restart the Router or Modem

If several devices are experiencing the same problem, the issue is less likely to be limited to one Windows computer.

Restart the relevant network equipment during an appropriate maintenance window:

Router
Modem/ONT where applicable
Firewall
Access point if relevant

In a business network, avoid rebooting managed network equipment without authorization because it can disconnect all users, VPNs, servers, VoIP phones, and remote sessions.

27. Check Whether Other Devices Have Internet

This is one of the quickest diagnostic steps.

Only one computer affected

Focus on:

Windows
Network adapter
DNS
Proxy
Browser
Antivirus
Firewall
VPN
Malware

Every device affected

Focus on:

Router
Firewall
DNS forwarder
ISP
WAN
Modem/ONT
Gateway
Network-wide filtering

This separates an endpoint problem from an infrastructure problem.

28. Check for an APIPA Address

Run:

ipconfig

If the IPv4 address begins with:

169.254.x.x

Windows may have assigned an Automatic Private IP Address because it could not obtain a valid address from DHCP.

Investigate:

DHCP server
Router
Ethernet cable
Wi-Fi association
VLAN
Switch port
Network adapter

A 169.254.x.x address is normally not appropriate for ordinary Internet access through a typical office/home router.

29. Check for Duplicate IP Addresses

A duplicate IP can produce intermittent or confusing network symptoms.

If static IP addresses are used, confirm that no other device is using the same address.

Useful commands include:

arp -a

and:

ipconfig /all

In managed networks, inspect DHCP leases, ARP tables, switch data, and IP address management records.

30. Check MTU Problems

An MTU or fragmentation problem can create a particularly confusing situation:

Ping works
Small packets work
Some websites work
HTTPS sessions stall
Downloads fail
VPN traffic behaves incorrectly

You can perform diagnostic Ping tests using the Don't Fragment flag:

ping 8.8.8.8 -f -l 1472

If fragmentation is required, test smaller packet sizes.

For example:

ping 8.8.8.8 -f -l 1400

MTU problems are particularly relevant to:

PPPoE
VPNs
Tunnels
Certain WAN configurations
Misconfigured routers

Do not randomly change MTU values without identifying the actual path requirement.

31. IPv6 Can Also Affect Browsing

Modern Windows environments normally support both IPv4 and IPv6.

A broken IPv6 configuration can occasionally cause delayed or failed connections while IPv4 tests appear normal.

Check:

ipconfig /all

and:

ping -4 google.com

Then:

ping -6 google.com

Comparing IPv4 and IPv6 behavior can help identify a protocol-specific issue.

Do not permanently disable IPv6 as a routine troubleshooting step unless there is a specific compatibility requirement or confirmed fault.

32. Use PowerShell for Better Connectivity Testing

PowerShell can provide more useful information than Ping alone.

For example:

Test-NetConnection google.com -Port 443

You can inspect:

ComputerName
RemoteAddress
RemotePort
InterfaceAlias
SourceAddress
TcpTestSucceeded

This tells you whether the actual TCP service required for HTTPS can be reached.

For many "Ping works but Internet doesn't" cases, this test is significantly more useful than repeatedly running Ping.

33. Check DNS Client Service

Open:

services.msc

Check relevant Windows networking services.

In particular, Windows DNS functionality depends on appropriate networking services being available.

Avoid randomly disabling or changing service startup types while troubleshooting. Compare them against normal Windows configuration or organizational policy.

34. Browser Opens Some Websites but Not Others

If only certain websites fail, investigate:

DNS filtering
Firewall filtering
Content filtering
TLS inspection
Website outage
Browser extension
ISP routing
IPv6
MTU
Certificate problems
Geographic/network restrictions

Try:

nslookup affectedwebsite.com

Then:

Test-NetConnection affectedwebsite.com -Port 443

This separates DNS resolution from HTTPS connectivity.

35. Recommended Diagnostic Sequence

Instead of immediately resetting everything, use a logical sequence.

Step 1 – Check IP configuration

ipconfig /all

Step 2 – Test local gateway

ping <gateway-IP>

Step 3 – Test public IP

ping 8.8.8.8

Step 4 – Test DNS

nslookup google.com

Step 5 – Compare hostname Ping

ping google.com

Step 6 – Test HTTPS

Test-NetConnection google.com -Port 443

Step 7 – Check proxy

netsh winhttp show proxy

Step 8 – Check browser, VPN, antivirus and firewall

Step 9 – Repair DNS/Winsock/TCP-IP if required

ipconfig /flushdns
netsh winsock reset
netsh int ip reset

Step 10 – Restart and retest

This approach identifies the failing network layer instead of applying random fixes.

36. Quick Diagnostic Table

Test	Result	Likely Area
Gateway Ping fails	Failure	LAN, Wi-Fi, VLAN, adapter, gateway
Gateway works, 8.8.8.8 fails	Failure	Router, WAN, routing, ISP
8.8.8.8 works, domain lookup fails	Failure	DNS
DNS works, TCP 443 fails	Failure	Firewall, filtering, routing, VPN
TCP 443 works, browser fails	Failure	Browser, proxy, TLS, security software
One browser fails	Failure	Browser-specific configuration
All computers fail	Failure	Router, DNS, firewall, ISP
Only one PC fails	Failure	Windows/network configuration
Small traffic works, large connections stall	Intermittent	MTU/fragmentation
Internet fails after VPN installation	Failure	VPN route/filter/DNS

37. Important Difference: ICMP vs TCP vs DNS

Understanding this distinction explains the entire problem.

Ping

Primarily tests:

ICMP

DNS

Translates:

google.com → IP address

Usually using DNS services such as UDP/TCP 53, although modern encrypted DNS mechanisms can differ.

HTTP

Normally uses:

TCP 80

HTTPS

Normally uses:

TCP 443 + TLS

Therefore, a computer can successfully exchange ICMP traffic while DNS or HTTPS is failing.

That is why:

"Ping is working" should never be interpreted as "the entire Internet connection is working."

38. Example Troubleshooting Case

Suppose a Windows 11 computer shows:

ping 8.8.8.8

Result:

Reply from 8.8.8.8

But:

nslookup google.com

Result:

DNS request timed out

This tells us:

PC → Gateway → Internet IP connectivity = Working
DNS name resolution = Failing

The technician should therefore investigate DNS before resetting browsers or reinstalling network drivers.

Now consider another case:

ping google.com

works, but:

Test-NetConnection google.com -Port 443

shows:

TcpTestSucceeded : False

DNS is resolving successfully, but HTTPS connectivity is failing.

The technician should shift attention toward firewall, VPN, routing, security software, or upstream filtering.

39. What Not to Do

Avoid immediately:

Formatting Windows
Reinstalling Windows
Resetting the router to factory defaults
Disabling antivirus permanently
Disabling Windows Firewall permanently
Deleting random registry entries
Removing network services
Changing many settings simultaneously

Changing several components at once makes it difficult to identify the actual cause and can create additional problems.

Diagnose first, then apply the smallest appropriate repair.

40. Advanced Technician Command Set

The following commands provide a useful starting toolkit:

ipconfig /all
ipconfig /flushdns
ipconfig /release
ipconfig /renew
ping 8.8.8.8
ping google.com
nslookup google.com
tracert 8.8.8.8
arp -a
route print
netsh winhttp show proxy
netsh winsock show catalog

For repair:

netsh winsock reset
netsh int ip reset

PowerShell:

Get-NetAdapter
Get-NetIPConfiguration
Get-DnsClientServerAddress
Test-NetConnection google.com -Port 443

These commands can usually determine whether the failure is associated with the adapter, IP configuration, gateway, DNS, route, proxy, or TCP connectivity.

41. Troubleshooting Decision Tree

A practical decision tree is:

Is the network adapter connected?
        |
       Yes
        |
Does the PC have a valid IP/gateway?
        |
       Yes
        |
Can it reach the gateway?
        |
       Yes
        |
Can it reach a public IP?
        |
       Yes
        |
Can DNS resolve a domain?
       / \
     No   Yes
     |     |
   Fix    Test TCP 443
   DNS      |
           / \
         No   Yes
         |     |
      Check   Check browser,
      firewall, proxy, TLS,
      VPN,     security software
      routing

This methodology is far more effective than assuming that every "no Internet" problem has the same cause.

42. Frequently Asked Questions (FAQ)

Q1. Why does Ping work when the Internet does not?

Because Ping primarily uses ICMP, while web browsing requires DNS, TCP, TLS, and normally port 443. One protocol can work while another fails.

Q2. What does it mean if I can Ping 8.8.8.8 but cannot Ping google.com?

It usually indicates a DNS resolution problem. Your computer can reach an Internet IP address but cannot translate the hostname into an IP address.

Q3. Which command should I use to test DNS?

Use:

nslookup google.com

You can also test a specific DNS resolver:

nslookup google.com 8.8.8.8

Q4. How do I clear the DNS cache?

Open Command Prompt as Administrator and run:

ipconfig /flushdns

Q5. Which DNS servers can I use for testing?

Common public resolvers include:

Google:
8.8.8.8
8.8.4.4

Cloudflare:
1.1.1.1
1.0.0.1

Use them according to your organization's privacy, security, and network policies.

Q6. What if Ping to google.com works but Chrome does not?

DNS and basic IP connectivity are probably working. Check TCP port 443, browser settings, proxy, VPN, firewall, TLS, antivirus, and browser extensions.

Q7. How do I test HTTPS connectivity?

Run PowerShell:

Test-NetConnection google.com -Port 443

Look for:

TcpTestSucceeded : True

Q8. Can antivirus cause Ping to work but websites to fail?

Yes. Web filtering, HTTPS inspection, firewall, or network protection modules can interfere with browser traffic while allowing ICMP Ping.

Q9. Can a VPN cause this issue?

Yes. VPN software can modify DNS, routing, proxy settings, virtual adapters, and network filter drivers.

Q10. Can malware cause this problem?

Yes. Malware and unwanted applications can modify proxy settings, DNS servers, firewall rules, browser settings, certificates, and the hosts file.

Q11. Should I reset Winsock?

It can be useful when application networking is corrupted:

netsh winsock reset

Restart Windows afterward.

Q12. How do I reset TCP/IP?

Run as Administrator:

netsh int ip reset

Then restart Windows.

Q13. Does successful Ping prove my ISP is working correctly?

No. It proves only that the tested ICMP communication succeeded. DNS, HTTPS, routing to other destinations, and other Internet services may still have problems.

Q14. Why do some websites work while others do not?

Possible causes include DNS filtering, IPv6 problems, MTU issues, firewall rules, content filtering, TLS inspection, routing problems, or a problem with the destination website itself.

Q15. Why does Internet work on my phone but not my computer?

If both devices use the same network and only the computer fails, investigate the computer's DNS, proxy, firewall, VPN, browser, adapter, driver, and Windows network stack.

Q16. Why does every computer on the network have the same problem?

That suggests an infrastructure-level issue such as the router, firewall, DNS service, WAN connection, modem/ONT, or ISP.

Q17. Should I disable IPv6?

Not as a standard fix. Test IPv4 and IPv6 separately first. Permanently disabling IPv6 without identifying the underlying issue can create other compatibility problems.

Q18. Can an incorrect date and time stop Internet browsing?

Yes. Incorrect system time can cause TLS certificate validation failures and prevent HTTPS websites from loading properly.

Q19. Can an MTU problem cause Ping to work but websites to fail?

Yes. Small packets may work while larger packets or encrypted connections stall because of MTU or fragmentation problems.

Q20. Should I reinstall Windows if Ping works but browsing does not?

Normally, no. Most cases can be diagnosed and repaired by identifying the affected layer—DNS, proxy, TCP/IP, firewall, VPN, browser, security software, or network infrastructure.

Conclusion

When Ping works but the Internet does not, do not assume the network is fully operational merely because ping 8.8.8.8 returns replies.

Instead, test each networking layer systematically:

Network Adapter
      ↓
IP Address
      ↓
Default Gateway
      ↓
Internet IP Connectivity
      ↓
DNS Resolution
      ↓
TCP Connectivity
      ↓
HTTPS / TLS
      ↓
Proxy / Firewall / VPN
      ↓
Browser / Application

The most useful initial commands are:

ipconfig /all
ping 8.8.8.8
ping google.com
nslookup google.com
tracert 8.8.8.8
netsh winhttp show proxy

and:

Test-NetConnection google.com -Port 443

By comparing these results, an administrator can usually determine whether the problem is related to DNS, routing, TCP/HTTPS, proxy settings, firewall rules, VPN software, security software, Windows networking, or the upstream Internet connection.

The key principle is simple:

Ping tests reachability; it does not test the complete Internet experience.

Technical Disclaimer

The commands and procedures in this article are intended for educational and troubleshooting purposes. Network configurations vary between home, business, server, VPN, cloud, and enterprise environments. Before resetting TCP/IP, changing DNS servers, modifying proxy settings, disabling security controls, or altering firewall configuration, document the existing settings and verify organizational requirements. On remotely managed computers or servers, network changes may terminate the remote session and prevent reconnection.