IIS Application Request Routing

Bill Hind
Bill Hind used Ask the Experts™
on
Hi, I have set up server 2016 with IIS Application Request Routing, (about 3 weeks ago) to enable sharing one internet connection for port 443, between a Remote Web Access server and an exchange 2013 server. The connection was working perfectly until this morning. Remote access on 443 fails to both servers. The setup was with different FQDNs and the appropriate certificates.

I cannot find any instructions to troubleshoot this type of setup there are articles on load balancing Exchange servers but nothing for this, I'm not even able to find out where the configuration can be accessed to see if something has changed.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Michael B. SmithManaging Consultant

Commented:
Perhaps a stupid question - but did you reboot the ARR server? I have a client where ARR sometimes just decides to stop working. A reboot fixes it right up.

ARR is configured right within IIS Admin Console. Open the console, click on the server name in the selection pane (the left pane) and in the working pane (center pane) you'll see entries for Application Request Routing, HTTP Redirect, Request Filtering, and URL Rewrite - all are the pieces that give ARR.
Director
Commented:
Thanks Michael,

 Not a stupid question but yes, I had restarted the server. That may have been causing the initial issue because there were a number of errors being logged which disappeared after a restart. I was not able to logon after the restart, which lead me to believe that the restart had not fixed the issue, whereas in fact it had, I spent ages looking for issues which were not there.

The information on the entries for ARR was very useful as I was not able to find anywhere what were the ARR entries.


The issue turned out to be: I have moved and there is an issue connecting my computers with that ARR site. I have yet to diagnose what is causing that issue but I suspect it might be ISP related! Strange that connection on port 443 should be interfered with!
Michael B. SmithManaging Consultant

Commented:
You accepted your own comment as the solution? Geez.

smdh

Regardless, request filtering may indicate that you are filtering based on IP.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial