Website troubleshooting in IIS

I put together this web site troubleshooting guide for a friend who was assisting on a project to deploy an iis based web application using Siteminder.

If there is more than one web server, stop IIS so that you can isolate and test web site on each node, to test web server one, stop iis on web server two.

Does the site browse with Siteminder agent disabled?

Does the site browse from a server/device on the same network (it’s not a proxy/routing issue)?

Does the site browse locally on the server with https

Does the site browse locally with just http

The objective should be to isolate each level of the web application. With this in mind we have to disable each layer until we get to a point where the site works and then start including the different components or layers of functionality.

Layer one – IIS starts, displays pages (with certificates as appropriate) and the site works.

Layer two – IIS works and the site is protected by Siteminder/SSO.

Layer three – IIS works with Siteminder/SSO protection and operates with load balancing.

This site uses Akismet to reduce spam. Learn how your comment data is processed.