IIS Application Request Routing

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.
Bill HindDirectorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Michael B. SmithExchange & Active Directory ExpertCommented:
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.
Bill HindDirectorAuthor 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!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Michael B. SmithExchange & Active Directory ExpertCommented:
You accepted your own comment as the solution? Geez.


Regardless, request filtering may indicate that you are filtering based on IP.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Remote Access

From novice to tech pro — start learning today.