Member Avatar for Imagikafan

Hello :D ,

Specifics:
Netgear WGR614 v4
Windows XP Home Edition
AOL 9.0 Optimized SE
Internet Explorer 6.0
Broadband Blaster


Everything works fine except when I try to access SSL sites. For example, I'll go to the MBNA America site to check on my credit card account. The home page will come up fine, but when I click on the link to the log in screen I get the infamous "The page cannot be displayed" screen.

I've talked to both the Netgear and AOL support staff and they both seemed baffled by this problem.


Any suggestions? :mrgreen:


Mark

  • 2 Contributors
  • 2 Replies
  • 98 Views
  • 17 Hours Discussion Span
  • Latest Post Latest Post by Imagikafan

Dani AI

Generated

This thread is a good example of SSL failures coming from the client side rather than the router. later reported the problem went away after removing a local security product, and ’s note about wireless encryption is useful context — WEP/WiFi settings affect the radio link, not a browser’s TLS handshake. Below are practical checks and safe fixes to use if HTTPS pages load partly (home page) but fail on the secure login page.

Quick diagnostic checklist

  • Confirm scope: try another PC or handheld and another browser. If only one machine fails, it’s local software.
  • Check browser proxy settings (IE: Tools → Internet Options → Connections → LAN Settings) and the hosts file for redirects.
  • Properly disable security software (not just “turn off” in the UI). Some AV/firewall suites keep kernel drivers active. Either stop the product’s services from services.msc or uninstall with the vendor removal tool to test.
  • Test raw TCP reachability: from a command prompt try telnet yourbank.example 443. A successful open means the network path is OK; failure suggests a local firewall/router/ISP block.
  • Boot Safe Mode with Networking or use a Live CD/USB to isolate OS-level interference.
  • If comfortable, capture traffic with Wireshark and look for a TCP RST/ICMP or an absent TLS ClientHello.

Common fixes and cautions

  • If the security suite is the culprit, re-install an updated build or disable only the SSL/HTTPS scanning/web-protection feature rather than leaving the PC unprotected.
  • Check router firmware and any built-in filtering/ALG/SPI settings; a firmware upgrade or temporarily placing the client in the router’s DMZ can help isolate router issues.
  • Do not leave the machine unprotected after testing. If this thread is being read years later, note that Windows XP/IE6 lack modern TLS support — upgrading the OS/browser is strongly recommended.

Recommended Answers

All 2 Replies

Member Avatar for Puckdropper

Are you running any kind of WEP? Perhaps the router is set up to deny access to secure sites without WEP enabled. WiFi is one of the most insecure ways to transmit data, especially if you're running running with any encryption. (I don't check my bank stuff with WiFi...)

Member Avatar for Imagikafan

Thanks for the quick response. As it turned out, my Norton Firewall was the problem (even though I had it disabled). Once I uninstalled it, everything worked fine. :lol:


Mark

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.