From: APA on
I have been having this problem for some time and have read all the articles about it but still can't get my web site to
work with Window integrated security. This is only on my development boxes which run Vista Business and Windows 7
Professional. The thing that the Vista machine was working fine and then all of a sudden stopped. I was wondering if
some patch have disabled something but I haven't found anything. I figured that I broke something. So, I expected that
when I setup my Win7 Pro machine that it would work but it to gives me a "You are not authorized to view this page" error.

My Vista box is on a domain (run on a Windoows 2000 server). I access the web site via a DNS name that does not match
the machine name but I have also tried it using the machine name and "localhost". I am logged into the machine with the
domain administrator account so permission are not a problem. This is my test environment so I have not configured any
domain policies that would prevent access. I'm not sure what changed or what needs to be configured but this is really
annoying and is preventing me from doing proper testing. Again this was working but just stopped for some unknown reason.

Any ideas?
From: APA on
More info, this only happens when browsing in IE and in my .NET application that access a web service on this site.
Also, it prompts me for a username and password three times then displays the "unauthorized" (HTTP Error 401.1 -
Unauthorized) page.




APA wrote:
> I have been having this problem for some time and have read all the
> articles about it but still can't get my web site to work with Window
> integrated security. This is only on my development boxes which run
> Vista Business and Windows 7 Professional. The thing that the Vista
> machine was working fine and then all of a sudden stopped. I was
> wondering if some patch have disabled something but I haven't found
> anything. I figured that I broke something. So, I expected that when I
> setup my Win7 Pro machine that it would work but it to gives me a "You
> are not authorized to view this page" error.
>
> My Vista box is on a domain (run on a Windoows 2000 server). I access
> the web site via a DNS name that does not match the machine name but I
> have also tried it using the machine name and "localhost". I am logged
> into the machine with the domain administrator account so permission are
> not a problem. This is my test environment so I have not configured any
> domain policies that would prevent access. I'm not sure what changed or
> what needs to be configured but this is really annoying and is
> preventing me from doing proper testing. Again this was working but
> just stopped for some unknown reason.
>
> Any ideas?
From: Ken Schaefer on
- Check that your account actually has NTFS permissions to the resources in
question.
- Enable account logon auditing in the local security policy, and see what
logon failure events are logged in the Windows Security event log

Cheers
Ken


"APA" <buddy.a(a)excite.com> wrote in message
news:OvwlxOj5KHA.2388(a)TK2MSFTNGP04.phx.gbl...
> More info, this only happens when browsing in IE and in my .NET
> application that access a web service on this site. Also, it prompts me
> for a username and password three times then displays the "unauthorized"
> (HTTP Error 401.1 - Unauthorized) page.
>
>
>
>
> APA wrote:
>> I have been having this problem for some time and have read all the
>> articles about it but still can't get my web site to work with Window
>> integrated security. This is only on my development boxes which run
>> Vista Business and Windows 7 Professional. The thing that the Vista
>> machine was working fine and then all of a sudden stopped. I was
>> wondering if some patch have disabled something but I haven't found
>> anything. I figured that I broke something. So, I expected that when I
>> setup my Win7 Pro machine that it would work but it to gives me a "You
>> are not authorized to view this page" error.
>>
>> My Vista box is on a domain (run on a Windoows 2000 server). I access
>> the web site via a DNS name that does not match the machine name but I
>> have also tried it using the machine name and "localhost". I am logged
>> into the machine with the domain administrator account so permission are
>> not a problem. This is my test environment so I have not configured any
>> domain policies that would prevent access. I'm not sure what changed or
>> what needs to be configured but this is really annoying and is preventing
>> me from doing proper testing. Again this was working but just stopped
>> for some unknown reason.
>>
>> Any ideas?