Jump to content

joaer

Members
  • Posts

    17
  • Joined

  • Last visited

Posts posted by joaer

  1. For the record, I managed to solve my Thunderbird SSL/TLS problems by keeping protocol filtering enabled, but adding the IP address of the IMAP server (a local address on my home network) to the Excluded IP addresses list, found in Advanced setup > Web and email > Protocol filtering > Excluded IP addresses. Maybe not the correct or best way to solve it, for for now, I'm good.

    I presume my firefox errors were a result of certificate regeneration, which I handled by following the advice above.

    Regards, Joakim

  2. Marco5342: these error messages are similar to the ones I get when protocol filtering is enabled.

    itman, as I mentioned, I have no problem accessing major email providers like gmail and outlook, but the problem is with my local IMAP server. It might be that NOD32 after the update finds the local self-generated certificate problematic, although it is sufficient for my needs. I found a Certificate Validity setting under Web and Email SSL/TLS settings in NOD32, but the only two options, "block" och "ask", did not make much difference either way. To be honest, I believe that certificate validity should be handled by the application, not the antivirus software. Is there any way to disable this check for local domains?

    When it comes to firefox, these errors now seem to have disappeared, for unknown reasons. Great, as long as it stay that way.

  3. Thanks for your reply! The root certificate is fine.

    However, I have done some more checking, and it appears that the firefox problems are intermittent; for now it seems to work even if SSL/TLS protocol filtering is enabled.

    Then I found a setting affecting only protocol filtering for email client, and I can confirm that thunderbird problems are reproducible. Any ideas?

     

  4. Yesterday, I got an automatic update for my ESET NOD32 to version 14.0.21.0 on my Win10 computer. After restart, I was no longer able to access some of my email accounts using thunderbird. My gmail and outlook accounts worked, but my main account, a local IMAP server, hanged with the message "Checking mail server capabilities..." At the same time, my firefox browser started to fail on a number of sites (not all, mind you) with the error "Secure Connection Failed: Peer’s certificate has an invalid signature. Error code: SEC_ERROR_BAD_SIGNATURE, The page you are trying to view cannot be shown because the authenticity of the received data could not be verified."

    All of this worked perfectly before I updated NOD32 so I started to investigate the AV settings, and soon discovered that if I disabled SSL/TLS protocol filtering, all worked perfectly. So something has happened when applying the update. Today, I found a new NOD32 update, 14.0.22.0, which I hoped should solve the problem, but it did not. Likewise, I updated both firefox and thunderbird to latest releases, but the problem is still there. I tried to find some useful changelog but could not find any other than a very high-level description which did not help me.

    So I wonder, given that I did not have these problems until I did the update yesterday, what has happened in NOD32 that broke my browsing and email reading? For obvious reasons, I don't want to have protocol filtering disabled permanently.

    Regards, Joakim

  5. Hello again,

    for the record, as of last week, the update process started to work again without network failure. I do not know the reason for this; I have not during this week modified or updated my computer in any way, apart from NOD32 signature updates and MS Defender.  I don't know if ESET or Microsoft changed anything, but I am happy. :-)

     

    Regards, Joakim

  6. 4 hours ago, itman said:

    Note that Eset IDS has an Intrusion detection setting to block unsafe addresses after an attack. Assume the Wi-Fi router if has built-in IDS protection performs the same activity. 

    I checked my Tilgin router, provided by my ISP, and I could not find any intrusion detection settings in it. (Although, I consider the setup of that router to be rather complex and somewhat hard to get a grip on, so I might have missed it,)

  7. 17 hours ago, itman said:

    This tells us the problem is related to your Wi-Fi network connection.

    As to why an Eset update would interfere with the Wi-Fi connection is a mystery. One possibility is that the security encryption for the Wi-Fi connection has not been properly set-up. This might be causing the Eset update download to hang. This in turn hangs the Wi-Fi network connection.

    Best to open up an Eset technical support request on this.

    Sorry, I believe I haven't been completely clear in my problem description. The download of the update works fine, and it seems to install correctly as well, but it is (more or less immediately) after the update has been installed that the network connection goes down. I use ping towards another node in my network, and I get "Request timed out" and "Destination host unreachable", until the connection is restored again after three minutes.

    Please note that this Eset update operation has worked without any problems for many years, up until around two weeks ago. I checked if I had installed any software at that time, but I had not.

    Could you please give directions on how I go about opening a support request?

  8. itman, I connected my computer using Ethernet cable before doing an update, and this time the network remained up. I should test it one more update before I can say it works, but it looks like it does. What does that tell us?

    Btw, as I mentioned, I am running Windows 7, not 10.

    EDIT: And I now just did a second update with Ethernet cable, and there was no network failure. I also noticed that the little icon in the system tray did spin for almost exactly three minutes after updating, similar to the time that the wifi is down. Is that a lead?

  9. Marcos,
    I do have the Cleaner module 1211.1 installed.

    And I'm sorry, but to uninstall EAV, install a demo version of ESET Internet Security, then uninstall that before it expires and finally potentially reinstall EAV, is way too much of a hazzle for me to do on this old computer, which I am soon to replace anyway. I am just worried that this problem will show up also on my new computer, should I choose to install EAV on that one as well. I have used EAV for many years and I have never experienced any problems with it, until now.

    However, if no solution can be found for my current computer, I'll just have to live with it. I did find the alert letting me decide whether to install updates or not, so at least I can postpone my three minutes of wifi blackout to a suitable point in time.

    @itman, I am not using a VPN connection, thanks for asking.

  10. Thank you for your reply!

    I did as you suggested, but unfortunately it did not seem to help, soon (some seconds up to a minute or two) after I install the updates, the network stops responding for three minutes and then comes back again. So I am returning to the regular update channel again.

    Looking through the logs, I found an entry dated 10th July, that is, after the problem started, that says (in translation): "Undocumented serious error (500b)", with no further information. Can this be a lead?

  11. Hello,

    I started to notice about a week ago that my wifi connection occasionally stopped working for a while and then reconnected again. Most often this happened when i started up my computer, but could also occur while it was running. I confirmed using another computer that the problem was not the wifi.

    Today when it happened again, I was going through the NOD32 logs, and I found that this network outage (I have clocked it to be a little over 3 minutes) occurs at the same time as NOD32 updates the detection engine which it does regularly, or, if the computer was shut down by that time, when the computer starts up again. Needless to say, I find this very annoying. Can
    somebody here assist me?

    ESET NOD32 was updated on July 12 to product version 13.2.15.0, but the problem did occur before the update. The computer runs windows 7.


    Best regards,
    Joakim

×
×
  • Create New...