Member Avatar for blackbelt27

***RUNNING:windows xp sp 2
ok i ridded a computer of 1021 infected files 23 viruses and 3 droppers. after disinfection internet axcess was damaged , so i re-installed the TCP/IP to the LAN connection and deleted the WinSock and WinSock2 entries and rebooted, (automatically rewriting the entries correctly) and bam i had internet connection, BUT when i try to go to the gmail sign-in page i get an ssl connection error (google chrome)

Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.

it seems like its missing a driver or something because it ONLY happens on the gmail login page (which is https) PHP works perfect, but https i get the said error, on all other browsers i get "page cannot be found"

so it appears if a driver or something is missing, can anyone direct me? specifically on how to re install and check ALL components essential to ssl within windows xp

  • 4 Contributors
  • 5 Replies
  • 222 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by blackbelt27

Dani AI

Generated

Brief summary and diagnosis tied to the thread: described a Windows XP SP2 machine that regained HTTP access after a Winsock/TCP reset but failed on the Gmail HTTPS sign‑in (Chrome Error 107). In this situation the usual suspects are (a) antivirus / web‑shield HTTPS interception, (b) leftover/broken Winsock/LSP hooks after an infection, (c) an invalid system clock or damaged root CA store, or (d) plain OS/browser TLS incompatibility on legacy XP builds. Replies from and rightly flagged firewall/AV as likely; the Avast Web Guard HTTPS scan is specifically able to intercept and break TLS handshakes, so disabling it is the first quick test. (support.avast.com)

Practical immediate checks (do these before re‑installing anything):

  • Temporarily disable Avast Web Guard HTTPS/SSL scanning (Menu → Settings → Protection → Core Shields → Web Guard → untick Enable HTTPS scanning) and retest the Gmail login. If that fixes it, re-enable and examine Avast’s HTTPS certificate used for interception. (support.avast.com)
  • Verify system date/time and timezone (bad clocks cause certificate errors).
  • Inspect the Windows trusted root store with certmgr.msc or Internet Options → Content → Certificates to ensure root CAs weren’t removed or replaced during cleanup. Restoring missing roots (or syncing with Windows Update) often fixes validation failures. (learn.microsoft.com)
  • If changes were made earlier, run netsh winsock reset, netsh int ip reset and sfc /scannow, then reboot to ensure Winsock and core files are intact.

Longer-term context and recommendation: Windows XP is out of support (security updates ended in April 2014) and modern sites and browsers have moved to TLS 1.2+ and stronger ciphers that XP/IE8 can’t negotiate reliably. Chrome also stopped receiving updates on XP in 2016, and major browser vendors phased out older TLS versions—so even a “fixed” XP may fail HTTPS to Gmail and other sites. The realistic, secure solution is to migrate the machine to a supported OS or isolate XP from sensitive accounts. (learn.microsoft.com)

Short checklist to attach to the thread for future readers: 1) Disable HTTPS scanning in AV and retest; 2) check clock and root CAs (certmgr.msc); 3) reset Winsock/IP and run sfc /scannow; 4) test from another device to rule out server-side blocks; 5) plan OS/browser upgrade if the problem recurs. Tying back: the forum replies (including ’s pointer and the AV suggestions from /) were on the right track — AV interception is the single most common cause in cases that look like a working HTTP but broken HTTPS connection. (support.avast.com)

Recommended Answers

All 5 Replies

Member Avatar for caperjack

***RUNNING:windows xp sp 2
ok i ridded a computer of 1021 infected files 23 viruses and 3 droppers. after disinfection internet axcess was damaged , so i re-installed the TCP/IP to the LAN connection and deleted the WinSock and WinSock2 entries and rebooted, (automatically rewriting the entries correctly) and bam i had internet connection, BUT when i try to go to the gmail sign-in page i get an ssl connection error (google chrome)

Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.

it seems like its missing a driver or something because it ONLY happens on the gmail login page (which is https) PHP works perfect, but https i get the said error, on all other browsers i get "page cannot be found"

so it appears if a driver or something is missing, can anyone direct me? specifically on how to re install and check ALL components essential to ssl within windows xp

Hi, perhaps this will help ,I don't use chrome myself but found this info with a google search .
http://roezer.com/LostBlog/error-neterr_ssl_protocol_error/

Member Avatar for RenoM88

This problem might be caused if you have firewall program installed, firewall bloked ssl conection.

Member Avatar for blackbelt27

ahh i never thought about firewall, im using the latest avast

Member Avatar for anhbloginc

The avast might block the ssl

Member Avatar for blackbelt27

yeah it was avast, i had already checked to make sure the ssl was enabled

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.