Eset Activation Code

0 views
Skip to first unread message

Florentina Holcombe

unread,
Aug 3, 2024, 4:16:49 PM8/3/24
to spirtirapar

By looking at all event journals, I found a lot of times, the error below in the "code Integrity" journal. I'm not sure my problems come from this, but I prefer ask you for it, especially because I notices all recorded times correspond to my lock times.

- configure Windows to generate complete memory dumps as per
- reboot the machine
- reproduce the lock
- manually generate a system crash as per the above KB so that a dump is generated
- after a reboot, compress the memory dump
- collect logs with ESET Log Collector
- open a support ticket with your local ESET distributor and provide them with the dump and ELC logs.

Code Integrity determined that a process (\Device\HarddiskVolume6\Program Files\ESET\ESET Security\ekrn.exe) attempted to load \Device\HarddiskVolume6\Program Files\Bonjour\mdnsNSP.dll that did not meet the Custom 3 / Antimalware signing level requirements.

Appears Bonjour attempts to inject mdnsNSP.dll into every running process: -why-does-bonjours-mdnsnsp-dll-inject-itself-into-every-process . Eset's ekrn.exe process won't allow that due to certificate restrictions employed on it.

Please excuse my lack of understanding of this process. Our company had many layoff due to the Covid 19 and my head security officer has been laid off. I am looking for help in setting up agent on local PC's that are on the outside of our network. All local domain computer are functioning as expected with tasks from Security Management Center. I about 5 pc's that are at other locations that I would like to manage with SMC. Only when the PC are logon onto the network through a VPN software does the SMC apply the tasks correctly. Problem is, these computers really don't log in to the network very often, only to get rare files. I have tried to set up the agent to connect to the server hosting SMC. I have set up firewall ports 2221-2225 to point to this server using the same url that the VPN connects to successfully. Could someone please help me with what this error means?

There is obviously a problem with the agent peer certificate which cannot be verified. Create a fresh agent live installer and re-deploy it on the client so that the current CA and peer certificates are installed and used.

Ok, I redid the agent like you asked and connected via vpn to my local network with ESMC server and all is fine. Once I disconnect the VPN the management center now can not see the client anymore. Is there a way to configure the agent so It can connect to my server with being connected to a vpn software?

From logs it seems that after reinstallation, AGENT is connecting (or attempting to do so) to different hostname, containing .local. Maybe problem is that it cannot use "local" hostname when connection from outside of internal network? In case it is required to use different hostname (as visible in original logs), I would recommend to explicitly set it in installer configuration, or maybe ESMC Agent configuration policy containing both internal and external hostname should be used.

When your endpoints are not part of the VPN, eg. they are on their own network, whether a home network, coffee shop, public wifi...regardless of the case, they are no longer attached to your 'local network' - they are part of that networks 'local network'

1) The ESMC will need an outside IP address to reach with ports 2222 open (this can be accomplished by placing a public IP NAT that is bound to the internal IP address or port forwarding 2222 from that internal address, but traffic must be allowed in and out) -- obtain the public IP address of that device (typically will be firewall external address if going port forwarding, or NAT public internet address, save that for next step)

Include the IP address on the inside, include the inside IP address as first on list, and add the external address (NAT or FW pub IP) as second and then assign that to (I usually would just say all, it wouldn't hurt) those devices; its best to use that red lightning bolt for admin enforcement, and just to make sure there isnt any other conflicts at hand --- test out one or two devices if possible, take a laptop home or something for a test

3) Have endpoints that have not received policy - VPN in or connect to corporate network as soon as possible once that step two is successful. When the endpoints check in, they should obtain the policy update for the ESMC/ERA agent

Following on from what @TonyK has said, the following KB shows you how to allow External Communications to ESET Security Management Center 7.x to allow manageability of remote Machines.
-network-configuration-requirements-for-allowing-clients-to-connect-to-eset-security-management-center-remotely

Let me throw in another solution possible (Though it's hard to understand the security level of it)
You can create a proxy in the cloud that will only be used for ESMC reports (and not mirror for AV Installation files\images to minimize the data usage costs)

that way whenever the agent fails to report the local server, it use a failover using the proxy to reach it the other way around.

(I managed to perfect that method in my case, where we do not allow local servers access from the external network internally.)

Hello. I have reinstalled my eset internet security software and i can't activate my license. After I log in, when i choose the license and click continue, i get this message "Activation failed, An error occurred during activation" "An internal error occurred during the activation process"

I don't remember. Searching through my emails i have found the email from nor...@orders.eset.com thanking me for purchasing ESET Internet Security. But if my licences were issued for an Afghan reseller, how is the other license working on my laptop? Btw, i'm in Romania.

Why i was able to activate an Afghan locked license in Romania in the first place? I came here to find the solution to my problem, only to find out i was sold a faulty license and it's my fault, one year after the purchase while everything works fine on my other device. This is absurd!

Thank you! After a little bit of searching through my emails i have found my purchase information. I have bought two licences for ESET Internet Security on -internet-security-key-3-years-1-pc . I have contacted both the license seller and Kinguin support. Hopefully we can resolve this issue without involving the bank for refund.

On their marketplace, you can find everything from Windows keys (both the Pro versions and Home versions), to World of Warcraft time cards, to CSGO skings, to game keys for popular games (like PUBG), all the way to software (like anti-virus programs and Microsoft Home Office.)

very easy, you don't even need a VPN, during the initial activation, it will ask you for the customer name, and email address, then the country, if you select the correct country (ie. Afghanistan in this case) then the activation will work regardless of the geographical IP address of the computer.

I know this because I work for a computer reseller in California and our ESET distributor is in Dubai. We have to select the region as UAE and then the activation iwill work and is permanent regardless of the location or IP of the laptop.

I need help with the installation of eset. I keep having this error code even though I have reinstalled eset and restarted my laptop a number of times. I have also downloaded the installation fixer but it doesn't open (like something is stopping it?) Any help regarding this matter is highly appreciated.

If malware is again found, you will need to create an Eset SysRescue CD/USB media. Instructions on how to do so are here: . It is best to create this media on a non-infected device. Boot to the CD or USB drive and run a full system scan using it.

Over the past two days, different customers have been responding that after installing EEA/EFSW, the product activation failed with the error code: ACT.0. I tried to connect to and it looked fine, and I got the following content:

I am having the same issue. I followed all the procedures -resolve-act-or-ecp-errors-during-activation-business-users, but all else fails. So I think there is an issue with the activation servers, even the trace logs shows no sign of blockings from the network side.

If you get an error, please try activating the product again or a bit later. Today we've been experiencing some issues with a part of the cloud infrastructure, causing some activation attempts to fail.

Seriously? Are you employed by ESET or do you speak on behalf of ESET corporate?

This is a forum where are users are posting valid and legitimate request and concerns.

It is a bit Oxymoronic isn't it?

EXAMPLE : LICENSING is crucial part of the software. If the LICENSING expires the App would not be activated and renewed. ESET allows the user to suppress the License status/notifications for such a core and fundamental function of the Application.

But ESET would not allow disable of the status/notification of "Missing Support for Azure Code Signing"? But they allow in in ESET Endpoint?

It does not makes sense. When both products are used in Business environments.

@Marcos I have no way to reach out to ESET corporate. Isn't this forum is a place for that where you get user's request and send it to ESET HQ? I am not the only one in this thread. There are other users as well.

@Marcos Let me ask you this?

Was there "Big Demand" to disable LICENSING notification/status? Which is the core part of your App. Did a lot of users write into to ESET HQ stating that we desire and "demand" to disable all licensing related notifications?? Tell me.

I am sure I will hear cricket sounds.

Then why did ESET give users the option to disable licensing notification/status? What was the rational explanation?

If ESET can users the options for licensing, they should also provide the option to disable "Missing Support for Azure Code Signing".

c80f0f1006
Reply all
Reply to author
Forward
0 new messages