Integrated windows authentication problems

Hi.
I was wondering if anyone has any insight to the following problem.
I use a DNS connection service to run public websites from my home computer.
Recently I created a website that uses Integrated Windows Authentication for
access. I created the virtual directory in IIS 5.1 and gave all the relevant
XP users/groups access to the target directory (Administrators, Creator
owner, everyone, internet guest account, network, network service, system,
users, guests and a new user that I added to the guests group). I
may have added more users than I needed to, but I've had problems
authenticating.
Basically, the login window comes up when I hit the site and when I type in
the user/pwd for , the window comes up again, indicating that the
user/pwd combo is unknown (event viewer concurs). I've also tried this with
my administrative logon.
I can logon to the site through localhost, naturally, but when I go through
my web domain, the above happens.

Other relevant info:

IIS virtual directory tab:
Read, Write, Log visits, index this resource
Execute permissions: Scripts only
Application protection: Medium (Pooled)

Frontpage server extensions 2000

I have windows firewall turned off.

Internet connection through comcast broadband connection

I use a router which is configured to route port 80 traffic to my computer

computer uses static IP (no dhcp)

I have tried the same thing with basic authentication, though did not know
what to put for the default domain and realm, so I left blank

Tried different network security policies without success

Out of 3 websites set up in this fashion, I can successfully authenticate on
only one, but only on another computer. The only difference with this website
is that it does not have the ASPNET user associated with the target directory
as it involves no server scripting. NOTE: frontpage server extensions gave
option to configure server extensions when making this website because there
were no preexisting "vti_" directories created by visual studio .net in the
target directory. I think frontpage server extensions add two anonymous users
onto the target directory (all guesswork).

Anything anyone could add to this would be greatly appreciated.
I've been banging my head against the wall.

Thanks in advance

Regards,

Warren Hennemuth

Re: Integrated windows authentication problems

Hi,

a) Are you saying that Basic Authentication doesn't work either?

b) Enable Logon Failure auditing (in the Local Security Policy - there's a
shortcut to the policy editor inside your Admin Tools folder) for your
machine. Post the relevant logon failure events here (if you open the event,
there is a "copy" button you can use to copy the data and paste it into a
new message). Please post the events you see when Basic AuthN fails (if you
have that enabled), and when IWA fails. Note: you should not have IWA and
Basic Authentication enabled at the same time when you want to test Basic.
Just enable either Basic -or- IWA and test.

Thanks

Cheers
Ken

"warhen" wrote in message
news:AA2BF156-4781-4B61-BDA6-2A98A52ADF78@microsoft.com...
> Hi.
> I was wondering if anyone has any insight to the following problem.
> I use a DNS connection service to run public websites from my home
> computer.
> Recently I created a website that uses Integrated Windows Authentication
> for
> access. I created the virtual directory in IIS 5.1 and gave all the
> relevant
> XP users/groups access to the target directory (Administrators, Creator
> owner, everyone, internet guest account, network, network service, system,
> users, guests and a new user that I added to the guests group).
> I
> may have added more users than I needed to, but I've had problems
> authenticating.
> Basically, the login window comes up when I hit the site and when I type
> in
> the user/pwd for , the window comes up again, indicating that the
> user/pwd combo is unknown (event viewer concurs). I've also tried this
> with
> my administrative logon.
> I can logon to the site through localhost, naturally, but when I go
> through
> my web domain, the above happens.
>
> Other relevant info:
>
> IIS virtual directory tab:
> Read, Write, Log visits, index this resource
> Execute permissions: Scripts only
> Application protection: Medium (Pooled)
>
> Frontpage server extensions 2000
>
> I have windows firewall turned off.
>
> Internet connection through comcast broadband connection
>
> I use a router which is configured to route port 80 traffic to my computer
>
> computer uses static IP (no dhcp)
>
> I have tried the same thing with basic authentication, though did not know
> what to put for the default domain and realm, so I left blank
>
> Tried different network security policies without success
>
> Out of 3 websites set up in this fashion, I can successfully authenticate
> on
> only one, but only on another computer. The only difference with this
> website
> is that it does not have the ASPNET user associated with the target
> directory
> as it involves no server scripting. NOTE: frontpage server extensions gave
> option to configure server extensions when making this website because
> there
> were no preexisting "vti_" directories created by visual studio .net in
> the
> target directory. I think frontpage server extensions add two anonymous
> users
> onto the target directory (all guesswork).
>
> Anything anyone could add to this would be greatly appreciated.
> I've been banging my head against the wall.
>
> Thanks in advance
>
> Regards,
>
> Warren Hennemuth