For Failed Request Tracing to be helpful, you kind of want to know a little about what you are looking for. Event logs, or Failed Browser requests generally give you the Familiar 401, 404 or 500 error we have grown accustomed to. Unfortunately, sometimes we have to actially fix these issues. So here is the way to dig into those auth issues in a litte more understandible way.
1. Remove any proxy during this troubleshooting period
2. Ensure ports are open for smb to function
3. Remove the IIS policy from the Group Policy in the domain.
4. Make sure any DNS failures are addressed first. and the basic can i ping from here to there.
6. Turn on your failure request tracing
Here is how:
1. Open IIS manger
2. Click on the server object and select “add” on the right action pane
3. Select all
4. Select 401 to 500
5. Next , next finish
6. For the OME web site (I think it’s of the default web site), in other words the top level site for the directory, highlight and look at the center pane. You have to choose “failed request tracing from the center pane. Then you can see this message in the upper right action pane. You should see text to the effect of:
Now once you select this, you should be able to “enable” tracing for this level in the site
Once this is done, Try to do an update, or access the site in the way to recreate the failure.
The logs should be somewhere like C:\inetpub\logs\FailedReqLogFiles\
In this location you will see the lovely xml file with some more information on the auth failure.
My particular trace ended up looking like this with a nice credential failure and code for me to research if i didnt know that the security package i sent had an issue: