IIS 7 and Above
Application Request Routing (ARR)
ARR load balance can't be reached
Last post Mar 13, 2018 07:02 AM by Yuk Ding
Mar 12, 2018 04:23 PM|suchanewbee|LINK
I just deployed the load balance with application request routing. But I can't reach the backend server after I finish configuring the LB. I just create the Server farm and added the backend server to it. The health check could be passed and monitoring and
management show the server is health and availlable. However, when I access the website, it return site can't be reached. I can access the backend server from ARR server. I can also access the front-end website from external. How can I fix this? Thanks in
Mar 12, 2018 05:42 PM|Rovastar|LINK
You need to establish whether the external traffic is
a) hitting your ARR server. e.g. does the correct info appear in the ARR IIS logs.
If that is ok then
b) Are the correct rewrite rules used to redirect the traffic to the correct farm.
Failed request tracing is useful for this:
if that is all ok then
c) Look at your backend servers to make sure you are receiving traffic to the correct place there. e.g. check you various IIS logs, http.sys logs, etc to see if you see the traffic hitting those servers.
Or use things like wireshark to view explicitly the traffic hotting the boxes.
Mar 13, 2018 07:02 AM|Yuk Ding|LINK
This is how I configure the ARR load balance.
1)I have two internal server A: 192.168.2.50,B:192.168.2.51
I set the A‘s binding to www.mydomain.com 192.168.2.50
2)I set B's binding to null binding 192.168.2 51
3)I Add the backend server 192.168.2.51 to serverA's farm and create the routing rule.
4)I test the health test and try to access the website
5)The load balance start working.