Menu
Forums
New posts
News feed
Latest activity
Search forums
News
Security News
Technology News
Hardware News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
MalwareTips Giveaways
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Malware Hub
Malware Samples
Statistics and Reports
Blogs
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Forums
Software
General Software
Performance & Health
Hard_Configurator - Windows Hardening Configurator
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Andy Ful" data-source="post: 910728" data-attributes="member: 32260"><p>Anyway, it is easy to check if FirewallHardening is involved. <strong>Just remove all entries from the Blocklist and restart the computer.</strong> Next, use the FirewallHardening Log to see if these svchost related blocks disappeared. FirewallHardening does not do anything else than adding/removing firewall rules. No rules, no blocking by FirewallHardening.</p><p>The Log shows all blocked outbound connections visible to Windows Firewall, no matter if FirewallHardening blocks something or not.</p><p></p><p>Edit.</p><p>I think that some outbound connections can be blocked without Windows Firewall rules, for example by the router. Such events will be also visible in the Log, because the packets are not sent.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 910728, member: 32260"] Anyway, it is easy to check if FirewallHardening is involved. [B]Just remove all entries from the Blocklist and restart the computer.[/B] Next, use the FirewallHardening Log to see if these svchost related blocks disappeared. FirewallHardening does not do anything else than adding/removing firewall rules. No rules, no blocking by FirewallHardening. The Log shows all blocked outbound connections visible to Windows Firewall, no matter if FirewallHardening blocks something or not. Edit. I think that some outbound connections can be blocked without Windows Firewall rules, for example by the router. Such events will be also visible in the Log, because the packets are not sent. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
