Completely stumped at this one. We've got an internal web server accessed by users for a variety of sites. One of those requires Windows Authentication the site is http://caf. ("caf" is an A record in DNS in our domain)
The server itself is set up for Windows Authentication:
And the site is set up like this:
Believe me, every permutation of the provider order, extended protection, and kerberos switch have been tried over the past few days of debugging.
After repeated prompting for name/password, the error that comes back is 401 Unauthorized. The name and password are correct, have not been locked out, are being presented with the domain name, etc..
I turned on failed request tracing, and this is what comes out of it:
Detail here, but I've omitted some for brevity:
...
...
Can anyone shed some light on what's going on here? Perhaps suggest a remedy?