"Compilation Of Tutorials, Guides, Tips & Updates"

[steven36]

I'm starting to think it will take a mircale for them not to check the expire date of your key .. Because you can very easily activate expired keys offline but once they check for updates they expire .

Old versions of ESET didn't even have and activation server, they just checked keys thorough updates was all , that activation server was something added down the line and easily be fooled .

Once the results comes out with mara-'s new fix the real truth will be widely known it would be nice if i didn't have to get a new key every time expired but from my testing the future looks very grim :(

[mara-]

Yes, I also suspect that this won't work. Otherwise, we would be able to use expired keys. There is also a possibility to get new key every 30 days, but that would require disabling self-defence, reboot, getting new key, enable self-defence, reboot, which is not very convenient, but it can happen that this will be only solution when Eset v4 servers stops working.

Cheers ;)

[exodius]

This trick no longer works.

[dcs18]

This trick no longer works.

Working fine, for me - just updated 2.1.4 to 2.1.5 :secret:

What seems to be the issue, on your end?

[steven36]

This trick no longer works.

Working fine, for me - just updated 2.1.4 to 2.1.5 :secret:

What seems to be the issue, on your end?

Its a keygen issue with Yamicsoft Windows 7 Manager 5.0.0 always keygens stop working on major version change . They will have to use old version tell it gets new medicine.

[dcs18]

Fixing ESET With Windows Firewall Control

This share is being brought to you on behalf of Torres - it actually belongs to him (my humble contribution constitutes just the last 2 steps - step # 06 and step # 07.) Once Torres decides to register himself, here - this post shall be taken down (once again - all due credits go to Torres.)

This tutorial is now available and shall be kept updated, by Cortana - at the following link:--

//www.nsaneforums.com/topic/222515-prevent-idm-other-programs-from-dialing-home/page-78?do=findComment&comment=855625

[kantry123]

just represented the above Ip's to be allowed in HORIZONTAL order

here's the list of IP

38.90.226.36,38.90.226.37,38.90.226.38,38.90.226.39,91.228.166.13,91.228.166.14,91.228.166.15,91.228.166.16,91.228.167.21,91.228.167.26,91.228.167.132,91.228.167.133

[idmresettrial]

I guess Eset will not let us update unless they accept the ID & password sent to their server.

Something like this:

If isValid(Lic):    Return updatePackageElse:    Return nothing

[dcs18]

Here is the representation of those IP range:--

91.228.167.21,91.228.167.26,91.228.167.132,91.228.167.133,38.90.226.36-38.90.226.39,91.228.166.13-91.228.166.16

[kantry123]

Yeah ESET Stop US if u can

[dcs18]

I guess Eset will not let you update unless they accept the ID & password send to their server.

Yep exactly, that was the reason for mentioning the condition of a valid and working license:--

02.) Switch on your net and activate your copy with any license (Trial / Retail) - it should be a valid working one (those wanting to test out this new method, may want to select a license with the shortest expiry date.)

[idmresettrial]

I guess Eset will not let you update unless they accept the ID & password send to their server.

Yep exactly, that was the reason for mentioning the condition of a valid and working license:--

02.) Switch on your net and activate your copy with any license (Trial / Retail) - it should be a valid working one (those wanting to test out this new method, may want to select a license with the shortest expiry date.)

What will happen when the lic is expired? Will Eset still be able update?

Can we create a minor server for updating which do not require an valid Lic ? :d

[dcs18]

What will happen when the lic is expired? Will Eset still be able update?Can we create a minor server for updating which do not require an valid Lic ? :D

As per my protracted testing - the license which was due to expire on the 9th of December - continues to work, in activated state (since the server at which it can be verified is blocked - at step # 5.)

Have not yet had the opportunity of trying out the server part - sounds possible in theory, though.

[steven36]

When I test this by just allowing those v8 update ips it checks expired keys after i have activated them as soon as i try update it spits the key out.

Same problem as before

//www.nsaneforums.com/topic/222515-prevent-idm-other-programs-from-dialing-home/?p=850902

[dcs18]

Expired keys wont work - check out point # 2.

[steven36]

If expired keys that's activated before you allow updates don't work . Were is any proof that its not going expire my key I have set to expire on the 24 th ? you guys have been testing this since what Aug ? and only one person said they really past expire it stop working for them after 2 weeks . Are you using a expired key by any chance and its still updating ?

[dcs18]

Please either follow the guide completely or not at all - also, remember a couple of things are being disclosed here for the very first time (even Torres is not yet aware of the same.)

I would personally suggest using some other fix, if you cannot get this working, for you.

[steven36]

Thats not what I ask you .

[exodius]

Working fine, for me - just updated 2.1.4 to 2.1.5 :secret:

What seems to be the issue, on your end?

I'm using windows 7 manager, mine its always trial after inserting key. :confuse:

[rudrax]

@dcs18, I have a activated ESET with TNOD. So if I block/allow those IPs specified in the guide, will my activation last forever?

P.S. You got your reply in the SB.

[steven36]

Yes, I also suspect that this won't work. Otherwise, we would be able to use expired keys. There is also a possibility to get new key every 30 days, but that would require disabling self-defence, reboot, getting new key, enable self-defence, reboot, which is not very convenient, but it can happen that this will be only solution when Eset v4 servers stops working.

Cheers ;)

If what is happening is what I think that happening . The developers at ESET are laughing at this whole thing. Witch I'm soon to find out for myself :)

[dcs18]

@dcs18, I have a activated ESET with TNOD. So if I block/allow those IPs specified in the guide, will my activation last forever?

If you follow the guide, word-to-word - you can eat your cake and have it, too.

Please post the results, here.

[dcs18]

Working fine, for me - just updated 2.1.4 to 2.1.5 :secret:

What seems to be the issue, on your end?

I'm using windows 7 manager, mine its always trial after inserting key. :confuse:

I did not have to insert any key - the same activated state of my previous Windows Manager 8, v2.1.4 has been carried forward to the present v2.1.5.

The last time I inserted a key was in 2013.

[mara-]

Yes, I also suspect that this won't work. Otherwise, we would be able to use expired keys. There is also a possibility to get new key every 30 days, but that would require disabling self-defence, reboot, getting new key, enable self-defence, reboot, which is not very convenient, but it can happen that this will be only solution when Eset v4 servers stops working.

Cheers ;)

If what is happening is what I think that happening . The developers at ESET are laughing at this whole thing. Witch I'm soon to find out for myself :)

Yes, anything can happen, but if we look from logic point of view, it sounds strange. In order to get updates, Eset must login with user name and password on the update servers, so updates servers are checking it. It's possible that there is separate expiration server, and there is some kind of delay between them. But, I'll keep monitoring this, and won't release anything until I'm sure it works.

Cheers ;)

[dcs18]

In order to get updates, Eset must login with user name and password on the update servers, so updates servers are checking it. It's possible that there is separate expiration server, and there is some kind of delay between them.

There are 2 servers for key verification and then there are 12 other servers (IPs) for the Virus signature database updates - the hosts cannot possibly block any of those IP (can block only their corresponding hostnames - which ESET has been rotating regularly.)

FWIW, I am monitoring the ESET servers for any change in IP, myself - there has been no change in the past 6 months.