Jump to content

Marcos

Administrators
  • Posts

    37,941
  • Joined

  • Last visited

  • Days Won

    1,504

Everything posted by Marcos

  1. This is not possible because the membership in dynamic groups is evaluated by the ERA agent installed on computers.
  2. Although not related to this topic, the Antispam folder has always been created automatically as long as integration with the email client was enabled. I assume that disabling automatic start of antispam protection would also prevent the folder from being created.
  3. Of course it never happened with v10 because these notifications were first added in the latest v10.1 build.
  4. If the message appears only for a short time and then it disappears, the potential risk of getting infected with a new malware should be very low. Please try changing the update type to pre-release updates in the advanced update setup and see if it makes a difference. Should the warning still appear, please create a Wireshark log with network communication from that time captured.
  5. Try creating an allowing rule for ICMP and moving it to the top above pre-defined rules that are hidden by default. You'll need to unhide them to accomplish that.
  6. Since you are able to reproduce it, please use Wireshark to capture the network communication until the issue occurs. When done, compress the pcap log and post it here or send it directly to me via a private message.
  7. It's a known bug which will be fixed in the next service release of v11. Is the folder d:\caches persistent? Its content may not be cleared after a reboot.
  8. Only one real-time protection can be active at a time. You can disable automatic start of real-time protection in the advanced setup but this will substantially deteriorate protection provided by ESET. The best would be to convince the admins to allow ESET as an alternative AV but that'd be probably a lost battle.
  9. Do you get this error only shortly after starting Windows or even later when the Internet communication appears to work just fine? Could you try switching to pre-release updates and see if the error occurs less often?
  10. We've received the following notice instead of the actual update.ver file: Application Blocked! You have attempted to use an application which is in violation of your internet usage policy. NOD32.Update Category: Update URL: http://91.228.166.16/eset_upd/v10/dll/update.ver Client IP: 10.12.17.7 Server IP: 91.228.166.16 User name: Group name: Policy: bae90eb4-0f61-51e5-bbf5-e5d9f4906456 FortiGate Hostname: Blumarine_Attitude It appears that you connect to the Internet from a company's network and FortiGate blocked the network communication with an ESET's update server.
  11. We will continue to use version numbers but they will be used rather for internal identification of products than being used in marketing and sale.
  12. Please install Wireshark and capture the network communication during an update. When done, save the log in the pcap format and attach it here or send it to me via a private message.
  13. Please collect logs with ESET Log Collector in case we'll need it for analysis. Then uninstall EIS and install the latest version from scratch. EIS should not download the Password manager since it's only a part of ESET Smart Security Premium (ESSP). If you attempt to change the installed product, are you offered ESSP as well?
  14. To my best knowledge, this will be fixed in the upcoming service release of v11. Currently we recommend using default folders.
  15. The years in the version number were just for the marketing purposes in some countries. In Slovakia we never named them version 2015, 2016, etc. but we've always used the internal number (v9, v10, v11,...) for reference. Consumer products are now provided more like as a service than a product with a new version released each year. It's similar to Windows OS; in the past Microsoft had Windows 95, 98, Windows XP, etc. and now has Windows 10 with regular updates and bigger OS updates at times, such as the last Falls Creator Update.
  16. First of all, please uninstall ESET, then run the Uninstall tool in safe mode and install the latest v11 from scratch. Should the problem persist, collect logs with ELC, upload the generated archive to a safe location (e.g. OneDrive, Dropbox, etc.) and drop me a private message with a download link.
  17. Please create a new topic for this. It sounds rather like a bug than something to be improved in future versions. Also provide a screen shot of the window where you enter the email address since I have no clue what you mean by "sender filter". I was able to enter an email address with the "loan" TLD in the smtp notifications setup.
  18. It works C:\>ping 8.8.8.8 Pinging 8.8.8.8 with 32 bytes of data: General failure. General failure. General failure. General failure. You need to check the box to enable display of default rules and put your custom block rule above the default rule "Allow outgoing ICMP communication (echo request)".
  19. EFSW 6.5 cannot create a mirror for Endpoint 6.6+ since it uses a different format of module files. However, you can use the Mirror tool to create a mirror and install a simple HTTP server that will serve the mirror content to Endpoint 6.6 clients.
  20. Please use this topic only to report wishes and suggestions for future improvements. Do not use it for discussions on a particular subject. If you want to discuss something, create a new topic.
  21. We regularly add support for newer versions of browser if changes in them require the BPP module to adapt to them. You can switch to pre-release updates to get new modules among the first.
  22. I'm afraid there's no way to work around it than by using exclusions.
  23. You can try if it helps you. To my best knowledge, we keep information that the value was changed after installation and do not attempt to change it back then.
  24. There's a solution for you; just run: eis_nt64_ENU.exe --silent --accepteula --language 1034 --msi-property ADMINCFG="%path_to_the_cfg_xml%"
×
×
  • Create New...