IIS 7 and Above
ARR ip address to load pages, only loads from one server on network b...
Last post Apr 08, 2018 06:10 AM by carrzkiss
Mar 30, 2018 12:46 PM|carrzkiss|LINK
(Win16 Server installed on VMWare. 3 servers running Win16-VM for this test scenario setup for learning and teaching)
OK. I am finally getting around to learning how to work the farm.
I have everything installed, IIS, ARR, NLB, DFS, etc...
Everything seems to be going great, except for the loading pages from different servers from domain.com on the network.
Works great when you load the site on the ARR Server itself, But not on the network.
.89 and .93
.89 is the primary web server.
.93 is the secondary web server.
ARR Server, IP Address for NIC is .110
IP Address for the ARR Side is 109
When I type in domain.com/info.asp on the ARR Server, the page changes from 89 to 93 when refreshed.
But, on the network, when I load the page and refresh.
I only get the .89 feed.
I refresh the page, I still on get the .89 page and not the .93 page.
When I disable the .89 site the domain.com page running on the ARR server will load the correct page.
However, when I load the domain.com on a network computer it loads the error page [Service Unavailable]
Any ideas on why this would be happening?
Apr 02, 2018 12:22 AM|Rovastar|LINK
Apr 02, 2018 08:55 AM|Yuk Ding|LINK
What weight did you set for secondary server. The 503 service unavailable sounds like an ARR front-end issue while if the backend server stop working, it should return 502 bad gateway. Secondly, are you sure the application is completely the same? How did
you set the binding host header for the backend server?
Secondly, please check whether the application pool is still running. The frequent error may stop application pool and return service unavailable.
Maybe you could enable the failed request tracing to check what's going on when the request is relayed to .93 server.
Apr 05, 2018 09:18 AM|carrzkiss|LINK
I had the Affinity set but disabled it.
>> What weight did you set for the secondary server
Are you referring to the [Load Balance in IIS?]
[Weighted round robin] / [even distribution]
I have the front-end BINDING and the Back-end BINDING
All the same. except for the IP Address, of which the Front-End has it assigned, the back-ends are set as [All Unassigned]
If I set the same IP Address, I get a 404 error.
The strange part is.
When I test the site on the local ARR server, it works.
I refresh the page, it shows the [503 error], I then refresh the page again, and it picks up on the other server.
When I test the site on an external network machine, it does not work, when I pull a system down. (I stop the App Pool for the site, to test)
It shows the [503 error] no matter how many times I refresh the page.
So, it works on the ARR Server, but not on any other machine on the network. Until I enable the App Pool again, and it all goes back to working.
Any ideas on this one?
Apr 06, 2018 05:06 AM|carrzkiss|LINK
I made a video demonstrating this issue. Hopefully, someone can look at it, and pinpoint exactly what is going on here.
Apr 08, 2018 06:10 AM|carrzkiss|LINK
The issue is resolved, or more than less, the non-issue was resolved.
When testing the ARR to make sure everything is working properly from outside of the server. (Other computers in the network to load the webpage) do not stop the app pool for the site.
Instead, go into the Web Server itself, and use the NLB, and stop the Web-1 and test, then start, and then the Web-2 and test, and then start.
So, this issue is resolved, thank goodness.
Now time to test other things like the SQL Server Failover to make sure it works as expected.