Jump to content

itman

Most Valued Members
  • Content Count

    7,568
  • Joined

  • Last visited

  • Days Won

    190

Everything posted by itman

  1. Now this article: https://kb.eventtracker.com/evtpass/evtPages/EventId_36871_Schannel_45297.asp is fairly specific in stating it is SSL SMTP; i.e. e-mail, related. SMTP is used by most e-mail providers to receive e-mail.
  2. This gist of this error is a mismatch of cypher suites being deployed: This posting relates to SSL issues but that same can happen in TLS: https://teridon73.blogspot.com/2018/08/windows-schannel-error-event-id-36871.html Tracking down the source in your case will take some effort.
  3. Actually, Win 8.1/10 fast startup feature only applies when the PC was previously shutdown. When a Win 8.1/10 restart is performed via Start menu option or via program directive as done after select Win Updates, Eset product upgrade processing, etc., Win normal startup processing is performed. The fast startup feature is bypassed in this instance.
  4. I just noticed something interesting in regards to Eset's root certificate stored in both FireFox and Thunderbird. It is only authorized for code signing purposes. Why that is I am clueless since it has full authorization privileges assigned in its Win root CA store certificate. This issue wouldn't cause problems with FireFox since the Eset cert. stored there can identify web sites. What I am wondering is if enabling the "identify e-mail providers" setting on the Eset cert. stored in Thunderbird will fix this Thunderbird SSL connection issue?
  5. Based on what I see here: https://emailconfiguration.com/orange-fr , Orange e-mail is using SSL. I am interpreting this literally to mean it is not using TLS. As noted above, others are also having the same issue when trying to receive SSL communication from their e-mail providers servers. As such, it really appears Eset e-mail is no longer working for SSL e-mail other than by creating a certificate exclusion in Eset SSL/TLS protocol scanning as posted previously. Open an Eset tech support request with your in-country Eset provider so this issue is properly tracked. I also advise any
  6. Refer to my prior posted Advanced setup screen shot. Do you have "Exclude communication with trusted domains" enabled?
  7. I was on ver. 68.12.1 and had no issues w/Eset IMAPS and POPS scanning enabled. Just upgraded to 78.4.0 and still no issues. Are you using an internal IMAPs server? Both my IMAPS and POPS connections are to third party e-mail providers; AOL and Yahoo.
  8. Note that you posted into an existing forum thread. The OP of this thread was having an issue with Thunderbird. This is why the forum rules are not to cross-post into an existing thread. It only causes more confusion and often results in the OP's issue being obscured and not being resolved.
  9. In regards to this Thunderbird e-mail account, is it indeed an IMAP account and not IMAPS? What is the connection security for this account in Thunderbird? The options are None, STARTTLS, or SSL/TLS.
  10. This really doesn't make a lot of sense in regards to client received e-mail. The feature is primarily designed via web site certificate identification to modify Eset's default SSL/TLS protocol scanning behavior for a given web site. It can also be used to override Eset default Access and Scan settings for a given web site. What may be "busted" in ver. 14 in regards to e-mail is this setting which is enabled by default: https://help.eset.com/eis/14/en-US/idh_config_epfw_ssl_known.html?idh_config_epfw_ssl.html I will also add I use Thunderbird as my e-mail client with two
  11. At least we're getting somewhere now. Eset has a setting for SSL/TLS protocol scanning accessible via Advanced Setup that blocks SSL v2 traffic. I suspect this setting; possibly by mistake in ver. 14, is now blocking all SSL traffic. Disable this setting and see if e-mail connectivity to its server is resolved.
  12. This is true if the license was purchase directly from Eset. As far as boxed versions go, every one I have ever purchased always contained a license key.
  13. I also reviewed a number of posting on the motherboard forums such a Gigabyte's forum. It appears a common occurrence is to have a firmware update bork mouse use in the BIOS/UEFI GUI. As such, that is where I would start researching as to you your erratic mouse behavior.
  14. Ref.: https://help.eset.com/license_manager/en-US/elm_add_license.html Per the above linked reference, the following is unclear. When an inactivated Eset license is added to Eset License Manager, is the license key verified as legit?
  15. I would say this is a fake popup message; probably malware related, attempting to spoof you into elevating process privileges. Why do I believe this is a spoofed alert? For starters, Eset Smart Security Premium does not run on Vista. Do you perhaps have the old version of Smart Security? The last issued version for that was 10.1.245. It is end-of-life and no longer supported. Note that if you are using a cracked version of Eset, anything is possible.
  16. Post a few web site URLs where you have problems in FireFox w/Eset SSL/TLS protocol scanning enabled.
  17. I have no problem connecting to AOL e-mail using IMAPS. Is the problem with a local IMAPS server?
  18. 👍 Note that once Windows is loaded, it is using it's mouse driver, USB controller, etc.. When accessing the BIOS directly, the BIOS is using the mouse via direct hardware access to it.
  19. For somewhat obvious reasons, Eset is not going to publicly state what the security reasons are so the can be exploited.
  20. Since both Thunderbird and FireFox are having SSL/TLS protocol scanning issues, the only thing I can think of is you somehow you have a bad Eset certificate installed. Eset product update will update the existing Eset root certificate in both Thunderbird and FireFox. How this could have happened I have no clue. Verify Eset certificate shows "OK" per the below screenshot:
  21. I am assuming that you have not purchased an ESU for the 2008R2 server? This is why it has not been patched? Personally, I wouldn't rely 100% on Eset IDS protection for this vulnerability. You might want to check this out: https://blog.0patch.com/2020/09/micropatch-for-zerologon-perfect.html
  22. https://support.eset.com/en/kb7674-what-s-new-in-eset-version-14-home-products?ref=esf#Password
  23. I assume what you mean here is your pinging activity from the source client device was blocked to all servers other than the 2008 R2 one? Did you try to connect to the 2008 R2 server other than using ping?
  24. About CVE-2020-1472: https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-1472 My best guess is Eset IDS is not currently capable of blocking the attacker IP address for this type of attack. Appears most of those are set up for SMB related vulnerabilities. So it instead blocked access to the targeted IP address.
×
×
  • Create New...