Windows authentication doesn't work: 401.1

From: BRG (bigredgum1_at_excite.com)
Date: 07/05/05

  • Next message: Thiago Campos Pereira: "ASPNET X J2EE" 
    Date: 5 Jul 2005 07:05:05 -0700

    I'm having an issue getting Windows authentication to work on a couple
    of machines. The problem is that if I connect to a Windows
    authentication protected web page served by my local Windows XP
    machine, I get an HTTP 401.1 (Logon Failed) error. No Windows logon
    dialog appears at any time. Despite auditing for any security failures,
    nothing shows up in my security event log. For all other purposes,
    ASP.NET works fine.

    If I take my project (simple ASPX page + web.config) and copy it to
    another machine, it works great. My ASPX page prints out Context.User
    info, and "MACHINENAME\Administrator" appears.

    I am experiencing this issue on two Windows XP machines. On most other
    machines, Windows authentication works. Can anyone think of any
    machine-specific settings that would cause Windows authentication to
    fail?

    I'm just about at my wits end. Thanks in advance for any help you can
    provide.

    Settings:

    IIS: Integrated Windows Authentication enabled, all others (including
    anonymous) disabled
    Windows: Windows XP SP2, .NET 1.1 SP1, Guest account disabled

    web.config:

    <configuration>
      <system.web>
        <authentication mode="Windows" />
        <identity impersonate="true"/>
        <authorization>
            <allow roles="BUILTIN\Administrators"/>
            <deny users="*"/>
        </authorization>

        ... other default web.config settings ...

     </system.web>
    </configuration>

  • Next message: Thiago Campos Pereira: "ASPNET X J2EE"

    Relevant Pages

    • Re: Problems connecting to SQL server on W2K3 from Win 2000 workst
      ... Can you connect to a network share on the SQL server? ... Also I know this isn't as important on 2k machines but is the primary DNS ... >> This is because you are using Windows authentication without a domain ... >> because it tends not to work, use SQL Authentication and you'll always ...
      (microsoft.public.sqlserver.connect)
    • Re: Problems connecting to SQL server on W2K3 from Win 2000 workst
      ... The machines are in the same domain. ... "Mike Bulava" wrote: ... > This is because you are using Windows authentication without a domain setup. ...
      (microsoft.public.sqlserver.connect)
    • Re: Windows authentication doesnt work: 401.1
      ... I'm having an issue getting Windows authentication to work on a couple ... The problem is that if I connect to a Windows ... My ASPX page prints out Context.User ... I am experiencing this issue on two Windows XP machines. ...
      (microsoft.public.dotnet.framework.aspnet.security)
    • Re: Problems connecting to SQL server on W2K3 from Win 2000 workstatio
      ... This is because you are using Windows authentication without a domain setup. ... because it tends not to work, use SQL Authentication and you'll always ... > from windows XP machines. ... > to the server using the SA account and Named Pipes from a windows ...
      (microsoft.public.sqlserver.connect)
    • Re: ASP.NET on charge!
      ... application" option then just your DLLs and ASPX files will be copied along ... Ken Dopierala Jr. ... > 1) Which files of an ASP.NET project should I copy to the host server? ... the browser gives "windows authentication" error. ...
      (microsoft.public.dotnet.framework.aspnet)