Jump to content

itman

Most Valued Members
  • Content Count

    8,280
  • Joined

  • Last visited

  • Days Won

    201

Everything posted by itman

  1. Also, are you using some type of browser add-on/extension to access Gmail in the browsers? If so, access Gmail sign-on site directly via the browser search bar; e.g. https://accounts.google.com/signin/v2/identifier?continue=https%3A%2F%2Fmail.google.com%2Fmail%2F&service=mail&sacu=1&rip=1&flowName=GlifWebSignIn&flowEntry=ServiceLogin. If this is successful, the problem lies with the add-on/extension you are using to access Gmail.
  2. I really don't know what the problem is on your end. Given the widespread use of Gmail if this issue was widespread among Eset users, the forum would be bombarded with like postings. Do as @Marcos instructed as to gathering and submitting Eset logs as he requested.
  3. One other thing. Are you actually receiving Eset phishing alerts when you try to access Gmail from the browser:
  4. The IP address shown, 142.250.200.133, is associated with Google. However, this IP address is not associated with mail.google.com domain. Are you accessing gmail via a browser or an e-mail client?
  5. This also would be indicative that Eset is not the source of these connect.com.fj connection resets in Thunderbird. If Eset were the source, it would manifest with this new e-mail account. FYI - I did a test for connect.com.fj using QUALS SSL Server web site. What was shown is this domain downloads an additional chain certificate. This activity is problematic to Eset SSL/TLS protocol scanning. Although a POP3 connection is being used for e-mail delivery, I believe initial HTTPS connections are being established with the domain to initiate the e-mail transfer. It is also possible tha
  6. Also, add IP address, 202.137.178.55, to Eset Protocol Filtering's Excluded IP addresses and retest using Thunderbird.
  7. The only English documentation I could find on "Clash For Windows" is here: https://docs.wannaflix.net/windows/v2ray-shadowsocks/clash-for-windows-new . Everything on Github where the software is hosted is written in Chinese. According to the link I posted, Clash For Windows uses an in program mode: To initiate an Internet connection: Appears to me one must be in "Proxy" mode when activating Eset If the Eset Chinese web site is in-country based. Otherwise, "Global" mode must be used.
  8. Just how do you do that? I use Extello LANSocket adapters and they are constantly on. They don't even have a power switch.
  9. Here's something else to try. As a test, add this IP address, 119.235.102.67 , which is the IP address for connect.com.fj to Eset Protocol Filtering's Excluded IP addresses per below screen shot. After adding and saving, verify the IP address was added. Now attempt to access your e-mail via Thunderbird.
  10. Not according to what @shocked posted here: https://forum.eset.com/topic/28300-repair-installation-option-isnt-available-when-starting-the-downloaded-installer-again/?do=findComment&comment=133234
  11. Based on what has been posted in this thread including @Marcos statement that Eset's uninstaller is not being properly upgraded as far as Win installer info. goes, I would never perform an Eset repair via Win Programs uninstall option. I know I will never attempt one again. Also Eset needs to fix this issue in regards to Eset in-product upgrades, or remove the Repair option from the uninstaller entirely.
  12. This is a bit hillarious. Eset has a long KB article on how to repair your installation here: https://support.eset.com/en/kb5844-repair-an-existing-eset-installation-using-the-setup-wizard . The jest of the article is you have to uninstall and reinstall.
  13. I couldn't make out what you were trying to do from the video you posted. The only way I knew of running an Eset repair installation was via Control -> Programs as shown in the below screen shot. And you appear to be correct in that it appears that option no longer exists; at least in ver. 14.x. I believe it may have existed in ver 13.x, but not sure since it has been a while since I ran a repair install. -EDIT- Just noticed the Eset uninstaller created a log file. The interesting part is: So it appears the last Eset ver. to support the repair option was 13.1.16.
  14. What is the context of this inquiry? If Eset is installed properly, none of the Microsoft Defender associated services are started.
  15. Did you uninstall Eset, then re-install Eset after deleting the C:\ProgramData\ESET\ESET Security folder you created? The Eset installer will create this folder and populate it with data.
  16. The only other "culprit" I can think of would be the Network protection module. Mine on regular release update channel is ver. 1688.4 dated 3/31/2021. BTW - do you have the B&PP secure all supported browsers setting enabled? That also is a possible "culprit."
  17. I and others have asked this previously to no avail.
  18. Technically speaking, "SMART" mode employs more restrictive rules than "Automatic" mode. The demonstrated fact is it would be a rare occurrence that one would see a HIPS detection in "SMART" mode that would not have triggered in "Automatic" mode. In reality, the HIPS default rules are conditioned by other Eset protection settings such as ransomware protection.
  19. I assume "steamed updates" means Pico updates? Since Pico updating is the primary method of updating Eset versus module updates, it is definitely something that should not be disabled.
  20. As a test, create a HIPS rule; you can delete it afterwards. Is the rule created and saved w/o issue?
  21. How did you block module updates? As far as I am aware of, that option does not exist in the Eset GUI.
  22. Are you logged on to Windows under a standard user account?
  23. This is weird. I upgraded to ver. 14.1.19 yesterday and my firewall module ver. is 1418 dating to 11/2/2020. The problem might be you're using pre-release updating and a later dated firewall module is the issue. Set Eset back to regular update channel and this will hopefully solve your issue.
  24. Force the Eset upgrade via use of Eset GUI Update option. I had no issues upgrading to ver. 14.1.19 this way.
  25. Appears that's the case: ekrn.exe 1552 TCP xxxxx.xxxxx.net 49706 38-90-226-65.ptr.eset.com 8883 ESTABLISHED 13 428 12 372 I don't have any issues with this, but some might that expect ekrn.exe to be using ports 80/443.
×
×
  • Create New...