dcs18 Posted October 13, 2014 Author Share Posted October 13, 2014 Anybody who desires to test the effectiveness of the latest ESET fixing tutorial (without having to advance his / her system date) can make a shout on this thread for the following Trial key with a short (9 days) shelf life remaining:-- Link to comment Share on other sites More sharing options...
kantry123 Posted October 13, 2014 Share Posted October 13, 2014 Anybody who desires to test the effectiveness of the latest ESET fixing tutorial (without having to advance his / her system date) can make a shout on this thread for the following Trial key with a short (9 days) shelf life remaining:--Send me too..short trialI'm willing to test Regards Link to comment Share on other sites More sharing options...
dcs18 Posted October 13, 2014 Author Share Posted October 13, 2014 I know this is not gonna be appreciated by the likes of Nostra Damus - however, just couldn't stop myself from putting my evil side, on display:-- Link to comment Share on other sites More sharing options...
steven36 Posted October 13, 2014 Share Posted October 13, 2014 Fixing ESET With Windows Firewall Control - The Precautionary Measures06.) This step is a new implementation (an improvisation, I was working on long back - even prior to my motorbike crash) -an Allow rule exclusively for the following selected IPs (meaning - no other IPs except the following responsible for the ESET Virus signature database, shall be allowed):--38.90.226.3638.90.226.3738.90.226.3838.90.226.3991.228.166.1391.228.166.1491.228.166.1591.228.166.1691.228.167.2191.228.167.2691.228.167.13291.228.167.133Check out this implementation - it could change the way we do business on this thread:-- Have you ever messed with NOD Update Viewer ?It checks to see if the keys are valid or not thorough 91.228.167.21 one the ips you have allowed .I found something else out as well These are the IPS that TNOD checks keys withum02.eset.com/v7-rel-sta/mod_031_speclean_1002/em031_32_n2.nup (91.228.166.14)http://expire.eset.com /getlicexp (91.228.167.125)Seems all IPS in the 91.228 range can check to see if your key is valid or not. Link to comment Share on other sites More sharing options...
dcs18 Posted October 13, 2014 Author Share Posted October 13, 2014 Anybody who desires to test the effectiveness of the latest ESET fixing tutorial (without having to advance his / her system date) can make a shout on this thread for the following Trial key with a short (9 days) shelf life remaining:--Send me too..short trialI'm willing to testRegardsYou've got PM. Link to comment Share on other sites More sharing options...
mara- Posted October 13, 2014 Share Posted October 13, 2014 We'll sort that out when the time comes. Is the key you're using now expired? This is the most important part to test now.Cheers ;)The firewall method does not allow the key to expire - it preserves activated state as reflected by the screenshot on rudrax's post.The firewall method does not have anything to do with it. Firewall method only prevents Eset from getting expire date from server. Update servers are the ones who require loging, and there is nothing to stop Eset servers to block the key once it expires. I'm giving this only 10% that it will work, maybe there is some loophole.Cheers ;) Link to comment Share on other sites More sharing options...
steven36 Posted October 13, 2014 Share Posted October 13, 2014 Yes thats like when TNOD OR NOD32 Viewer checks keys to see if there valid .NOD32 Viewer uses 91.228.167.21 and will check to see if the key valid and when it expires .TNOD uses 91.228.166.14 to check if the key is valid but uses 91.228.167.125 just to check for expire date and is optional its not needed to check.Out all 3 those ips I have just one blocked from getting trough my NOD32 If you block too many it want update at all . :P Link to comment Share on other sites More sharing options...
dcs18 Posted October 13, 2014 Author Share Posted October 13, 2014 We'll sort that out when the time comes. Is the key you're using now expired? This is the most important part to test now.Cheers ;)The firewall method does not allow the key to expire - it preserves activated state as reflected by the screenshot on rudrax's post.The firewall method does not have anything to do with it. Firewall method only prevents Eset from getting expire date from server. Update servers are the ones who require loging, and there is nothing to stop Eset servers to block the key once it expires. I'm giving this only 10% that it will work, maybe there is some loophole.Cheers ;)In your own words (red-lighted above,) we will see very soon - it's a matter of a mere 10 more days. :coolwink: Link to comment Share on other sites More sharing options...
kantry123 Posted October 13, 2014 Share Posted October 13, 2014 bro dcs18 i've a question my wfc forgets the rules i made yesterdayThat is the reason why ESET connected to server on boot up WFC was asking whether to allow or deny the EKRN.exe service?do u know why this happens?regards Link to comment Share on other sites More sharing options...
dcs18 Posted October 13, 2014 Author Share Posted October 13, 2014 bro dcs18 i've a question my wfc forgets the rules i made yesterdayThat is the reason why ESET connected to server on boot up WFC was asking whether to allow or deny the EKRN.exe service?do u know why this happens?regardsWe can TeamView the issue and sort it out. ;) Link to comment Share on other sites More sharing options...
kantry123 Posted October 13, 2014 Share Posted October 13, 2014 bro dcs18 i've a question my wfc forgets the rules i made yesterdayThat is the reason why ESET connected to server on boot up WFC was asking whether to allow or deny the EKRN.exe service?do u know why this happens?regardsWe can TeamView the issue and sort it out. ;)Check>>PM Link to comment Share on other sites More sharing options...
kantry123 Posted October 14, 2014 Share Posted October 14, 2014 Bro dcs18after making the rules i activated with 9 days trial keysbut the ekrn.exe service is also asking to connect this IP eventhough the rules for both allow and block r madeSo do u want me to allow? this IP 38.90.226.11 port 80details of this IP%rwhois V-1.5:0010b0:00 rwhois.cogentco.comnetwork:ID:NET4-265AE20018network:Network-Name:NET4-265AE20018network:IP-Network:38.90.226.0/24network:Postal-Code:92101network:City:San Diegonetwork:Street-Address:610 West Ash Street, Ste. 1501network:Org-Name:ESET, LLC.network:Tech-Contact:ZC108-ARINnetwork:Updated:2013-09-23 19:44:24%okpls check and tell me whether to allow or deny?regards Link to comment Share on other sites More sharing options...
dcs18 Posted October 14, 2014 Author Share Posted October 14, 2014 @ kantry123Lemme know if you would like me to TeamView your ESET and WFC for a comprehensive G33K config (not limited to and way beyond the scope of this thread .) :) Link to comment Share on other sites More sharing options...
kantry123 Posted October 14, 2014 Share Posted October 14, 2014 @ kantry123Lemme know if you would like me to TeamView your ESET and WFC for a comprehensive G33K config (not limited to and way beyond the scope of this thread .) :)Check>>PM Link to comment Share on other sites More sharing options...
dcs18 Posted October 14, 2014 Author Share Posted October 14, 2014 All done, bro. - reboot you system a few times and do provide your feedback whenever you find time. Link to comment Share on other sites More sharing options...
idmresettrial Posted October 14, 2014 Share Posted October 14, 2014 no meaning post. Link to comment Share on other sites More sharing options...
dcs18 Posted October 14, 2014 Author Share Posted October 14, 2014 I can confirm that it is not an issue of time-zone, bro. Link to comment Share on other sites More sharing options...
dcs18 Posted October 14, 2014 Author Share Posted October 14, 2014 The latest IDM CC 7.3.88 add-on made compatible for Users of Mozilla Firefox Nightly V36 :–http://www.mediafire.com/download.php?ozfp8bp6uz3vu10 Link to comment Share on other sites More sharing options...
kantry123 Posted October 15, 2014 Share Posted October 15, 2014 Bro dcsUr ip method is still intactIt's working for nowThe key expired yesterday nightAnd the product still remains activated...till nowI'll test it till Diwali and let u knw the resultsRegardsAlso u forgot to Send me the theme linkCan u send me...if u have time? Link to comment Share on other sites More sharing options...
dcs18 Posted October 15, 2014 Author Share Posted October 15, 2014 The firewall method does not have anything to do with it. Firewall method only prevents Eset from getting expire date from server.Update servers are the ones who require loging, and there is nothing to stop Eset servers to block the key once it expires.Absolutely, false - on both the above counts.Yes, I also suspect that this won't work. Otherwise, we would be able to use expired keys.We can use expired keys.maybe there is some loophole.Cheers ;)Now, this is the only one point where we can either work together to bring the people a better firewall and box, mara- fix or continue to be influenced by the hollow words of Amateurs who specialize in snatching defeat from the jaws of victory - the choice is ours. Link to comment Share on other sites More sharing options...
mara- Posted October 15, 2014 Share Posted October 15, 2014 One day does not mean anything. One member reported that his key was blocked after 15 days. And I am correct about update servers. Loophole can be that expire server does not "call" update servers to tell it that key expired.Cheers ;) Link to comment Share on other sites More sharing options...
dcs18 Posted October 15, 2014 Author Share Posted October 15, 2014 You are wrong on both the counts.Not to also forget that my own activation never failed despite the report from that member - that is exactly what I meant in my previous post reproduced below:--Now, this is the only one point where we can either work together to bring the people a better firewall and box, mara- fix or continue to be influenced by the hollow words of Amateurs who specialize in snatching defeat from the jaws of victory - the choice is ours.It is most unfortunate that the tone of at least one person has been showing a pointed desire that this fix should fail. Link to comment Share on other sites More sharing options...
ZinnPL Posted October 15, 2014 Share Posted October 15, 2014 Firewall method do not working for me in v6.21 Build 14 Retail. I use Windows Firewall Control.1. I disabled IDM autorun.2. Added IPs to firewall (IDM can't check updates (error),3. Next I used "IDM_Cleaner" (as administrator).4. Ran IDM and registered with serial from SnD keygen.Program is registered but after IDM restart I have "fake serial" error.In Build 14 we have any new IP? :mellow: Link to comment Share on other sites More sharing options...
dcs18 Posted October 15, 2014 Author Share Posted October 15, 2014 In Build 14 we have any new IP? :mellow:No new IP in build 14, bro. - I am using it, myself. ^_^Can you post all your security programs - each one of them? Link to comment Share on other sites More sharing options...
ZinnPL Posted October 15, 2014 Share Posted October 15, 2014 I have only Windows Firewall Control. No any AV and other firewall. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.