"Compilation Of Tutorials, Guides, Tips & Updates"

[Cortana]

Kaspersky Firewall Guide

Deleted

Follow-up here: //www.nsaneforums.com/topic/222515-prevent-idm-other-programs-from-dialing-home/page-82?do=findComment&comment=856303

[Cortana]

Fixing ESET With Windows Firewall Control

Would like dcs18 to let his post remain for a few days, as my membership is still not confirmed :hehe:

01.) If you are an existing ESET User, rid your copy of all fixes - this is a clean method, if required opt for a fresh, full and clean install (new Users - disregard this step.)

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.)

03.) Reboot - you lazy bums.

04.) Your copy of ESET will now proceed to update, itself - if not, update it manually.

05.) Next, let's block the ESET activation servers and other servers responsible for blacklisting keys - 38.90.226.40, 91.228.165.81, 91.228.166.88, 91.228.167.125 and 91.228.167.170 as illustrated by the following Block rule:--

06.) 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.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

Check out this implementation - it could change the way we do business on this thread (for the bigger picture - click the following image):--

07.) Here is another improvisation - it is my own custom scheduling that is being shared here:--

For the bigger picture - click the following image:

All this work has been done by dcs18 himself, he is just being modest giving Torres the credit :yes:

[clubhouse]

Trial and error is not the same as beta testing. Also, divulging code and method is not the same. Everyone knows how box, mara- fix works, but you feel like you need to keep a secret why you blocked an IP. And sharing is the point of this forum. Also, please don't insult me by posting image of a post by that poor soul.

Cheers ;)

Agreed. I think most members here can use ip methods and trial and error will reveal if they are successful or not...Having skills to create patches and or keygens are a different kettle of fish...I'm in awe of guys like you :)

[dcs18]

@ Cortana :welcome:

Have taken down the ESET tutorial - wish you all the best.

Post # 1 and post # 2, duly updated - shall be updating the KIS tutorial to those sections, too.

[rudrax]

Have taken down the ESET tutorial - wish you all the best.

:lol: Can you do any better? :angry:

[dcs18]

Post # 1 and post # 2, duly updated with the Kaspersky tutorial, from Cortana.

[Cortana]

>--->

:rofl:

btw why u took down your own tutorial ?

[dcs18]

but when i use a proxy for download in IDM it discover that i use a fack srial, Except that all going fin

Post # 1499. 8)

[dcs18]

>--->

:rofl:

Gender readjusted. :hehe:

[steven36]

What no one has told how does these update ips expire your key?

I allowed 38.90.226.40 and rolled back updates 2 times and it updated with this IP 38.90.226.40 2 times and nothing happen

Also if you have used step 06, unless your firewall is leaking there would be no need to block more ips but original 2 on the list . So are you saying step 6 don't work for you ? If you keep having to block new ips evidently its not!step 6 is working fine for me I never had to add no new ips to the block list. :)

[dcs18]

Fixing Skype For A 100% Advertisement-Free Experience

A comprehensive tutorial coming up shortly - be patient, thank you (final touches being deployed.)

[wesh]

A quick check, to see if you set the rules right, is to now try and activate trial license, if you set the rules correctly it will display the following illustration

I have followed to the letter all the steps, tried 2 times, but everytime i actually CAN get a 30 days trial key. Nothing is blocked there. But, once i insert the blacklisted key, and update it 'til today, everything seems ok (i use the 1035 key). Thought you'd find it maybe interesting. Thanks a lot for this new method for KIS.

[steven36]

See what they are failing to tell you here is WFC leaks at boot up, even the developer knows it leaks. This is why they added the Secure Boot

Secure Boot saves the current firewall rules at system shut down in the installation folder, then it sets High Filtering profile. When the computer starts, High Filtering is enabled until wfc.exe starts again. When wfc.exe starts it restores the firewall rules that were saved at the previous shut down. In this way, even if some programs create new rules at system boot, before WFC being able to protect the rules, they are not effective because High Filtering is enabled. Block rules are applied over allow rules. When this feature is enabled, at system start-up the network connections are blocked until WFC (wfc.exe) starts too. It works fine on my test machines. Are there any other users for whom this is not working like described ?

http://www.wilderssecurity.com/threads/windows-firewall-control-4.347370/page-46#post-2420216

They didnt add this feature tell version before last and chances if your not useing Secure Boot something of yours may be leaking too. Thats even if it works right , Its vey new .

[Cortana]

I have followed to the letter all the steps, tried 2 times, but everytime i actually CAN get a 30 days trial key. Nothing is blocked there. But, once i insert the blacklisted key, and update it 'til today, everything seems ok (i use the 1035 key). Thought you'd find it maybe interesting. Thanks a lot for this new method for KIS.

I am sorry to break the bad news but there might be a problem in ur following the guide, if you are getting through the firewall and able to activate the trial key.

The step was specifically mentioned to ensure u have done all pin point, which is not the case in ur method.

I would suggest you to try again from absolute scratch.

Additional info like what OS ? what version of KIS u r using wud be helpful.....

[Cortana]

Secure boot feature has been there for quite a while on WFC, its just that they renamed it a few builds ago ;)

[wesh]

I have followed to the letter all the steps, tried 2 times, but everytime i actually CAN get a 30 days trial key. Nothing is blocked there. But, once i insert the blacklisted key, and update it 'til today, everything seems ok (i use the 1035 key). Thought you'd find it maybe interesting. Thanks a lot for this new method for KIS.

I am sorry to break the bad news but there might be a problem in ur following the guide, if you are getting through the firewall and able to activate the trial key.

The step was specifically mentioned to ensure u have done all pin point, which is not the case in ur method.

I would suggest you to try again from absolute scratch.

Additional info like what OS ? what version of KIS u r using wud be helpful.....

running win 8.1 x64 , KIS 2015 (v15.0.1.415) I did the steps many times, and believe me , i can still catch a trial key. But 1035 key remains UNBLOCKED.

I did another test in a VMware machine, same configurations, but this time i did not create any blocking rule for kaspersky. Of course , once i tried to insert the 1035 key, it was immediately blocked.

Conclusion : your method works 100% as for now, but i don't know why i can still get the trial key. I will try again, repeating the same steps and will report back

[Cortana]

running win 8.1 x64 , KIS 2015 (v15.0.1.415) I did the steps many times, and believe me , i can still catch a trial key. But 1035 key remains UNBLOCKED.

I did another test in a VMware machine, same configurations, but this time i did not create any blocking rule for kaspersky. Of course , once i tried to insert the 1035 key, it was immediately blocked.

Conclusion : your method works 100% as for now, but i don't know why i can still get the trial key. I will try again, repeating the same steps and will report back

The thing is if u r able to activate trial license, this means there is a leak.

And hence it would fail within 24hrs when it would make contact to this IP : 218.213.94.62

Thats why i said there is a problem in your follwing the guide.

If u want i could help u over team viewer

otherwise i will eagerly await for ur result.

p.s. just for having more grip block it in packet rules as well.

[dcs18]

@ one & all

Please do not enable the Secure Boot feature on your WFC - it is buggy and causes failure . . . . . . . . . . . . this was demonstrated to kantry123 in this TeamViewer session, post # 1392 (almost 10 days ago.)

During TeamViewing sessions, we also found that most of our members are unable to get their WFC configurations right - a tutorial was also proposed to be put up, but had to be aborted due to a lack of adequate response (post # 1496.)

[steven36]

Secure boot feature has been there for quite a while on WFC, its just that they renamed it a few builds ago ;)

Ok well for in instance with tu when I run WFC TU always wants to make new rules and TU got mad at it and unregistered me. Also all through the topic there's instances were members had trouble with it making rules they didn't want.

I've came up with a very simple solution with using just windows firewall were It cant add new rules or leak , a program that piggybacks off something is never no better than the source , because if was not for the source it uses it would not exist. More times than not a program that piggybacks off something just adds a new set of bugs to get in your way.

[Cortana]

Please do not enable the Secure Boot feature on your WFC - it is buggy and causes failure . . . . . . . . . . . . this was demonstrated to kantry123 in this TeamViewer session, post # 1392 (almost 10 days ago.)

i think it depends on system to system maybe.

Bcoz in my W8.1 it works flawlessly, apps cannot make contact with net until wfc.exe opens up. ESET shows up that it cannot update until WFC is started, so i say it is another way for me to prevent ESET from updating at startup

Also the latest version has worked on refining a few features, u may wanna give it a second chance.

edit : what type of failures one can experience ?

[dcs18]

Please do not enable the Secure Boot feature on your WFC - it is buggy and causes failure . . . . . . . . . . . . this was demonstrated to kantry123 in this TeamViewer session, post # 1392 (almost 10 days ago.)

i think it depends on system to system maybe.

Bcoz in my W8.1 it works flawlessly, apps cannot make contact with net until wfc.exe opens up. ESET shows up that it cannot update until WFC is started, so i say it is another way for me to prevent ESET from updating at startup

Also the latest version has worked on refining a few features, u may wanna give it a second chance.

edit : what type of failures one can experience ?

It screws up with UAC. ;)

[Cortana]

Again as dcs18 said , configuration is what matters most.

if configured correctly, WFC is easiest to work with.

If not, it can be a PITA.

[Cortana]

It screws up with UAC. ;)

have u experienced the same in ur sys ?

bcoz i have been using it(secure boot) and there is no problem with UAC...

[dcs18]

It screws up with UAC. ;)

have u experienced the same in ur sys ?

bcoz i have been using it(secure boot) and there is no problem with UAC...

On my system everything works like a dream - however, point to be noted is that UAC has always been left disabled on my system (I have a better alternative for UAC - ask kantry123.) :secret:

[Cortana]

On my system everything works like a dream - however, point to be noted is that UAC has always been left disabled on my system (I have a better alternative for UAC - ask kantry123.) :secret:

and on mine it works, even with UAC left to default settings.

So i guess, maybe a problem on W7 systems :dunno: