I have a customer that wants to run our web application through
BorderManager Proxy Server. The customer cannot get the web
application to
run through our designated non-standard port. We have other web
applications that they can run because the default ports 80 or 443 are
being
used.



We require ports 80, 443 and a designated non-standard port to be
open. We
use multiple servers, which are being load balanced to run the web
applications. Most customers are given the IP range of the web site's
server
farm, port, and TCP protocol, which is enough to open the traffic
through
the designated port setting up a filter exception or an entry in the
Access
Rules list.



The Customers comments: We use a proxy to get through our firewall.
Ports
80 and 443 are no problem for the software. In order to proxy a
non-standard port, I need to know a destination IP, not a range, but a

specific IP is what the proxy setup is asking for.



The web sites URL public IP is the only IP that is not behind the
firewall.
When we load balanced multiple servers that are being used to run the
web
applications, which are behind the firewall.



Why do they say they need to use a specific IP address instead of
using a
designated range of IP addresses to open a non-standard port?



Bob