Member Avatar for Daniel_26

Ok I just recently changed isp this afternoon. I show full connectivity, I'm sending and receiving data, I can ping websites and have no loss in packets. But all browsers I use can do nothing (IE, Chrome, Firefox). I've tried many things; dns flush, system restore, clearing prior settings, disabling Norton and Windows defender, the
netsh int ip reset resetlog.txt cmd. I can't even remember everything I've tried. I'm connected wirelessly, using Windows 7 on a hp pavilion elite hope. My new isp is xfinity(comcast). The best results I've seen is with the system restore, I got 2-4min of browsing. I had my laptop right next to pc and it works fine. Also everything in the house connected wirelessly works fine. I'm at a loss and have no clue what to do.

  • 2 Contributors
  • 4 Replies
  • 202 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by Daniel_26

Dani AI

Generated

Quick diagnostic checklist for the “connected but browsers won’t load” symptom (based on ’s report that the PC showed full connectivity and could ping sites while other devices worked, and ’s router question).

  • Narrow first: verify the problem follows the PC or the network. Try the PC on a different network (phone hotspot) and try another device on the same Wi‑Fi. If the PC works elsewhere, the router or its settings are suspect.
  • Simple, high‑value checks (in order): confirm there’s no proxy set in the browser/Windows LAN settings; open a browser and paste the IP you get from a ping (use the IP returned by ping example.com) to bypass DNS; check the browser console for specific errors (timeout, connection reset, SSL).
  • TCP vs ICMP: ICMP (ping) can succeed while TCP (HTTP/HTTPS) fails. An easy MTU/fragmentation test on Windows is:
    ping -f -l 1472 8.8.8.8

    If that fragments, lower the payload until it succeeds and then set a matching MTU on the adapter/router. Also test port reachability with telnet <ip> 80 or PowerShell Test-NetConnection -ComputerName <host> -Port 80 (if available).

If those point to the router: factory‑reset it (backup any config first), check firmware, and inspect firewall/parental‑control/QoS rules or device blacklists. For intermittent or hard‑to‑explain failures, capture a short packet trace (Wireshark) and look for TCP RSTs, repeated retransmits, or ICMP unreachable messages — these tell whether the host, router, or ISP is dropping/altering traffic.

If unsure, gather: router logs, a browser network error message, and a small packet capture — then contact the ISP or router vendor. Replacing a failing router is a common, quick fix, but these steps will help prove it and preserve useful evidence.

Member Avatar for Stavros_1

Did you change the ISP but kept the old router?

Member Avatar for Daniel_26

New router

Member Avatar for Stavros_1

Now in case you still haven't fixed it, it would be easier to call tech support
- just sayin

Member Avatar for Daniel_26

It was a bad router... easy fix

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.