I’ve been scratching my head over a weird problem that I just can’t seem to solve. In Microsoft Edge (or any Chromium-based browser), I cannot connect to Norton’s website (https://www.norton.com). I get a 500 Server Error: “Could not connect to the server.”
What I’ve Checked So Far
- Trusted/Restricted Sites: All clear, no blocks.
- HOSTS File: Nothing unusual, no entries that would affect Norton.
- Ping & Traceroute: Both succeed, so the network path is fine.
- Other Browsers: Firefox and Chrome work perfectly — no issues loading the site.
This is bizarre because it’s only happening in Edge. I’ve tried clearing cache, disabling extensions, and even resetting Edge settings — still no luck. Any ideas?
Possible Causes I’m Considering
- DNS Caching: Edge might have its own DNS cache or be using a different resolver.
- IPv6 vs IPv4: Maybe Edge is preferring IPv6 and the site’s IPv6 is misconfigured.
- Security Software: Could be a conflict with Windows Defender or third-party AV that only affects Edge.
- Corrupted Profile: Edge profile might be damaged.
Has anyone else encountered a similar issue with a specific site only on one browser? What did you do to fix it?
What I’ve Tried Without Success
- Flushed DNS via command prompt (
ipconfig /flushdns)
- Cleared browser history and cookies
- Disabled all extensions
- Checked proxy settings (they’re off)
- Ran Edge in InPrivate mode — same error
- Used the built-in Network Reset in Windows
I’m leaning toward a corrupted profile or a rogue Edge flag. Before I nuke my profile, any suggestions?
I’ve been following this thread and have some additional insights that might help. The issue you’re facing is a classic example of how browser-specific behavior can expose subtle network or configuration differences. Modern browsers like Edge (Chromium-based) and Chrome share the same core engine, but they still have distinct profiles, flags, and default settings that can cause divergence.
Browser-Specific Network Stack Differences
One major factor is how Edge handles DNS over HTTPS (DoH) and IPv6 preference. Edge might be configured to use a different DNS resolver or have DoH enabled, while Chrome uses the system default. If Norton’s CDN has issues with that specific resolver, it could cause a 500 error. You can check this by navigating to edge://net-internals/#dns and comparing with Chrome’s chrome://net-internals/#dns. Also, Edge has a flag for “Use DNS over HTTPS” that might be set differently.
Another area is connection coalescing and HTTP/3 (QUIC). Edge and Chrome both support QUIC, but they may negotiate different protocols. If Norton’s server misbehaves with QUIC (e.g., broken connectivity via UDP), Edge might fall back to HTTP/2 or HTTP/1.1. You can test by disabling QUIC in Edge flags (edge://flags/#enable-quic) and see if the site loads.
Modern Implications: The Rise of Browser-Isolated Environments
Today, browsers are more than just HTML renderers—they are sandboxed environments with their own caches, certificate stores, and even network stacks. Microsoft Edge integrates tightly with Windows Network Service Accounts and Windows Defender Application Guard, which can block certain sites. If Norton’s site triggers a SmartScreen false positive or a malware signature, Edge might block it silently. Check Windows Security > App & browser control > Reputation-based protection settings.
Another modern trend is containerized browsing (e.g., Edge’s Application Guard) where each browser instance runs in a separate container with its own network namespace. This can cause DNS resolution failures if the container’s network is misconfigured. You can verify by launching Edge without Application Guard: start msedge --no-sandbox.
Step-by-Step Diagnostic Flow
I recommend creating a systematic diagnostic map to isolate the culprit. Below is a flowchart that visualizes the decision process based on your observations and possible causes.
What to Try Next
- Reset Edge’s network stack: In
edge://net-internals/#sockets, click “Flush socket pools.”
- Check for Proxy Auto-Config (PAC): Edge might be using a different PAC file than Chrome. Go to Settings > System > Open your computer’s proxy settings and verify.
- Create a fresh Edge profile: No need to nuke the whole profile. Create a new user profile in Edge and test from there. If it works, migrate your bookmarks gradually.
- Examine Edge’s Secure DNS settings:
edge://settings/privacy — toggle “Use secure DNS” off and on to see if it changes behavior.
Hopefully one of these steps resolves the mystery. It’s fascinating how a single site can be blocked by one browser while working perfectly on another. The root cause is often a combination of small settings that snowball into a connectivity failure. Keep us posted on what works.
