Problem with integrated IIS authentication on XP

Hi all,

I have the following constellation:

Windows 2003 Server with IIS and integrated windows authentication as
the only authentication method

When I request a page like http://myserver.com/file.html, it works fine
with a Windows 2000 client (on the server I can log the requesting
user, just the way it should be).

When I request the same page with the same user from a Windows XP
client, I get the requested content in the browser window AND a dialog
window which asks me to enter username and password

In the IIS logfile I can see that the Windows XP client generated three
requests, one without supplied credentials, the next one with them
(this can happen as the IIS tells the Internet Explorer to send the
same request again after the first one, but this time with
credentials), and the third request without credentials again.

The HTTP codes are 401 for request 1, 200 for request 2 and 401 again
for request 3.

I don't understand why there are three and not two requests, and I
don't know why the browser displays the required content AND the dialog
box as well.

I tried to enable / disable "use integrated windows authentication" in
Internet Explorer, but neither of the settings changed anything.

I really don't have a clue what might be wrong, any help is very
appreciated.

Best regards

Tim

.

Relevant Pages

  • Re: Where is the user impersonation token stored?
    ... Can you explain a little more with respect to IIS? ... User requests a restricted page and the Windows popup dialog appears so ... When an HTTP request is finished and the response is sent back to the client ... Where does IIS (or some ISAPI authentication filter/extension) get ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Where is the user impersonation token stored?
    ... It looks like this is an IIS question now. ... > bounces back a 401 to the client along with the possible authentication ... > header to the server on each request. ... >> 1) User requests a restricted page and the Windows popup dialog ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: HTTP 400 - Bad Request
    ... Windows Server 2003 comes with Network Monitor, ... none of those settings have ANYTHING to do with a 400 Bad Request. ... and IIS never bothered to execute it. ...
    (microsoft.public.inetserver.iis)
  • Re: Double Posting??
    ... The IIS logs list two entries for each page request. ... > Integrated Windows Authentication double the load on IIS? ...
    (microsoft.public.inetserver.iis)
  • RE: Password Protect Intranet Pages
    ... Using IIS console one can restrict access at various level, i.e. site, ... The client requests a resource on the server. ... The server, if configured to require it, will request authentication ... IIS checks if the user has a valid Windows user account. ...
    (microsoft.public.inetserver.iis.security)