IWA not working

16 May 2006 3:07 PM

Ishmealm

I recently upgraded to IIS 6. In the past we haven't used Intergrated
Windows Authenication, but I thought that it would be nice to start using
that instead of Basic Authenication w\ SSL. For some reason it doesn't work.
I get prompted for a username\password even when I use IE (v6 SP2) when I
enter my username password, I get in. I was wondering if there are any
special rights that I need to grant at the machine or folder level to get it
to work. Or if our site setup is causing some sort of naming problems. All
of our traffic is intranet trafic, but from several different domains.

Our setup is:
machine name-   webserver-01
site name-          example.site.com
url-                    http://example.site.com/testperm/test.html

Thanks!

16 May 2006 3:49 PM

Miha Pihler [MVP]

Hi,

IWA only works on sites that are in Local Intranet Zone (This is IE
setting). By default this would be sites named http://example but not e.g.
http://example.domain.com or http://10.10.10.10. If you want for IWA to work
on sites named e.g. http://example.domain.com you have to make sure that
this URL is in Local Intranet Zone and not e.g. Internet zone (by default).

I hope this helps,

--
Mike
Microsoft MVP - Windows Security

Show quoteHide quote

"Ishmealm" <Ishme***@discussions.microsoft.com> wrote in message
news:3F0E0B47-CD34-4442-8113-08B7744FCC48@microsoft.com...
>I recently upgraded to IIS 6. In the past we haven't used Intergrated
> Windows Authenication, but I thought that it would be nice to start using
> that instead of Basic Authenication w\ SSL. For some reason it doesn't
> work.
> I get prompted for a username\password even when I use IE (v6 SP2) when I
> enter my username password, I get in. I was wondering if there are any
> special rights that I need to grant at the machine or folder level to get
> it
> to work. Or if our site setup is causing some sort of naming problems.
> All
> of our traffic is intranet trafic, but from several different domains.
>
> Our setup is:
> machine name-   webserver-01
> site name-          example.site.com
> url-                    http://example.site.com/testperm/test.html
>
> Thanks!
>

18 May 2006 1:35 PM

Ishmealm

Thanks Mike!

Show quoteHide quote

"Miha Pihler [MVP]" wrote:

> Hi,
>
> IWA only works on sites that are in Local Intranet Zone (This is IE
> setting). By default this would be sites named http://example but not e.g.
> http://example.domain.com or http://10.10.10.10. If you want for IWA to work
> on sites named e.g. http://example.domain.com you have to make sure that
> this URL is in Local Intranet Zone and not e.g. Internet zone (by default).
>
> I hope this helps,
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "Ishmealm" <Ishme***@discussions.microsoft.com> wrote in message
> news:3F0E0B47-CD34-4442-8113-08B7744FCC48@microsoft.com...
> >I recently upgraded to IIS 6. In the past we haven't used Intergrated
> > Windows Authenication, but I thought that it would be nice to start using
> > that instead of Basic Authenication w\ SSL. For some reason it doesn't
> > work.
> > I get prompted for a username\password even when I use IE (v6 SP2) when I
> > enter my username password, I get in. I was wondering if there are any
> > special rights that I need to grant at the machine or folder level to get
> > it
> > to work. Or if our site setup is causing some sort of naming problems.
> > All
> > of our traffic is intranet trafic, but from several different domains.
> >
> > Our setup is:
> > machine name-   webserver-01
> > site name-          example.site.com
> > url-                    http://example.site.com/testperm/test.html
> >
> > Thanks!
> >
>
>
>