Quantcast
Channel: Forefront Edge Security – DirectAccess, UAG and IAG フォーラム
Viewing all articles
Browse latest Browse all 1485

Unable to get a web application (portal hostname) farm to work.

$
0
0

I have a pair of tomcat apache web servers that I am trying to publish via the UAG.

I have a separate trunk for this application and the portal page and authentication are disabled on the trunk. The UAG is just passing users through straight to this application.

I can publish the application without any issues to a single server (configure an application server) via the other web application (portal hostname) in the add application wizard.

However I am unable to get the 'configure a farm of application servers' to work when publishing via the other web application (portal hostname) in the add application wizard.

If I use the default HTTP GET health checking I get the error message 'You cannot access this site because there is no Web farm server available' which makes sense as the website only accepts HTTPS. If I change the health checking to ping, I get the error message 'You are not authorized to access this website' even though authorization is set to all users.

Like the single application server, I am using DNS names under the addresses tab, paths is set to / and HTTP port is removed. I am not using the farm name in the HTTP host header and am balancing the request with cookie-based affinity.


Viewing all articles
Browse latest Browse all 1485

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>