Re: IIS and Integrated Windows Authentication

From: Viperlein (Viperlein_at_discussions.microsoft.com)
Date: 11/11/04 

Date: Thu, 11 Nov 2004 08:54:02 -0800

Hmmm, thanks.

But why does this not happen to ALL people, but only a few with their
certain profile.
How can this be profile related ? In the company each one has the same
installation and updates. Some have more software than others. But in the
end, the browser configuration is the same to all.
I thought if I activate "Integrated WIndows Authentication", the login of
the user is used automatically and all the rights for drives and so on are
taken from the Active Directory, as it is for all who do not get the error ?

"Miha Pihler" wrote:

> Hi,
>
> You will always get authentication failed on a website that is not
> accessible anonymously. This is "caused" by web browser (any of them) trying
> to access site anonymously (browser can't know beforehand that site is
> protected). Once the site returns "authentication failed" it will return
> list of authentication options that it will support (e.g. IA, Basic, ...).
>
> INFO: How IIS Authenticates Browser Clients
> http://support.microsoft.com/default.aspx?scid=kb;en-us;264921
>
> Mike
>
> "Viperlein" <Viperlein@discussions.microsoft.com> wrote in message
> news:6BC95DC9-1E4F-4DCE-B6DE-CE2B17CA9DF3@microsoft.com...
> > Hello @ll :)
> >
> > We have a problem with our ASP.NET application and the IIS in our company:
> >
> > As soon as you disable the "Anonymous access" and use the integrated
> > Windows
> > Authentication, some users (it is only XP-profile dependant, not PC
> > dependant
> > !) receive a "Bad Request" when calling the startpage. If you look closely
> > at
> > the communication with a sniffer, there you see an "authentication failed"
> > error before receiving the "Bad request" one.
> >
> > I also made a simple ASP.NET page with an asp-button on it without any
> > functionality and the same settings for the IIS. And guess what ????
> > The error also appears !
> >
> > So no problem with our program.
> >
> > We have no idea what to do any further ............
> > Any ideas would be welcome !
> >
> > Thank you all for your support !
> >
> > Christian
>
>
>

Relevant Pages

  • Re: Authentication Issues
    ... | I've have turned on Integrated Windows Authentication for my entire site. ... Your browser may be configured to always ask the user for credentials regardless of the IIS authentication method requested. ...
    (microsoft.public.inetserver.iis.security)
  • Re: Substituting new Context.User.Identity for Authentication in SPS 2003
    ... MS SharePoint Portal Server does not perform authentication. ... MS SPS does perform authorization based on a Windows account presented ... Since SPS is accessed via a browser, ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: Soymail not working with WASD
    ... A 404 can also indicate the server account does not have permission to access the file entry in the parent directory and therefore does not 'see' it during the directory search. ... Once authentication is going I suspect we may be back to analysing the originally reported 404 error. ... WATCH is a tool that if it doesn't indicate exactly the reason for any given server behaviour usually provides a very good hint. ... which should provide you with a browser username/password dialog box requesting authentication for "SKELKEY". ...
    (comp.os.vms)
  • Re: ASP and NTFS
    ... If you are using a HTTP based authentication mechanism (eg NTLM, Basic, ... then the browser needs to send the appropriate credentials in ... > be able to redirect with the user name and password they already ...
    (microsoft.public.inetserver.iis.security)
  • Re: Windows Integrated and the domain name
    ... Both NTLM and Kerberos authentication require the full realm and username - that's unfortunately the way both of those two protocols work. ... for a direct integrated windows authentication ... Microsoft Online Community Support ...
    (microsoft.public.inetserver.iis.security)