David
Fri Apr 21 06:16:37 CDT 2006
I don't know what your special log format is supposed to mean.
HTTP Status 304 means "not modified" which means that the client already has
the content and actually serves it out of the client-side cache. I do not
see how that can lead to prompting for username/password when server already
return 304 and no authentication happened.
In other words, the information you gave does not corroborate what you
claim.
Since you are parsing through the log file and giving me what you think is
the error, I presume you know what you are doing and can troubleshoot your
issue without me.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Jonte@bson.se" <jonasberthelsson@hotmail.com> wrote in message
news:%23d0pzDvYGHA.4164@TK2MSFTNGP04.phx.gbl...
> ok here comes the IIS log entries
>
> GET 304
> GET 302
> GET 200 ok
>
> Under 304 and 302 the user get prompted for domain\user and the password
> and when she writes the password it work's fine.
>
> \\Jonas B
>
> "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
> news:%23VcTt9hWGHA.1204@TK2MSFTNGP04.phx.gbl...
>> Check the IIS logfile for the website and report the exact log entries
>> that correspond to these users getting prompted for logon. Start from
>> what is actually wrong and recorded in the log file, instead of guessing
>> at what could be wrong.
>>
>> --
>> //David
>> IIS
>>
http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>>
>> "Jonte@bson.se" <jonasberthelsson@hotmail.com> wrote in message
>> news:eVQSwGhWGHA.4652@TK2MSFTNGP04.phx.gbl...
>>> when they surf to our Intranet.
>>> We are running an IIS 5.x (w2k sp4 member server in a w2k3 sp1 AD in
>>> interim mode) in a Intranet envirement with Windows Integrety
>>> Authentification and now and then some users are prompted for logon with
>>> the IIS-server\username prefilled. If you then change to domain\username
>>> and put in the password it works fine for that session. The next time
>>> with a new session it's the same problem. They are logged on and can do
>>> other stuff as a domain user, so that should't be the issue.
>>> Often the soultion for us has been to give them a new profile but thats
>>> not so funny. The clients are Windows XP sp2 and are running IE 6.x. The
>>> "Enable Windows Integretaed Authentification" are on in the web browser.
>>>
>>> What's happening ?
>>>
>>> \\Jonas B
>>>
>>
>>
>
>