Bad Request (Request Header Too Long)

Recently we just upgraded our Windows 2003 Server Box to SQL 2005 from SQL 2000. Not only does this server have SQL on it, but it also runs IIS 6, hosting our ASP.net applications. We currently use ASP1.1 applications, but we have the framework for 2.0 installed on our server and some workstations. Recently, on two administrator workstations one of our apps will not work after the first click on the page. It gives us a Bad Request (Request Header Too Long) error message. However on all the other PC's it works just fine. We are using integrated Windows Authentication because the application requires obtaining the groups the user belongs to. It authenticates fine-- the user name is displayed-- but when the user clicks a link the error is thrown. I have tried repairing 2.0 framework, with no success. Also, when the server's IP address is typed in instead of its name, it works after being prompted for the user name and password. Any ideas?

After a day's worth of diagnostics, I found the problem to be with non persistant cookies. According to Microsoft's site IIS can only handle headers that are 16KB, otherwise it rejects it. Non-persistant cookies are stored in the header, which exceeded 16KB. Microsoft has a solution to increase the size limitation of the header. However, this can be a security concern, so I rewrote the app and all is well.

Thanks for posting your solution!

No Problem-- I figured I can't be the only one who runs into this problem. By the way the HTTP Analyzer I used was IEInspector's HTTP Analyzer

may we have the fix that microsoft has for this? I canno't find it. Thanks in advance