Look ‘n’ Stop Application Filtering disadvantages 1) The incapability to backup and re-apply 2) Incapability to specify a port to address. Benefits to specify port to address; - Passive FTP issues - Application: Windows Explorer - - Ports And IP address selection – TCP - Ports: 443 - @ IP: 18.104.22.168 Now if I were to use Internet Explorer with Passive FTP setup, Windows Explorer on XP is seen making TCP initiating connection to FTP server via port 21. Not a problem, add port 21 to the TCP Ports field, now I try to download file off of FTP server, whoops blocking! Reason; the specified IP for port 443 is at fault, have two options, keep manually adding FTP server IP addresses all throughout the days or empty the “@ IP:” field. Since manually adding/removing FTP server address to the list is out of the question, so empty the IP field it’ll have to be, but now Windows Explorer can connect to any legit or not IP addresses through TCP ports 443 and 21. Done? Wait a minute! Trying to download off of FTP server I see further blockings, what? Reason; Temp range TCP ports usage for Passive FTP data connections, what does this mean? Back to modifying for applications “Ports And IP address selection”, add 1024-5000 to the TCP ports list s required. Now what do we have here? Windows Explorer being capable of use to make TCP initiating connections to any remote machine through ports 21, 443, and 1024-5000. And now I’m asking myself what is the point to even bother using “Ports And IP address selection” feature? I’m experiencing these problems with a lot of things I run….