<div>
Then I must be missing something. &nbsp;I don't see any way to select more than a single protocol/port per policy or create a custom protocol object that includes more than 1 port? &nbsp; Is it &quot;secondary connections&quot; maybe? 
</div>


Then I must be missing something.  I don't see any way to select more than a single protocol/port per policy or create a custom protocol object that includes more than 1 port?   Is it "secondary connections" maybe?

<div>
Please let me know, is it a web publishing rule or allowing protocols?? Please explain a bit.
</div>


Please let me know, is it a web publishing rule or allowing protocols?? Please explain a bit.

<div>
@araberuni the OP is obviously talking about server publishing rules and he is right he will need to create 5 rules as I said earlier
</div>


@araberuni the OP is obviously talking about server publishing rules and he is right he will need to create 5 rules as I said earlier

<div>
<div class="content wysiwyg-content">
Am I missing something or do you really need to create a separate policy for every port you want to allow? &nbsp;For example, if I want to allow ports 80, 443, 1207, 8080 and 15000 to specific internal server, do I really need to create 5 policies? &nbsp;This would get messy really quick for a large number of servers/policies. &nbsp;
</div>
</div>


Am I missing something or do you really need to create a separate policy for every port you want to allow?  For example, if I want to allow ports 80, 443, 1207, 8080 and 15000 to specific internal server, do I really need to create 5 policies?  This would get messy really quick for a large number of servers/policies.  

ISA/TMG Firewall policy with multiple allowed ports?

Microsoft Forefront, formerly known as Internet Security and Acceleration Server (ISA Server), is a network router, firewall, antivirus program, VPN server and web cache that runs on Windows servers. It includes identity management and protection systems, and discontinued systems for threat management and network protection, along with protection for Sharepoint and Exchange. The scope of discussions includes forward and reverse proxy, application and service publishing, virtual private networks (VPNs), outbound access rules, SSL certificates and network routing within either a single node or an highly-available array pairing.