Windows client damage authorization header (Kerberos) => IIS 400 (Bad Request)
We are facing strange behavior on about 5% of Windows (7 Pro and XP Pro, both 32 and 64 bits) client computers. These computers gets randomly error from IIS server - 400 Bad request. We are using...
View ArticleWindows client damage authorization header (Kerberos) => IIS 400 (Bad Request)
What are the server OS and what is your AD environment ? does it include 2003 and 2012 R2 Dcs?
View ArticleWindows client damage authorization header (Kerberos) => IIS 400 (Bad Request)
We do not have Windows 2003 Servers any more. Functional level of our domain is 2008 R2. IIS is running on Windows Server 2008 R2 and 2012 R2.
View ArticleWindows client damage authorization header (Kerberos) => IIS 400 (Bad Request)
Have you changed the MaxTokenSize on ALL devices to 48000 ? (Client and server)
View ArticleWindows client damage authorization header (Kerberos) => IIS 400 (Bad Request)
Thanks for your interest. Sure MaxTokenSize is changed by "Default Domain Policy". Checked that it is applied ... But that is not the issue. Client with bigger TGT is logged on the computer. All other...
View ArticleWindows client damage authorization header (Kerberos) => IIS 400 (Bad Request)
I`m on the trail. Seems that it.is.caused by Eset NOD32 Antivirus. I will confirm it after tests next week.
View ArticleWindows client damage authorization header (Kerberos) => IIS 400 (Bad Request)
Solved. Eset NOD32 Antivirus version 4 was modifying HTML authorization headers on some computers. After disabling Web access protection everything works like a charm.
View ArticleWindows client damage authorization header (Kerberos) => IIS 400 (Bad Request)
Hello,ESET NOD32 Antivirus 4 Business Edition is a pretty old. As a matter of fact, it was replaced with ESET Endpoint Antivirus several years ago. Is there a particular reason you haven't upgraded...
View Article
