Jetico Personal Firewall vs Privatefirewall (vs Simplewall vs Windows Firewall Control)

Hmm... I tried to do that but I couldn't - will try again.

Oh, I see... I was expecting something more, like, for example, more detailed messages.

Well, your posts are among these which helped me a lot to start. Also, I have some programing background and Jetico has many things that can be compared to logical statements so I really enjoy that part. In future, if I find some spare time then I maybe try to prepare some "better starting template" for new users, but I need to solve the problems I descibed in question 10 or it won't make much sense.

 

I think I'm ok with Process attack rules and other tables but I still have some problems with connectivity. I'm not sure how to do a proper set up of "IP address" groups (these which are used later by JPW in default rules) - how to correctly fill these groups with IP addresses (and what's the proper IP notation to use here) to allow basic communication with servers.

But do you maybe still have your old configuration file and could show me the content of your "IP address" groups? For example, what should be in Trusted Zone, local network groups? What's the difference between Local Area Connection and Local Area Connection LAN and what are they for?

It seems that my PC has some problem with changing named addresses to IP - so it is some problem with DHCP/DNS but I can't see anything wrong in my rules. My DHCP/DNS/gateway IP address is the same and this is the router I'm connected to (it is not my own router, I'm plugging my cable to the socket in the wall). It's not the problem of the router for sure, as when I'm not running Jetico all seems to be fine.

I've noticed one more thing - just after PC restart IP address groups are auto-filled with default values - at this time my connection works (if I use numbered IP adresses). After some time these values are dropped and connection stops...

Doesn't Jetico somehow disable windows in-build firewall when running? I'm asking because windows in-build firewall says it's "on".

 

Update: It seems there was "some fault" in indirect network access table...
The funny thing is: I have all rules on "accept" here.
My problems ended after some "nonsignificant" changes in order of the rules... sigh.

But my last question still remains valid: shouldn't Jetico turn off Windows build-in firewall?
Or I need to do this manually? Or maybe it is not needed at all?

 

Hi Lexor,

sorry, it's harder to help out now that I don't have it installed. No, Jetico will not disable Windows firewall, and it's something you'll want to do so there're no conflicts. I created my own IP address Groups for certain programs. One such group was for svchost.exe - wuauserv.exe service, where I restrict the Windows update service to specific Microsoft/Akamai update servers:

Code:

 <group name="Microsoft Updates Servers" comment="">
            <item value="4.27.0.0/16" />
            <item value="8.12.0.0/16" />
            <item value="8.254.0.0/16" />
            <item value="13.107.0.0/16" />
            <item value="64.18.0.0/16" />
            <item value="64.145.0.0/16" />
            <item value="64.208.0.0/16" />
            <item value="65.54.0.0/16" />
            <item value="65.55.0.0/16" />
            <item value="69.16.0.0/16" />
            <item value="69.22.0.0/16" />
            <item value="72.246.0.0/16" />
            <item value="92.242.0.0/16" />
            <item value="107.14.0.0/16" />
            <item value="128.242.0.0/16" />
            <item value="134.170.0.0/16" />
            <item value="151.139.0.0/16" />
            <item value="157.55.0.0/16" />
            <item value="157.56.0.0/16" />
            <item value="165.254.0.0/16" />
            <item value="172.217.0.0/16" />
            <item value="173.245.0.0/16" />
            <item value="191.232.0.0/16" />
            <item value="191.234.0.0/16" />
            <item value="194.7.0.0/16" />
            <item value="198.78.0.0/16" />
            <item value="199.7.0.0/16" />
            <item value="204.160.0.0/16" />
            <item value="204.191.0.0/16" />
            <item value="204.245.0.0/16" />
            <item value="205.250.0.0/16" />
            <item value="206.108.0.0/16" />
            <item value="207.34.0.0/16" />
            <item value="207.228.0.0/16" />
            <item value="208.38.0.0/16" />
            <item value="b00:2048:1::681c:1138/128" />
            <item value="2606:2800:11f:85d:13e0:11e9:1a6:201d/128" />
            <item value="2a01:111:2003::50/128" />
            <item value="93.184.0.0/16" />
            <item value="64.4.0.0/16" />
            <item value="67.131.0.0/16" />
            <item value="216.58.0.0/16" />
            <item value="23.103.0.0/16" />
            <item value="23.73.0.0/16" />
            <item value="23.54.0.0/16" />
            <item value="104.80.0.0/16" />
            <item value="66.119.0.0/16" />
            <item value="8.253.0.0/16" />
        </group>

Notice I use CIDR masks to help cover the vast range of server IP's MS uses. Also remember to enable logging for rules and filters that seem to be giving you problems, so thiat you can easily track down and resolve network connection or Process interaction rules. The Default rules are something you'll just have to analyze to see if they need modifying, if additional rules are required or if there are rules you feel can be removed.