Home All Groups Group Topic Archive Search About

Problem with IIS windows authentication

Author
13 Aug 2006 2:52 PM
jakeh11
We are having problems with windows authentication in IIS on one of our
domain controllers. Here's what we have done: We have setup a test
virtual directory in the default web site to D:\WebSites\WebSiteA,
disabled anonymous access and enabled windows authentication.
Everything works fine. But, if we create a new website or virtual
directory on a different web site, we get prompted for credentials. I
am not sure what I am doing wrong.

Author
13 Aug 2006 6:39 PM
Roger Abell [MVP]
<jake***@gmail.com> wrote in message
news:1155480734.724891.200740@75g2000cwc.googlegroups.com...
> We are having problems with windows authentication in IIS on one of our
> domain controllers. Here's what we have done: We have setup a test
> virtual directory in the default web site to D:\WebSites\WebSiteA,
> disabled anonymous access and enabled windows authentication.
> Everything works fine. But, if we create a new website or virtual
> directory on a different web site, we get prompted for credentials. I
> am not sure what I am doing wrong.
>

It sounds as if you have not set the NTFS permissions as needed on the
storage used for the new website or vdir.
Author
13 Aug 2006 11:49 PM
jakeh11
Thank you for your response. That was not the problem, but I think I
found it. I have been using the FQDN to access it (eg.
http://server_name.company.com/) but when I used http://server_name/ it
worked fine. I don't know why I did not think of it before.
Author
14 Aug 2006 2:48 AM
Bernard Cheah [MVP]
This is because IE doesn't not auto authenticate in FQDN url.. read
Intranet site is identified as an Internet site when you use an FQDN or an
IP address
http://support.microsoft.com/?id=303650

--
Regards,
Bernard Cheah
http://www.iis.net/
http://www.iis-resources.com/
http://msmvps.com/blogs/bernard/


<jake***@gmail.com> wrote in message
Show quoteHide quote
news:1155512943.611530.235640@b28g2000cwb.googlegroups.com...
> Thank you for your response. That was not the problem, but I think I
> found it. I have been using the FQDN to access it (eg.
> http://server_name.company.com/) but when I used http://server_name/ it
> worked fine. I don't know why I did not think of it before.
>