Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
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
.
Forums
Software
Security Apps
Other security for Windows, Mac, Linux
Binisoft WFC problem
Message
<blockquote data-quote="n8chavez" data-source="post: 984476" data-attributes="member: 90863"><p>Ok. I think I really have the solution this time. I thought the solution was the profile type. That was not the case. After I rebooted my issue was still there, even with the profiler change. But, as <a href="https://www.wilderssecurity.com/members/117366/" target="_blank">@alexandrud</a> said, sometimes the allow rules don't work like they're supposed to. This was the case here. The allow rules, allow generically set, didn't work. I created 4 allow rules, UPD in/out and TCP in/out, and now destiny 2 work on the private profile.</p></blockquote><p></p>
[QUOTE="n8chavez, post: 984476, member: 90863"] Ok. I think I really have the solution this time. I thought the solution was the profile type. That was not the case. After I rebooted my issue was still there, even with the profiler change. But, as [URL='https://www.wilderssecurity.com/members/117366/']@alexandrud[/URL] said, sometimes the allow rules don't work like they're supposed to. This was the case here. The allow rules, allow generically set, didn't work. I created 4 allow rules, UPD in/out and TCP in/out, and now destiny 2 work on the private profile. [/QUOTE]
Insert quotes…
Verification
Post reply
Top