Hi All,
How can I be sure that a email arriving in the exchange mailbox has been scanned by EMSX? If your answer is "X-ESET header", second question is "If this tag is missing in the header, does it mean it has not been scanned for sure?" Thank you.
↧
A Simple Question About EMSX
↧
ESET Security Management Console v7.2 update
Hy Community!
I have a problem, i cant update my Security Management Console .....
What can i do ?
↧
↧
Error "Login Failed: Connection has failed with the state of 'Not connected'" in ESET Security Management Center Web Console
Hi,
I try to update the server CA by adding a custom CA (using Webmin) and I see an error. Then I lose the connection to the web console.
I try to go through all the steps as mentioned in this link:
https://support.eset.com/en/kb6813-error-login-failed-connection-has-failed-with-the-state-of-not-connected-in-eset-security-management-center-web-console-7x
But unfortunately no result. (my server is Centos7)
Please give me a solution. I attached all the useful data.
↧
eset mail server question
Dear support!
We have on premise exchange 2013 running on Windows server 2016 standard and eset mail security version 7.0.10019.0. Today I logged in to the server, and the eset mail warned me about the Antivirus protection module, that something is not okay i dismissed the messeage. I checked the logs, and started Eset shell, used the get status command, to check the status of the modules, and all are enabled, getting the "maximum protection" messeage. To be sure, I turned off and on the module, everything looks fine. But, in the log files I still see warnings, look for the picture attached. Should i be worried, or this is safe to be ignored?
This XmonCom: Error while communicating with ThreatSense kernel warn still present in the logs. It is started 2 says ago.
↧
ESET Mail Security for Microsoft Exchange Server version 7.2.10007.0 has been released
Release Date: August 25, 2020
ESET Mail Security for Microsoft Exchange Server version 7.2.10007.0 has been released and is available to download.
Changelog
Version 7.2.10007.0
Fixed: Various fixes
Known Issues
To review a detailed and up-to-date list of known issues, see Known issues for version 7 ESET business products.
Support Resources
For more information and to download the product, visit the ESET Mail Security for Microsoft Exchange Server download page or contact your local reseller, distributor or ESET office.
↧
↧
ESET Security for Microsoft SharePoint Server version 7.2.15001.0 has been released
Release date: August 25, 2020
ESET Security for Microsoft SharePoint Server version 7.2.15001.0 has been released and is available to download.
Changelog
Version 7.2.15001.0
Added: Aggressive detections
Added: "Repeat last scan" option
Improved: The expiration date for MSP license doesn't show in EMSC
Fixed: Defender was disabled when Real-time protection was not installed
Fixed: Various fixes
Support Resources
Online Help (user guide):
ESET Security for Microsoft SharePoint Server
For more information and to download the product, visit the ESET Security for Microsoft SharePoint Server download page or contact your local reseller, distributor or ESET office.
↧
Error Installing Agent with Error checking Peer Certificate
Hi, i'm trying to install agent on linux centos 6, but failed with 1105: Error checking Peer Certificate. can you help me? thanks
↧
La protección del sistema de archivos en tiempo real no es funcional (Real-time protection is non-functional)
Estimados,
Agradeceré su ayuda.
La consola web del server muestra alerta "La protección del sistema de archivos en tiempo real no es funcional" para un equipo con S.O. Centos 7
adicionalmente muestra la alerta: "El sistema operativo no está actualizado"
software instalado es el siguiente:
ESET Management Agent 7.2.2233.0
ESET File Security 7.2.463.0
Machine translation:
I will appreciate your help.
The server's web console displays the alert "Real-time file system protection is not functional" for a computer with S.O. Centos 7
additionally it shows the alert: "The operating system is not up to date"
installed software is as follows:
ESET Management Agent 7.2.2233.0
ESET File Security 7.2.463.0
ESET Management Agent 7.2.2233.0
ESET File Security 7.2.463.0
↧
ESET detect threat only when the file is opened But not when scanned
ESET Endpoint for Linux detects the threat only when the file is executed or created within the NFS server , but if we scan the local drive it’s not detecting the file which was written by NFS client.
In this test server, we have shared one local drive and from client system was made to write some virus files remotely , But when we scan the drive it’s not detecting the virus file. The virus sample get from https://www.makeuseof.com/tag/how-to-safely-test-your-antivirus-software/
↧
↧
DNSBL vs RBL Mail security
Where should I be putting the servers? under 'Additional DNSBL servers' or 'Additional RBL servers' ? I am using
zen.spamhaus.org
bl.spamcop.net
psbl.surriel.com
b.barracudacentral.org
Currently they are in both, is this right?
↧
Allow specific file types inside archive
Hello All,
I'm new to ESET and ESET Cloud Administrator, I want to control rules around what is allowed/blocked by the Exchange Transport Scanner. Due to the nature of my business, I need to be able to allow the transfer of some files inside a compressed archive (.zip). However, I do not want these files to be transferred if sent directly attached to the e-mail.
Is this possible and if so how? I can only see a way to completely block or allow those files.
Thanks
↧
Update ESET Remote Administrator (Server), Version 6.4.304.0
Hallo,
Info für die VM:
ESET Remote Administrator Appliance
CentOS ESET Remote Administrator Appliance
Gastbetriebssystem: CentOS 4/5/6/7 (64-bit)7 (64-bit)
Aktuell Version:
ESET Remote Administrator (Server), Version 6.4.304.0
ESET Remote Administrator (Web Console), Version 6.4.280.0
beim Upgrade bekommen wir die meldung
wird erfolgreich durchgeführt:
1.wget https://download.eset.com/com/eset/apps/business/era/server/linux/latest/server-linux-x86_64.sh
2.sudo chmod +x agent-linux-x86_64.sh
chmod: cannot access ‘agent-linux-x86_64.sh.1’: No such file or directory
vielen Dank für Ihre Unterstützung.
↧
Possible upgrades of ESET Business Product.
Possible upgrades of ESET Business Product.
Hello everyone and thanks for hosting my question in the forum.
I am doing a research for a client at this moment and I can’t find any clear answer to my questions through the websites of ESET.
I will briefly explain a couple of things, so you can have a better image of the situation.
Right now, on a Server we are running an ESET NOD32 Antivirus 4 Business Edition protection, but according to ESET EOL Policies this version will be supported until December 2020. Although there is a transition period.
Our product is for one more year licensed, but as I mentioned before, is not going to be supported anymore.
Q: Can we upgrade our product? If yes is there a list with the upgrade possibilities? Which product are supported for the one-year transition period?
Q: ESET NOD32 Antivirus 4 Business Edition stops at the 4rth Edition, after that the 5th, 6th and 7th Edition continue as Endpoint Security and Endpoint Antivirus(?). Is this a rebranding of the older Antivirus 4 Business Edition?
Q: ESET NOD32 Antivirus 4 Business Edition is at the same category with Endpoint Security and Endpoint Antivirus, can we upgrade our product to one of those two?
Q: Is there any specific requirement for the migration/transition to a newer version? i.e. must the server be a Domain Controller or needs to have a specific role?
Thank you in advance for any your answers!
↧
↧
Kernel Panic crash
Hello,
Some of our user experience multiple kernel panic issue lately.
Here some log if you can help us :
panic(cpu 0 caller 0xffffff8012a02d5d): "Invalid queue element linkage for 0xffffff80496a5240: next 0xffffff804d47cb70 next->prev 0 prev 0xffffff804d47cb70 prev->next 0"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Binaries/xnu/install/TempContent/Objects/EXPORT_HDRS/osfmk/kern/queue.h:247
Backtrace (CPU 0), Frame : Return Address
0xffffff92385a3610 : 0xffffff80123215cd
0xffffff92385a3660 : 0xffffff801245a3c5
0xffffff92385a36a0 : 0xffffff801244bf7e
0xffffff92385a36f0 : 0xffffff80122c7a40
0xffffff92385a3710 : 0xffffff8012320c97
0xffffff92385a3810 : 0xffffff8012321087
0xffffff92385a3860 : 0xffffff8012ac2c7c
0xffffff92385a38d0 : 0xffffff8012a02d5d
0xffffff92385a3900 : 0xffffff7f97ab180e
0xffffff92385a3920 : 0xffffff8012997c91
0xffffff92385a3950 : 0xffffff8012997a66
0xffffff92385a3970 : 0xffffff8012999c3f
0xffffff92385a3990 : 0xffffff7f97aae995
0xffffff92385a39c0 : 0xffffff8012a05511
0xffffff92385a3a00 : 0xffffff8012a2d2fe
0xffffff92385a3a40 : 0xffffff8012a045d4
0xffffff92385a3ac0 : 0xffffff8012a038d7
0xffffff92385a3b20 : 0xffffff8012a073b0
0xffffff92385a3ba0 : 0xffffff8012a26c21
0xffffff92385a3be0 : 0xffffff8012a26ee7
0xffffff92385a3c20 : 0xffffff80129ab3f1
0xffffff92385a3c60 : 0xffffff80129b1fdf
0xffffff92385a3ce0 : 0xffffff80129c2198
0xffffff92385a3d60 : 0xffffff801238277b
0xffffff92385a3db0 : 0xffffff8012327328
0xffffff92385a3e10 : 0xffffff80122fdcc5
0xffffff92385a3e70 : 0xffffff8012314aa2
0xffffff92385a3f00 : 0xffffff8012432605
0xffffff92385a3fa0 : 0xffffff80122c8226
Kernel Extensions in backtrace:
com.eset.kext.esets-mac(680.40f1)[D1A3AE37-E13D-3734-8E6D-7B04FF00D5E7]@0xffffff7f97aa9000->0xffffff7f97ac3fff
dependency: com.apple.iokit.IOSerialFamily(11)[5E856447-43DC-3AE4-BC25-2CBBEFFBCBA5]@0xffffff7f92f6b000
dependency: com.apple.iokit.IOUSBFamily(900.4.2)[3AEBCBF6-21D4-3BDE-8732-1D3984F73392]@0xffffff7f9386d000
dependency: com.apple.iokit.IOSCSIMultimediaCommandsDevice(422.101.1)[112002A3-3196-3B2A-A0FE-CC5EEE112BB2]@0xffffff7f93842000
dependency: com.apple.iokit.IOStorageFamily(2.1)[425BC668-32EC-368C-B4EB-CF8510846BEE]@0xffffff7f9307f000
dependency: com.apple.iokit.IOFireWireFamily(4.7.5)[4E71D4F9-398B-3B08-833F-4F264F1001A2]@0xffffff7f97a36000
dependency: com.apple.iokit.IONetworkingFamily(3.4)[3F6EDFDE-6EF7-38D8-8006-C4EE6DB4D4B5]@0xffffff7f930af000
panic(cpu 0 caller 0xffffff801fa0171d): "Invalid queue element linkage for 0xffffff8063f80470: next 0xffffff8065847bb0 next->prev 0xffffff806ff95bb0 prev 0xffffff8065847bb0 prev->next 0"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Binaries/xnu/install/TempContent/Objects/EXPORT_HDRS/osfmk/kern/queue.h:247
Backtrace (CPU 0), Frame : Return Address
0xffffff9253443610 : 0xffffff801f31a65d
0xffffff9253443660 : 0xffffff801f454a75
0xffffff92534436a0 : 0xffffff801f4465fe
0xffffff92534436f0 : 0xffffff801f2c0a40
0xffffff9253443710 : 0xffffff801f319d27
0xffffff9253443810 : 0xffffff801f31a117
0xffffff9253443860 : 0xffffff801fac1abc
0xffffff92534438d0 : 0xffffff801fa0171d
0xffffff9253443900 : 0xffffff7fa39adb78
0xffffff9253443920 : 0xffffff801f9952d1
0xffffff9253443950 : 0xffffff801f9950a6
0xffffff9253443970 : 0xffffff801f99727f
0xffffff9253443990 : 0xffffff7fa39aafd5
0xffffff92534439c0 : 0xffffff801fa03ed1
0xffffff9253443a00 : 0xffffff801fa2bcde
0xffffff9253443a40 : 0xffffff801fa02f94
0xffffff9253443ac0 : 0xffffff801fa02297
0xffffff9253443b20 : 0xffffff801fa05d70
0xffffff9253443ba0 : 0xffffff801fa25601
0xffffff9253443be0 : 0xffffff801fa258c7
0xffffff9253443c20 : 0xffffff801f9a8a31
0xffffff9253443c60 : 0xffffff801f9af61f
0xffffff9253443ce0 : 0xffffff801f9bf7d8
0xffffff9253443d60 : 0xffffff801f37b9eb
0xffffff9253443db0 : 0xffffff801f3203c8
0xffffff9253443e10 : 0xffffff801f2f6d15
0xffffff9253443e70 : 0xffffff801f30db22
0xffffff9253443f00 : 0xffffff801f42c065
0xffffff9253443fa0 : 0xffffff801f2c1226
Kernel Extensions in backtrace:
com.eset.kext.esets-mac(690.6f1)[C4F2DAA6-364A-3883-8BB8-3BCD0C1A1F68]@0xffffff7fa39a6000->0xffffff7fa39bdfff
dependency: com.apple.iokit.IOSerialFamily(11)[DF4126A9-00D7-3A74-AE9C-BD80839409EB]@0xffffff7f9ff6c000
dependency: com.apple.iokit.IOUSBFamily(900.4.2)[3F343021-2C10-3568-BAF8-E81088923D3E]@0xffffff7fa08c1000
dependency: com.apple.iokit.IOSCSIMultimediaCommandsDevice(422.120.3)[FBF3D028-A942-3E17-AEE0-F71BBE7A1677]@0xffffff7fa3919000
dependency: com.apple.iokit.IOStorageFamily(2.1)[3581A46A-F3F3-3CE7-BA52-7046E8D66C32]@0xffffff7fa0080000
dependency: com.apple.iokit.IOFireWireFamily(4.7.5)[9565A679-1A7F-377B-8B68-7419AFDA88F8]@0xffffff7fa3933000
dependency: com.apple.iokit.IONetworkingFamily(3.4)[2FA065D5-72F7-3BE5-855C-E45B01AEFBD4]@0xffffff7fa00b0000
BSD process name corresponding to current thread: kextunload
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev
Mac OS version:
19G2021
Kernel version:
Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64
Kernel UUID: 1D3A0F3D-D908-397B-BD16-8F48C0823A2E
Kernel slide: 0x000000001f000000
Kernel text base: 0xffffff801f200000
__HIB text base: 0xffffff801f100000
System model name: MacBookPro16,2 (Mac-5F9802EFE386AA28)
System shutdown begun: NO
System uptime in nanoseconds: 359003251953428
last loaded kext at 349333178143912: >AudioAUUC 1.70 (addr 0xffffff7fa349b000, size 28672)
last unloaded kext at 358998193620106: com.eset.kext.esets-kac 690.06.00f01 (addr 0xffffff7fa3860000, size 483328)
Thank you !
↧
Agent Failed To create subchannel
Hello,
many of my agent have this log in agent trace.log
2020-08-26 23:40:05 Error: CNetworkGrpcModule [Thread 155c]: GRPC:Failed to resolve: esmc.mycompany.com:20033
2020-08-26 23:40:05 Error: CReplicationModule [Thread bb4]: InitializeConnection: Initiating replication connection to 'host: "esmc.mycompany.com" port: 20033' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "esmc.mycompany.com" port: 20033 with proxy set as: Proxy: Connection: 192.168.31.40:9999, Credentials: Name: , Password: ******, Enabled:1, EnabledFallback:1, failed with error code: 2, error message: Failed to create subchannel, and error details:
2020-08-26 23:40:05 Warning: CReplicationModule [Thread bb4]: InitializeConnection: Not possible to establish any connection (Attempts: 1)
and my agent can't connect to the ESMC.
i migrate my esmc from my cloud server to another server in my office.
i have offline network and i used apache in centos as HTTP proxy to connect to my cloud server. after i migrate to my office server i edit my /etc/hosts in centos 7 and add the esmc.mycompany.com address to resolve my local IP (when use my cloud server the esmc.mycompany.com can be access with FQDN because using external DNS) without changing anything in policy
after several weeks this error came in. and now some of my client didn't connect.
is there any solution of this ?
NOTE :
esmc.mycompany.com in external dns is 103.26.xx.xxx
esmc.mycompany.com in my office (offline network) is 192.168.xx.xxx
port esmc is 20033
my apache proxy is 192.168.31.40 with port 9999
↧
restore ESMC
hello
i am trying to migrate the ESMC from one server to the second ( the first one was messed up completely as i am having issues with support )
i have the certificates and backed up the ERA.DB from sql studio , what are the steps to restore the old server data on the new ?
if i used Eset remote installer and used the new server , can i replace the endpoints already installed remotely ?
↧
Can’t Uninstall ESET Endpoint Anti-Virus
When we try uninstall ESET endpoint AV I get an error saying it can’t and is missing Windows updates. I also get an error saying I don’t have rights even as administrator.
is there a manual uninstall procedure or uninstall tool?
Thanks!
↧
↧
firewall blocking known network
i have added my subnet to the known network hoping the firewall will not block any service in it , but it blocking several services like VNC per example
what did i miss ?
↧
Update using multiple proxy in the same subnet
Hi,
Our branches have two proxies in the same subnet, for instance:
proxy A: 192.168.0.1 -> Proxy that connected to each branch's internet provider
proxy B: 192.168.0.2 -> Apache http proxy that chained to http proxy in the HQ
Is it possible to have dual update profile for ESET Endpoint Antivirus 7.x, so the client will try to connect to proxy A first. While connection in proxy A is not ok (update failed, proxy cannot reach), then the client will try to update using proxy B as backup. Proxy A should has highest priority, so proxy B only be used if proxy A fails. At the end, direct connection should be used when proxy A and proxy B fail (probably when the client is outside the branch's network).
Thank you.
↧
Cannot open file /lib/modules/5.3.10-1-pve/eset/efs/eset_rtp.ko: No such file or directory
Hi,
i use proxmox mail gateway with Debian 10.5.
I am successfully installing and I can access eset gui. I can verify my license, but somehow I could not run the system. I have updated. I restarted but did not work.
root@pmg4:/# systemctl status efs
● efs.service - ESET File Security
Loaded: loaded (/lib/systemd/system/efs.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-08-30 14:54:06 +03; 6min ago
Process: 17745 ExecStartPre=/opt/eset/efs/lib/install_scripts/check_start.sh (code=exited, status=0/SUCCESS)
Process: 17773 ExecStartPost=/bin/sleep 2 (code=exited, status=0/SUCCESS)
Main PID: 17772 (startd)
Tasks: 30 (limit: 9482)
Memory: 224.9M
CGroup: /system.slice/efs.service
├─17772 /opt/eset/efs/sbin/startd
├─17774 /opt/eset/efs/lib/logd
├─17775 /opt/eset/efs/lib/scand
├─17776 /opt/eset/efs/lib/sysinfod
├─17777 /opt/eset/efs/lib/updated
├─17778 /opt/eset/efs/lib/licensed
├─17779 /opt/eset/efs/lib/utild
├─17780 /opt/eset/efs/lib/confd
└─17787 /opt/eset/efs/lib/oaeventd
Aug 30 14:54:04 pmg4 systemd[1]: Starting ESET File Security...
Aug 30 14:54:05 pmg4 oaeventd[17787]: ESET File Security Error: Cannot open file /lib/modules/5.3.10-1-pve/eset/efs/eset_rtp.ko: No such file or directory
Aug 30 14:54:05 pmg4 oaeventd[17787]: ESET File Security Error: Initialization of system handler for on-access scan has failed. Please update your OS and restart your computer, then check sy
Aug 30 14:54:06 pmg4 systemd[1]: Started ESET File Security.
root@pmg4:/# cat /etc/debian_version
10.5
root@pmg4:/# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@pmg4:/# hostnamectl
Static hostname: pmg4
Icon name: computer-vm
Chassis: vm
Machine ID: *******
Boot ID: *****
Virtualization: microsoft
Operating System: Debian GNU/Linux 10 (buster)
Kernel: Linux 5.3.10-1-pve
Architecture: x86-64
Eset File Security https://help.eset.com/efs/7/en-US/realtime-protection-cannot-start.html?system_requirements.html
System requirements
Hardware requirements depend on the server role. The following minimum hardware requirements must be met before the installation process in order to run ESET File Security for Linux properly:
The following operating systems of 64-bit architecture are officially supported:
•RedHat Enterprise Linux (RHEL) 6 64-bit
•RedHat Enterprise Linux (RHEL) 7 64-bit
•RedHat Enterprise Linux (RHEL) 8 64-bit
•CentOS 6 64-bit
•CentOS 7 64-bit
•Centos 8 64-bit
•Ubuntu Server 16.04 LTS 64-bit
•Ubuntu Server 18.04 LTS 64-bit
•Ubuntu Server 20.04 LTS 64-bit
•Debian 9 64-bit
•Debian 10 64-bit
•SUSE Linux Enterprise Server (SLES) 12 64-bit
•SUSE Linux Enterprise Server (SLES) 15 64-bit
How can I solve this problem?
↧