We have a Webserver that need access to our SQL server, so I have added a Data Filter to allow traffic from our webserver to our SQL server.

So I created the following rules:
WAN > LAN, Source Webserver, Destination SQL Server, Service UDP /TCP Any port to 1433, Action Allow and a 2nd rule to block.
WAN > LAN, Source Any, Destination SQL server, Service UDP /TCP Any to 1433, Action Block.

I am able to connect to the SQL server from other IP's than the Webserver. So I thought perhaps I have done it wrong, (I had added the rules to call not data) so changed the rules and still nothing, so I then created a rule so SQL was blocked. I am still able to connect to the SQL Server

I have also added a new rule to block SMTP out from our network:

LAN > WAN, Source DHCP range, Destination Any, Service UDP /TCP Any to 25, Action Block

none of the filters seem to be applied no matter how I link or call the filter sets. Any idea's as to why?

Thanks

Hi I think you're close.

What about setting the first rule for your websql as WAN > LAN, Source Any, Destination SQL server, Service UDP /TCP Any to 1433, Action Block If No Further Match.
Then the next rule as: WAN > LAN, Source Webserver, Destination SQL Server, Service UDP /TCP Any port to 1433 Pass Immediately

Does that fix it for you?

Regards,

Neal

It all looks right but make sure that the filter set you've put those rules in is linked from the #2 Default Data Filter? If you haven't already then set the Next Filter Set option in the bottom right so they link up.