Jump to content

Marcos

Administrators
  • Posts

    36,489
  • Joined

  • Last visited

  • Days Won

    1,452

Posts posted by Marcos

  1. There are 2 problems:
    1, You didn't uninstall ESET NOD32 Antivirus and install ESET Internet Security (a trial version). Only EIS and ESSP can create diagnostic firewall logs that can reveal the root cause of the issue.

    2, No diagnostic logs were included in the package. Prior to running ELC, with EIS installed make sure that you:
    - Enable advanced logging under Help and support -> Details for technical support.
    - Reboot the system.
    - Disable advanced logging.

  2. 19 minutes ago, Purpleroses said:

    So if I don't make any changes to rules etc.  Is it alright just to leave it  blocking unknown devices?  My computer is not at risk with this continuing  to block unknown devices?  I will just have tons of logs in my network protection.

    Not sure what you mean by blocking unknown devices. Do you have advanced logging turned off and logging verbosity set to informative (default) and not to "diagnostic"? What kind of records are being created in your firewall log?

  3. Try to generate a fresh Live installer. The paths inside the script should be as follows:

    eraa_installer_url="http://repository.eset.com/v1/com/eset/apps/business/era/agent/v7/7.0.471.0/agent_linux_i386.sh"
    eraa_installer_url="http://repository.eset.com/v1/com/eset/apps/business/era/agent/v7/7.0.471.0/agent_linux_x86_64.sh"

    Also I'd recommend upgrading ERA to ESMC or at least to the latest version of ERA 6.5 as soon as possible.

  4. Quote

    A threat (HTML/ScrInject.B) was found in a file that Microsoft Windows Search Protocol Host tried to access.

    There's nothing like that in the logs you provided. The only detections were:

    Win32/Bundled.Toolbar.Ask.G pot. unsafe app.
    HTML/Refresh.BC

  5. 1 hour ago, ram1220 said:

    People were having issues updating Windows 10 and Eset blamed the customer. After a bit of a heated debate for a while Eset finally admitted their problem and patched the program which fixed the issue.

    I was able to find only the following topics concerning issues with Windows updates, however, none of them turned out to be caused by ESET.  Therefore I will appreciate if you post links to the issues you were referring to.

    https://forum.eset.com/topic/15238-windows-updates-not-installing-using-eset/

    https://forum.eset.com/topic/15309-win-update-4093118repeating/

    To my best knowledge, we never blamed customers or other companies for issues without a proof and I haven't done so recently either. We are open to constructive discussion and troubleshooting various issues, however, this cannot be done without the help of users who experience issues.

  6. Please carry on as follows:

    1, Temporarily uninstall ESET NOD32 Antivirus and install ESET Internet Security. Activate a 30-day trial version.
    2, After updating modules, enable advanced logging under Help and support -> Details for technical support.
    3, Reboot the system.
    4, Disable advanced logging.
    5, Gather logs with ESET Log Collector and post the generated archive here. Also raise a support ticket for customer care so that the case is tracked properly and provide them with the ELC logs as well.

    After the issue has been sorted, you will downgrade to EAV.

×
×
  • Create New...