Hi guys
I can't seem to figure this out..
say I have software.exe
I would like to setup the custom Windows Firewall policy:
ALLOW ALL INBOUND and OUTBOUND CONNECTIONS
-> Except OUTBOUND to IP ADDRESS XXXX
So what i did was
1) CREATE INBOUND RULE = ALLOW from ANY IP ADDRESSES
2) CREATE OUTBOUND RULE = DENY connection TO x.xx.xx IP ADDRESS
at this point things seem to be setup right..
Except that I need to explicitly tell Windows to allow OUTBOUND to ANY IP ADDRESS as well to prevent the Firewall notification "Allow connection?" etc
so a 3rd rule comes into play
3) CREATE OUBOUND RULE = ALLOW to ANY IP ADDRESS
My problem is that this conflicts with RULE #2 .. basically Rule #3 takes over and software.exe is allowed to connect to any IP ADDRESS (the desired BLOCK of the specific IP Address doesn't work)
I know I should just use a 3rd party firewall w/ better RULE HANDLING but I wanted to keep things lite weight and use built in firewall.
I hope this is possible..
Tnx guys
I can't seem to figure this out..
say I have software.exe
I would like to setup the custom Windows Firewall policy:
ALLOW ALL INBOUND and OUTBOUND CONNECTIONS
-> Except OUTBOUND to IP ADDRESS XXXX
So what i did was
1) CREATE INBOUND RULE = ALLOW from ANY IP ADDRESSES
2) CREATE OUTBOUND RULE = DENY connection TO x.xx.xx IP ADDRESS
at this point things seem to be setup right..
Except that I need to explicitly tell Windows to allow OUTBOUND to ANY IP ADDRESS as well to prevent the Firewall notification "Allow connection?" etc
so a 3rd rule comes into play
3) CREATE OUBOUND RULE = ALLOW to ANY IP ADDRESS
My problem is that this conflicts with RULE #2 .. basically Rule #3 takes over and software.exe is allowed to connect to any IP ADDRESS (the desired BLOCK of the specific IP Address doesn't work)
I know I should just use a 3rd party firewall w/ better RULE HANDLING but I wanted to keep things lite weight and use built in firewall.
I hope this is possible..
Tnx guys