You can't help this for the first request. HTTP/NTLM authentication is based on the server sending a challenge (with the 401 response), and the client uses this challenge along with credential information to send a new request with authentication information.
Greg Reinacker Reinacker & Associates, Inc. http://www.rassoc.com -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of Thomas Have Sent: Tuesday, May 21, 2002 2:46 AM To: [EMAIL PROTECTED] Subject: More .Net/IIS tweaking. Hello. We have a client app that connects to an IIS-server (the client makes webrequests aswell as 'remotes' objects hosted by IIS. My problem seems the same in either case though). IIS is set up to use 'Integrated Windows authentication' for the VDir in question. But, according to the IIS-logfiles the client _first_ tries a Anonymous request (using W3C Extended format the 'cs-username' is '-' a dash), IIS replies 401 (unauthorized) then the client sends the login and then the request is successfull. This of course is a waste of bandwidth (we want to use IWA exclusively). Any ideas on how to eliminate this? On the client-side we have 'PreAuthenticate=true' and 'Credentials = CredentialCache.DefaultCredentials' (and similar things on the remoting request) on the webrequests but that doesn't cut it. Regards and TIA ThomasH You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
